Thank you, unfortunately they do not cover Synology Drive.
But I did some testing at home at it seems to work fine. My guess is that it might be the Synology disk format.
I have ext4 at home and in the studio I know for a fact they are using Btrfs.
This kinda sucks but I guess, we might have to move over to another NLE 😕
I don't think ext4 or Btrfs is related to the problem. Those are server-side filesystems used by a Synology NAS.
This is likely an operational problem introduced when you began using Synology Drive to sync complex open FCP libraries while in use. An FCP library is internally a relational SQL database consisting of many files. Therefore, it should be considered transactionally inconsistent unless FCP is shut down.
The situation is similar to having a Windows client running SQL Server and trying to sync that SQL database to a Synology server while writes to the SQL transaction log are happening. In either this case or the FCP case, it is not a bug with the app, and there is no fix possible in the app. Instead, it is a procedural issue that requires understanding the nature of transactional consistency during backup procedures and taking appropriate action.
Test results will naturally vary based on the activity level in the FCP library. For example, you could run one test where Synology Drive does not corrupt data, yet in another test, it might. But the only reliable method is shutting down FCP before the library is backed up, transferred, or copied.
Due to the complex internal structure of the library, it's also wise to consider doing a verified copy using any of the various utilities such as Beyond Compare:
, Carbon Copy:
or make a validation checksum using the tool Integrity Checker:
Other NLEs (such as Premiere) that are not based on a SQL database and have limited data organizational features might temporarily avoid having their project database damaged by Synology Drive. However, it could later happen. I suspect damage would be more likely with Resolve since it also uses SQLite but not to the degree of FCP. Resolve can optionally use PostgreSQL to store project data. If Synology Drive tried to sync that while in use, it would possibly damage the database similar to this FCP scenario.
Your best steps are to verify that no FCP library is backed up or synced while it is open and in use. When backing up or syncing a library through the network, it should ideally be verified or checksummed. If you only want a library or project moved to another machine, that can be done by exporting and importing XMLs.