![]() ![]() I had brought that folder over from my previous machine. Looked in those, the permissions were fine, but I started to suspect the problem was a clash between the apparently autogenerated project/folder names in those and the current installation. But the bit on CacheClip and hidden folders I had not. read up a bit more, most I caught on earlier (admittedly skimmy) read. We use a separate SSD, because it allows quick and easy access to the opt media. The media storage is the first mounted file path, and it's where optimized media is created. It has some ẃell-written passages on the media storage and optimized media that'll really help you along don't know what that means in this context yet. There is a checkbox for "Direct I/O" that is empty. Looking In preferences under "media storage", the only location I have there is that same resolve media directory. implying that it is there? I definitely don't have permission issues there. ![]() Not sure where that is (or if relevant), but clicking browse brings up my resolve media directory (in my homedir). Looking in project settings under "working folders", the cache files location is "CacheClip". Do you know where Resolve builds optimized media by default? no obvious write permission issues that I can find. ![]() Also tested writing/touching files here and there. most of the directories in there are 0777, the files 0666. You might want to copy that db aside, too. Check the file paths and, preferably, set them to point somewhere else. Sulo Kokki wrote:Sounds to me like Resolve lacks the rights to write to the assigned path, or something else is holding it up.īy default, Resolve sets everything to /opt/resolve, including the disk database. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |