bar the risk you assume of the sync tool finishing its job correctly. If you wanna explicitly close projects in a database, ensure that whatever sync tool you have has finished syncing and access them from a different machine, we don't expect that to cause issues. The PostgreSQL server manages this concurrency well - it reports to the user if a project is already in use (and who is using it), it reports if a project is capable fo collaboration and which bits are being used by which collaborators.ĭisk databases are not designed for concurrency. This applies for DropBox, mapped drives, local rsync services, SMB shares and pretty much anything else you can imagine doing this. Even if that other application is another DaVinci Resolve in another (or same) machine. If a Disk database is in use, but is being locked or written to by another application, there are no guarantees for sanity of the underlying data. It would be great if someone from Blackmagic could chime in and point out any other issues I might be facing.Īt the very least I plan to test this rigorously (Obviously not using important databases) and would always have a backup system in place in case of issues. I'm still willing to accept there may be issues to what I am attempting, but I'm genuinely curious now. This is a little different to the solution I am using with Syncthing, as it is just a system for networking identical folders on different computers. I watched that video from Patrick Inhofer at Mixing light and it appears the issues people were having were related to Dropbox and the way it deals with files when it stores them in the cloud. Seth Goldin wrote:See: viewtopic.php?f=21&t=66662&p=374578Ĭopying entire disk databases from one drive to another should be OK, but modifying parts of the disk database at different times could very easily cause it to go corrupt.
0 kommentar(er)
