Hi everyone,
First off, a huge thank you to @ytf, @randy, and the others who provided such valuable advice on archiving in my last thread. Your insights were a game-changer for my backup strategy! (Apologies, I can’t tag more than two people here).
For an upcoming production, I’ll be supervising another artist in a Multi-user Flame environment. I will be on Rocky Linux (Host) and they will be on macOS (Client). Our goal is to implement a robust Shared Project workflow via our local network to eliminate the overhead of manual archiving and file transfers.
To ensure a seamless collaborative pipeline, I’d like to validate a few technical points:
-
Connectivity & Discovery: Beyond standard networking, what are the current best practices for Stone+Wire configuration to ensure the macOS client reliably discovers the Linux Framestore?
-
Storage & Path Translation: We are using centralized storage. Are there specific mount point strategies or Path Translation (lowres.cfg) gotchas I should be aware of to maintain media integrity across different OS file paths?
-
Permissions: Any tips on managing UID/GID or OS-level permissions to prevent “Access Denied” issues when both systems write to the same folders?
-
Conflict Resolution & Locking: How does Flame’s Soft Locking behave in this mixed OS setup? Is the industry standard still to “Grab/Copy” sequences into private libraries for versioning, or is direct editing in Shared Libraries reliable enough for high-stakes supervision?
If you have any “pro-tips” on optimizing this type of cross-platform setup, I’d love to hear them!
Thanks in advance for your help!