Can't open projects created in libraries on QNAP SMB network share-Library Damaged error

We ran into this issue with our GBLabs FastNAS running SMB. As soon as we upgraded to MacOS Sonoma and 10.7.1, any FCP library living on the SMB volume would corrupt when duplicating a FCP project within the library. We have seven systems running FCP all mounted to the NAS and all FCP libraries will corrupt when an editor attempts to duplicate a project. Unfortunately all our editors must now work off local libraries while the media can still reside on the NAS. This has forced us to rework a good portion of our workflow. On the plus side, the editors love how much faster the FCP interface works with local libraries.

It would appear the current version of Samba and FCP 10.7 do not play well together.

I just ran a test on an Intel iMac running macOS 13.6.6 and FCP 10.7.1 to a QNAP NAS running 5.0.x firmware over 10GbE and I couldn't get it to corrupt the library. I created a new library, imported some footage, created a simple project and quit out of FCP. The library reopened without any complaints. I then duplicated a large, older library of a 2 hour show, opened and updated it to 10.7.1, then made a new project, added some footage. Quit and reopened the library several times without problem.

@Chris Tipton-King and @ambidextrous - are you experiencing random NAS disconnects? This is a thing and maybe upon quitting, the NAS is disconnecting before FCP has had a chance to finish writing things out?

You might try this smb settings adjustment to see if it helps. https://www.liftgammagain.com/forum/index.php?threads/new-macs-and-smb-disconnects-october-2023.18311/#post-176327

The problem isn't with duplicating the library, the problem lies with duplicating projects within that library. I always try to use exact FCP terminology in these types of forums so as not to confuse non-FCP users (Library vs. Project). We duplicate libraries quite often that live on the NAS. Other than it taking 5x longer to duplicate a library on the NAS as opposed to desktop, we've never had an issue. The issue with corruption begins when duplicating a project within the library. We were told by GB Labs that they have an internal Wiki note that states there is a known issue with opening/importing more than one .fcpxml file over SMB. That's all the info I've been able to dig up on this issue.

I just re-read the OP's description and it seems to point to a problem with FCP since he's running macOS 13.5.2 and experienced library corruption on the NAS after updating to 10.7.1.

@Chris Tipton-King and @ambidextrous can you run a backup copy of FCP 10.7 to see if the NAS library corruption still happens?

Try 14.4.1. There are fixes related to hub connectivity that may effect this.

@Chris Tipton-King and @ambidextrous - Have you raised the issue with the FCP devs via Feedback?

We're running QNAPs but on 5.0.x and FCP at 10.6.5 and haven't run into this issue. Did this start after an FCP update to 10.7.1 or a QNAP firmware update? If it's firmware, you should be able to downgrade. You could try asking on liftgammagain dot com in the storage forum. There's a very knowledgeable QNAP storage person who frequents there.

While I don't have an archive of 10.7 I can run, I can report that we also had a less severe issue when running 10.6.0 through 10.6.8. When running those older versions of FCP we could duplicate a project without corruption, however, if you attempted to duplicate the original one more time (not the new the newly created duplicate) FCP would beach ball and require a force quit. No library corruption occurred so we just lived with the problem. Now under 10.7.1 you will corrupt the library. This problem existed on our previous NAS from SANS Digital and persisted when we purchased our current NAS from GB Labs.

@ambidextrous - So it seems that it's not specific to QNAP, which I guess is good news. Which version of Sonoma did this start occurring? 14.4 or 14.3? Have you raised the issue with Apple and/or the FCP devs? Has there been any response? Your workaround to move libraries locally becomes a headache for version control if a project needs to be edited in another room -- now you've got multiple versions of the library. This is worrisome for all the shops like mine that rely on Network Attached Storage for editing.

Thanks for the correction Terry.

My apologies but I am completely ignorant on this topic, but how is a NAS formatted?

Thanks very much.