Re: FCPX and SAN

Hi Steve,

I use Small Tree products (and GraniteSTOR) here in my business... great stuff. I'm curious about your "good sharing" practices though. You mentioned the symlink which you showed me previously. My question is this (and it's a biggie):

If we symlink, or find another way to let FCPX access events and projects on the SAN, then you will have multiple editors all accessing one "FCPX Events" folder and one "FCPX Projects" folder. When you open FCPX the project and event browsers show you ALL the projects in those folders. Even if other editors have them open and in use. Now, if you accidentally click on a project that you aren't concerned with it loads the project. Now... in this case, which editor is writing to the metadata database? ... and what is the result of such action? Corruption? Version problems? FCPX, like iMovie does a lot when you load it up, depending on your preferences, it may start doing colour/shake/audio analysis on content that another editor was busy modifying.

Plus, project sharing, the "new Apple way" is all well and good but editor ONE will wrap up his work and "share" a project for someone else (great if the media files are all on the server, reconnecting will be a good experience) but, now instead of just telling someone else to open the project, we have a copy on different machines because we shared it out. Now we have to track who's got the most up to date version, and choose to delete surplus versions. Does this scare anyone else? Can someone please put together a workflow for the rest of us? I feel as though I haven't really cracked this yet.

In the meantime, my guys ARE using FCPX but projects/versions are staying put on local machines and I DON'T LIKE IT!! :-)

When we figure this all out, I'll be sure to post back. But in the meantime, I need all the help I can get!

James