Can the developers describe the behavior of the material/art libraries with respect to updates if they are stored on shared location?
Is it expected to be multi-instance “safe” with it’s updates, or does it just do a complete overwrite with what is in-memory? And/or does it “watch for/see” that the underlying file has been modified?
Mainly asking cause I run LB on an old laptop at my laser, but also on my main desktop sharing the library directories on NextCloud(similar to DropBox/OneDrive/GoogleDrive), and need to know if I need to be careful to only be running one instance at a time if any library is modified.
Storing any LightBurn files, whether they’re design files, library files or whatever on cloud or network drives is not recommended. Many users have lost valuable LB data doing so even when the access has been non-concurrent. However, having said that I have been successfully storing all LB related files on my Synology NAS for about three years now without issue.
I don’t think anyone has managed to get to the bottom of why LB suffers with corrupt files when stored in the cloud so I believe it’s still an issue.
AFAICT, LightBurn does nothing to protect library (or design) files from multiple instances on different machines.
I have basically the same setup as you: one PC atop the laser, another upstairs at my desk, and a “file server” with all the design & library files in the basement. The server uses NFS to share the files & directory structures.
Based on my experience, LightBurn does nothing to protect its files from multiple instances running on different machines. I have learned to never open the same design file on both PCs and to always close the file before trotting up or down the stairs. I get that right almost all of the time.
LightBurn reads the Material Libraryonce as the program starts, then writes it at every change. The only way to synchronize the file at the “other” machine is to hit the library’s Load button to re-read the file. I get that right most of the time.
Lightburn is not a network application. It is a desktop program and all expectations should include this parameter. Few programs can handle multiple instances across a network.
