Final Cut Pro X

We built our servers from the ground up to take full advantage of the power of FCPX

Most Final Cut Pro X facilities edit with their Libraries from a local volume, referencing media that lives on a Storage Area Network (SAN) or Network Attached Storage (NAS). The reasons for this have nothing to do with FCPX, but instead have far more to do with how FCPX needs to be integrated in a collaborative environment to be able to work effectively.

• In a traditional SAN environment (especially XSAN environments), FCPX Libraries have a difficult time because SAN’s by nature don’t handle small database-driven files well, which is exactly what FCPX requires in order to work quickly and effectively.  This causes FCPX cache, waveform, and analysis files to perform poorly in a SAN environment.
• 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.

The OWC Jellyfish is the only shared storage solution that has been optimized to meet the demanding performance requirements of the Final Cut Pro X Library Architecture, and waveform and thumbnail caching. Our extensive FCPX optimization, allows you to seamlessly work with your FCPX Libraries directly from your server and collaborate with other editors across all of your Mac clients as if your libraries lived directly on SSD storage.

There is no other shared storage system in the world that comes close to the FCPX performance that LumaForge has achieved.

Apple Final Cut Pro X 10.4 Presentation with LumaForge at LACPUG