Page 1 of 1

[MacOS] Cant stop trying connect to SMB share on launch

PostPosted: Tue Jul 28, 2020 12:42 pm
by jamesac
This problem exists on all MacOS computers ranging from MacOS 10.12 to 10.14 for versions 15 and 16. A media storage raid no longer exists, but DaVinci refuses to stop trying to connect to it at launch. I've tried removing all references to it in the Preferences and even destroying the database and creating a new one.

Regardless of attempts, Davinci will try, wait for a minute or more (per missing resource) and fail to connect to the network drive which significantly delays the application launch.

Re: [MacOS] Cant stop trying connect to SMB share on launch

PostPosted: Mon Dec 14, 2020 11:34 pm
by Ed Arsuffi
Did you ever find a resolution for this? I too am now experiencing this.

Re: [MacOS] Cant stop trying connect to SMB share on launch

PostPosted: Mon Dec 14, 2020 11:49 pm
by Dwaine Maggart
Are you using the Apple App Store version of Resolve? If so, the following should fix the issue.

This is all part of the Apple App Store sandboxing joy.

In Resolve, go to Project Settings - Color Management.

Scroll down and select Open LUT Folder.

Make sure you have the Finder View menu "Show Path Bar" enabled.

At the bottom of the Finder window that's open showing the LUT folder, you'll see the long convoluted path where Resolve App Store stuff gets saved.

The last part of the path is Library/Application Support/LUT.

Double click on that Library (not the Library further back up the path).

Now select the Preferences folder.

One of the files you'll see there is:

com.blackmagic-design.DaVinciResolveAppStore.plist

Change name of that file by adding a .tmp to the end:

com.blackmagic-design.DaVinciResolveAppStore.plist.tmp

Now restart Resolve. The file will get recreated from default settings, and will lose that bogus path info that's causing the issue.

Re: [MacOS] Cant stop trying connect to SMB share on launch

PostPosted: Wed Apr 14, 2021 2:58 pm
by Ed Arsuffi
Thanks for the help. Yes, that corrected the issue.