-
Relink
-
Everything is on the QNAP. Libraries and media.
—————-
Michael Hancock
Editor -
[Michael Hancock] “Everything is on the QNAP. Libraries and media”
Yep, that hasn’t worked well for me.
– Oliver
Oliver Peters – oliverpeters.com
-
[Michael Hancock] “I am not seeing this behavior for files stored on our QNAP. When the storage was local I could rename a file at the finder level with FCPX open and it would keep it linked to the file. On our network storage any change in the file name/location throws the file offline and a forced relink is necessary.
“FCPX inode lookup of media on a network volume works fine using Macs and SMB. If media and library is hosted by a networked Mac, it behaves just like a local drive. You can move the files, rename them, even delete the symlinks from within the library package — and upon restart FCPX automatically reconstructs the symlinks with the new filenames and locations on that shared network volume.
I don’t know why it’s not working on your QNAP. It would be interesting if this works on a Lumaforge Jellyfish or other NAS systems. Maybe it’s related to whether you are using NFS, SMB or what version.
On Lumaforge’s web site it says: “On most NAS based storage, FCPX Libraries and media management commands will not work because NAS storage is typically shared through AFP or SMB Protocols, which 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. Unfortunately, for FCPX users most NAS based storage is not optimized for NFS.”
https://lumaforge.com/workflow/
-
I am a big fan of NFS because it’s more stable than SMB and it supports hard links. But we do have many clients who use mixed workflows over SMB and I can say that FCP X editing performance over SMB equals that of NFS.
I did find that file copies over NFS are much faster. These are two screenshots I made recently when remotely testing a large Jellyfish Rack setup with 70 FCP X users at one of our clients in Switzerland (not Swiss national tv). You can see that transfer speeds between NFS shares are much stabler (fewer traffic drops) and that average transfer speeds are higher (370MB/s over SMB and 500 MB/s over NFS).
The Jellyfish (even the small Mobile) runs FCP X Libraries straight off the server without any issues. I actually don’t know any of our clients who do NOT keep their FCP X Libraries or their Premiere Pro project files and cache on their Jellyfish. We can do this because we use advanced hi-level caching in all of our systems.
Relinking files on a Jellyfish is exactly the same as relinking files on a direct attached drive, no matter f you use NFS or SMB. If you are at NAB next week, I will be happy to demo this. We are at the Frame io booth on the floor, in our demo suite at the Encore (send me an e-mail if you want to come and visit: ronny@lumaforge.com), and at the Faster Together Stage: https://lumaforge.com/nab
– Ronny
Reply to this Discussion! Login or Sign Up