Final Cut Pro media not reconnecting from Synology NAS on MacBook Pro after macOS update

No, Apple's specifies this somewhere, also, Libraries on normal local drives, NAS is for media only. Also, when using a NAS with FCP, Apple has some very strict specifications on how it has to be set up.

Critical SMB issue with Final Cut Pro 12.… - Apple Community

Issue solved, do NOT store your LIB files on the NAS, just don't do it!

Reviewing everything again, I do think it's Golden Gate. Recheck SMB/Samba/network/permission settings again. I agree it sounds like Golden Gate changed something.

Yea, that's actually a pretty good question, I chose BTRFS for it's ultimate flexibility, you can mix and match drives with it. Not that I actually did that, I have 8 4TB SSD's, I got them back in the day when they didn't cost near $1000 a piece! Perfect for editing off of. I did this about 4/5 years ago and in all that time, I didn't come across any mention of not storing your Libs in the same location as the media. I had a few issues doing it that way, like when you go to duplicate a project in an event in the library, it would crash the whole app, so I got used to make new, then copy paste into the new. Never dawned on me that I shouldn't be editing off the same source. This also fixes another issue where when I go on trips, I'd have to duplicate the libs onto my SSD for travel, and then when I got back, updating the lib on the NAS with what I had done, remembering to copy back over the assets that I had used. NOW I don't have to do that arduous task, just have to sync the content, as the libs will already be updated! This is a foundational shift in how I operate, and I do feel like a complete idiot for not finding this out sooner, BUT, I know it now, and am benefiting already as I had an update to an edit, command D now works! 😎 Using a MBP has the benefit of being a really good edit machine, and it travels!

Some more information, I have now backed up all the content that was on the NAS to disk and a few SSD's, Final Cut has zero issues relinking to those devices. When I attempt to even relink one item on the NAS, FCP sees the file, attempts to link to it, no errors, then, the item still remains unlinked. The dreaded Missing File! It's not a deal breaker, but I'd sure like to have this functional again, all because I updated to GG, which was supposed to be better. This setup worked perfectly before, there's some network thing that FCP is not happy with.

All I know is that I have been editing Libraries off my NAS for about 4 years now, without much issue, the few quirks, and like I said, in all my setups when I got the system, there was no forward information about not doing that. But hey, now I know, and life is SOOO much easier for it, streamlined a few processes for me that make working with the app now a more normal circumstance, as it was intended to work. I never knew, I think I did some digging in those early years, but clearly, I didn't dig deep enough.

I'd argue for the better, I was dreading the update as my Loupedeck driver was still the old Intel version. Luckily, my fears were put to rest when I loaded in the new Logi driver, they added FCP back into the list of control surfaces. Further more I was able to import my previous settings, win win. The trick came when granting permissions, as the installer placed the controller app into the correct spot in permissions, but it didn't give the controller the permission it needed to control an Apple app like FCP. The fix, remove it, then manually add it back in. This works, I don't know why, and I really don't like doing voodoo to get something to work, it means when I get a new system, I have to remember what I did before to get it to work again. I should make notes when I do these things.

There have been other posts over time about FCP and NAS issues. Not sure if it's a macOS issue, an FCP issue, or a little of both. What format is the NAS?