[cam khoury] “How do large facilities collaborate on projects with many shared resources if the main organizational tools, the project files, are restricted to many scattered local drives”
By setting up very rigid protocols and practices that all editors must adhere too. Failing to do so will result in corrupt projects, or lost projects…or scattered project. It’s true, the Shared Project Workflow is superior on Avid…but it can work in FCP as long as you set up a project workflow and make sure EVERYONE sticks to it.
[cam khoury] “Imagine a situation with running footage or a stock library that is shared among 4 or 10 or 20 editors.”
Yup…done that. Everyone has a copy locally. And if footage is added, it is added by ONE editor, or an assistant. They then update that project file to the SAN, inform the editors of the new footage and an updated project, and all the editors then grab the latest project for that media.
[cam khoury] “Is a shared project scenario or other collaborative situations just not attainable with FC?”
Oh no, it is TOTALLY attainable. Bunim/Murray, a company that uses FCP, has anywhere from 4-8 shows running at one time, and that has over 100 FCP stations, with many MANY editors working on one show at at time. How they do this is with a rigid set of ways of handling an managing projects. And I have been in more than one production facility where we had between 4 and 8 editors accessing the same media and using project files on local systems. It has been a challenge when some editors don’t adhere to the system, but every time something weird has happened, it is traced to editors not following the rules. User error.
You just need to figure out how to do things, and then post a sheet of the rules. Yes, it is more difficult than Avid…Avid works beautifully this way because the project file contains MANY MANY items. Each bin is a separate file in the project folder, that’s how someone can access it, then they OWN it…it locks to changes from anyone else…and other people can access it. This is how you can share ONE project among many editors. FCP is ONE project file, so multiple editors cannot access it at the same time. So you have to do things like make footage projects, sound effects projects, and SEQUENCE projects. And only allow the Assistants to update the footage projects. A lot is involved.
[cam khoury] “Now some will say that you can make copies of projects and use them locally, saving them back to your SAN or file server upon completion. My concern with that strategy in a high volume (or low volume for that matter)situation is that the risk of improperly syncing projects back and forth is extremely high.”
The main person who says that, Mark Raudonis, is the pioneer at Bunim/Murray who figured this out. And if you want an example of a successful, high pressure, multiple…and I mean DOZENS…edit stations on one project, that is the place. Reality shows galore. PROJECT RUNWAY, ROAD RULES. Reality programming with TONS of footage and tight deadlines. They have a process, and it works. I took the basics of that workflow (the only thing Mark would part with) and created separate workflows for two production companies. I put the basics on my GETTING ORGANIZED DVD. You just need someone who knows FCP inside and out, and who is HIGHLY organized, to develop the strategy…and you need editors who aren’t their sloppy-ass selves and get lazy and don’t do things right. Every time we had issues, and an editor was swearing at FCP and complaining up and down and missing files and sequences, we tracked it to them not sticking to the rules. Their excuse? “I can’t be thinking of all this technical stuff. I just need to be creative and edit!” Sorry, editing is TECHNICAL too.
And you need to hire VERY COMPETENT help…Assistant editors who are VERY skilled, and stay on top of things. Not bright young faces off the street. Experienced people.
[cam khoury] ” I was hoping to get some practical advice. I wonder how Turner or Discovery or Fox et al accomplish the monumental task of true project collaboration with this FC limitation.”
They hire bright people, or consultants (such as myself) to walk through strategies for multi-station workflows. And EVERY SINGLE case I talk about “work locally, back up to the SAN.” Or I point out EDIT SHARE, that has a proprietary way of organizing things that makes it very Avid-like. Unfortunately it is a tad more expensive than simple shared storage…so companies pass on it..thus making it so that we need to employ the rigid rules.
[cam khoury] “What strategies are people using? Sorry for the long setup but I hope this susses out some useful answers.”
I would go into more detail, but this is part of my business…part of how I remain marketable. I know what to do, how to set this up. If I, or Mark, just posted it for everyone to see, then we are now slightly less marketable, because EVERYONE knows that information. But, the basics.
– Multiple projects…somethng Avid can’t do. Footage projects, audio projects (music and SFX), and sequence projects…one main one to store them all that is maintained by an assistant, and one on each edit station. Share cuts by asking someone for their cut, and they send a project file with ONLY their cut in it. Or send an XML of the cut.
– Projects stay stored on the local system, with the masters on the SAN. Every night, the editor back up their projects to the SAN.
– Have a gate keeper. Any changes made to projects will be done by ONLY authorized personnel. One person, or couple of people (assistants, lead editor), that maintains the master project files. Captures the footage and adds it to the existing projects, tells editors to grab the latest one and replace what they have. EDITORS ARE NEVER EVER EVER TO CAPTURE FOOTAGE THEMSELVES, or import footage of any kind! Those who do will be repremanded, disciplined, shot…and fired. Any time we see FOOTAGE OFFLINE, and when we go to reconnect it is on the DESKTOP of an editor? BIG TROUBLE. Editors don’t do any capturing…they tell assistants, or the LEAD editor (who might be the gate keeper) and they do the capturing.
– ADHERE TO THE RULES at all costs. Stray and you hurt everyone.
– Again, if you want Avid-like project structure, look at EditShare.
– Hire a consultant who specialized in these workflows, and adhere to their workflows. Don’t hire them, listen, then just go about doing things the same old way, then complain that they messed up. Sorry, we come back and see that people don’t adhere and mess things up. It’s pretty obvious.
And, if in the end you just can’t do it… you can always go back to Avid. The software version is cheap, works on the same macs you have now, and you don’t even need UNITY to share media and projects. Wouldn’t hurt though.
Shane

GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def