[Tony West] ” but he doesn’t seem to be complaining about not being able to work in the same library”
We shouldn’t lump “collaboration” into a single workflow. There are a lot of different needs for ways to collaborate (on premises) depending on what you are doing. For example, in the “YouTube influencer” scenario, the workflow is about the same as multiple commercial or corporate video editors – and for that matter, broadcast news, too. You want to pull from a pool of media, but you aren’t all cutting on the same overall project. You may be cutting alternate versions, different videos from common sources, or something entirely unrelated. FCPX/Resolve/Premiere Pro/Media Composer can let you do that now and easily if everyone is connected to a shared storage system.
The next level is where you have different editors working on sub-projects that are interrelated to one larger campaign or production. There’s where FCPX falls short. For example, editor A has a cut of something that editor B can use within his edit – B-Roll stringouts for example. In the current version of Premiere (without any of the current or future sharing methods), editor B can open editor A’s project (while editor A is working on it) in a read-only mode and copy that stringout into his or her own project. That cannot be done in X today without using the workaround of a transfer library – or by editor A closing his library so editor B can briefly open it.
The third level is complete collaboration. Multiple editors/assistants/other artists all working within the same “master” project file. That’s where Avid excels and what Adobe is trying to attain. For example, the assistant editor syncing/organizing scene 2, while the editor is concurrently cutting scene 1.
It’s this third level that I suspect we will simply never see with FCPX. It was never attained in FCP7 either. I could be wrong, but it just doesn’t seem like a feature that Apple has interest in. In fact, the direction Catalina has taken the OS will make this much more difficult, so that’s a level of complexity that ProApps simply might not want to fight.
– Oliver
Oliver Peters – oliverpeters.com