I just updated to latest high sierra and mc and am having problems saving the project to a network drive. Prior to the update, no problems. I can save to internal drive as well as direct connected drives. Thoughts?

Have you tried Mac Repair permissions?

Then make sure the user permissions are Read and Write.

Then rebuild the databases.

Marianna

Hey Marianna,

I did all you recommended but no joy. The odd thing is that all the bins save fine to the network dirve, just not the project file. I thought it was the newest avid software, but I also have high sierra installed on my laptop running the last version 8.9.3? before the naming convention switch. Upon opening the project, a warning message comes up straight away and says I will not be able to save project. Very odd. Thoughts?

Brennan

UPDATE:

I did a clean install of the High Sierra OS 10.13.1. I then did a clean install of MC 8.9.3. (my latest version 2018.9 does the same thing as 8.9.3, I just happen to have a dongle for that one which makes it easier to check different processes) I then tried opening up a project from multiple network drives and none would save the project file, but had no problems saving bins, or anything else. I rebuild permissions from the terminal, I have tried everything the interwebs had to offer. Is no one else having a problem like this? I know its not just my NAS failing to save, its every drive I mount on a network. My network is not complicated...its all mac and all the machines are streamlined for thier particular purpose, ie not a lot of extraneous stuff installed. I would appreciate any help at this point. I can not be the only one....

Brennan

Have you tried a new project?

KK,

Yup. New project, new settings, same results. I am baffled. The exact same setup works flawlessly in 10.12.6.

Thanks for the response.

Brennan

Are you working in a Unity/NEXIS-Like environment? Or just using the NAS as external storage?

One way to tell is if there are subfolders in your project folder for each system that's accessed the project (and, a corresponding AVP file in the system folder).

KK,

I use my NAS in both situations. Sometimes I do project sharing with indiestor's mimiq (fantastic) and sometimes I just use it for shared storage. For my tests, I have tried both configurations with the exact same result. To reiterate, I have used both configurations flawlessly in 10.12.6. I'm attaching the error message I get.

And just to confirm, you're seeing this both in 8.9.3 (the screen shot above) AND 2018.8/9?

Mac based Media Composer has done this for as long as I can remember when using SMB based shares. It's fairly normal.

Certain third parties, such as Editshare, used to advise folks to install Thursby Dave as a fix. Later they found another solution.

For what it's worth you can normally work around this issue by saving projects to NFS based mounts. That doesn't cost a bean.

The bottom line is that the gold standard for working on a network is NEXIS. If you’re using third party storage talk to the vendor, they might have a fix

radrattus is spot on....

Also... one other thing to check.  Check your Mac Sharing name. On the Mac desktop go to..

Apple Menu > System Preferences > Sharing

The Mac sharing name will appear at the top of the page.  Make sure the name is less than 15 characters, has no spaces, or special characters (! @ # $ % ^ & * ( ) _+ ? : " > < , . ' ; ~ `).

Marianna