APPLE FINAL CUT PRO: Apple Final Cut Pro X FCPX Debates FCP Legacy FCP Tutorials

Re: Waveforms going Red

COW Forums : Lumaforge

VIEW ALL   •   ADD A NEW POST   •   PRINT
Respond to this post   •   Return to posts index   •   Read entire thread


Joe Marler
Re: Waveforms going Red
on Sep 13, 2019 at 2:06:08 pm

[Chad Greene] "Our media and cashe is saved externally on our Jellyfish shared storage with all editors/libraries using the same folder. We have been doing this for years on our NFS share without trouble, but just stared using an SMB. Does SMB work differently with cashe?"

I've seen this infrequently when using local storage. It is typically a cache issue. When I delete cache (which is easy to do from Finder if using a designated storage location), then restart FCPX it usually goes away.

If your cache is on the Jellyfish and all editors using the same folder, I'm not sure what prevents conflict. FCPX assumes a single-user mode and there is no built-in logic for deconfliction. This is OK for read-only content like media but for cache and library, writes are happening constantly. Maybe you mean cache and library are within the same folder but each editor has their own unique copy.

Because of high-bandwidth frequent random writes to the cache, I'd normally think you'd get better performance if that's on a local small SSD. This would especially be the case if you are on 1 gig ethernet not 10 gig.

However it's possible the issue was caused by switching to SMB.

It says on Lumaforge's web site: "SMB Protocols...are not designed to work with the FCPX Library Architecture. Currently, the best way to run FCPX in a shared environment is through NFS Protocol."

https://lumaforge.com/workflow

The Lumaforge support page says "Libraries and Cache should only be kept on a Jellyfish NFS Share."

https://jellyfish.support/knowledgeBase/7106702

https://lumaforge.com/workflow


Posts IndexRead Thread 


Current Message Thread:





© 2019 CreativeCOW.net All Rights Reserved
[TOP]