Anyone seriously using FCP X in a Volume-based SAN like SanMP?
We have a 12 seat, 60TB sanmp SAN. 8 seats are used for FCP 7, the rest for audio. We have a central job server, where the FCP suites save all projects and related Motion files.
Any client can walk in and open any project on any machine and continue working in any FCP 7 suite. New media for that project gets saved on the suite’s own write-enabled SAN volume, and any media stored on any other SAN volumes are accessed in read-only mode. No problem – we have been running like this for 6 years. No metadata server needed, not secondary ethernet network. It just works.
How do you see FCP X working in this environment? I understand that it will see each suite’s own write-enabled SAN volume as just another local disk. It will create events and projects there. However:
-If you want to open a project in another suite – what happens? It will only see the media, events and project from the original suite in read-only mode. Does it create a new events database on its own write-enabled disk? Or is this just a bad idea?
Considering the AVID and CS6 alternatives to FCP X – in an environment where I have hundreds of clients who work on thousands of projects in 8 suites looking at the same media set – where do I go?
Page 1 of 2