Page 1 of 1

Davinco Resolve 16 (free) keeps looking for old Drive

PostPosted: Wed Jan 27, 2021 6:41 pm
by Ralf Jakobs
Hey guys, hope you can help me on a specific problem.

So, i was using Davinci Resolve 16 (the Mac-App-Store version) with a NAS as an external drive. Long story short, my old NAS (a QNAP TS-431P) had some issues and i replaced it with a new one (Synology DS920+) and copied all the data over to that drive.

Now when i want to start Davinci, it tries to connect to the old one, fails obviously and then the program crashes before startup.

What i've done so far:
Created an extra volume with the name of the old one and activated afp connection on the NAS. I usually have this deactivated and only use smb, because my photography program (Capture One) really hates afp connection. This allowed davinci to auto mount the drive (on both smb and afp) and it starts normally I then deleted all the media storage locations in preferences and replaced them with their counterparts on the new drive.
And i replaced every single piece of media in every project (read: i deleted the old „offline“ ones from the media pool and added the same from the new drive)
So basically everything works, but it still searches for the old volume, even if nothing i can find in the programm itself refers to it

My main media location is on my main drive /users/#myuser/Movies/Davinci Resolve as well as the Project database /users/#myuser/Library/containers/com-blackmagic-design-DaVinciResolveLite/Data/library/Application Support/Resolve Disk Database
My machine is a iMac 27“ (Late 2013) with MacOsX 10.14.6 Resolve is the latest Mac App Store Version (16.2.7.010).

hope you can help me, thanks in advance :)

edit: i actually managed to get it to work again, just to keep you updated. I backed up the Database (with the in-program backup button) then deleted the whole com-blackmagic-design-DavinciResolveLite folder in Libraray/containers (didn't delete, but moved somwhere else). DaVinci was in it's default state afterwards, so i just imported back the Database, relinked my media, and everything works :).