Originally Posted by Marvin
It's not really about editing the same sequence and getting real-time updates or anything like that, it's just the workflow of sharing edits that hasn't been thought about enough. Here's an article describing some of the concerns:http://provideocoalition.com/index.p...t_avid_switch/
With FCPX, there is now no ability to manage media outside of FCPX. The focal point is Events, not clips. The relinking ability is fine and everything but it's still slower than before.
I believe that the reason for the focus on events rather than clips is the metadata and the ability to quickly categorize, find and reference the clips -- among other things, eliminating the need to copy/bury the same clip in several bins in several projects.
In FCP 7, you could right-click a segment, reveal in Finder, move it, open it in AE, do a comp and render it back out to the scratch and FCP 7 didn't even ask you to do anything, it just relinked it exactly in place with the changes.
In FCPX, you can't get to your source media easily as they are shoved into Events and if you make a change to an Event, it breaks. If you are constantly shuffling media around and making changes, which you do in a collaborative workflow, that gets to be a real pain the ass.
As I understand the collaborative environment, the media clips reside on a central store -- wouldn't moving/changing clips disrupt collaboration? In any case, in FCP X the events as well as the clips are on a central store for collaboration.
You can't open two projects/sequences at the same time. If someone sends you an edit that you need to merge into yours, you can't just flip between tabs and copy/paste the parts you want because FCPX only opens one project sequence at a time.
In FCPX the project and the sequence are the same thing. In FCP 7 you cannot have 2 sequences open at the same time (but you can tab between them). In FCP X you cannot have 2 projects open at the same time -- but you can easily go back and forth among projects... there are left and right arrow controls in the upper left of the project/storyline window.
So, you can open project A, then open project B, go back <--, copy (any or all), go forward -->, paste... I think it is easier to incorporate and rearrange the clips in the combined FCP X project that it is in the FCP 7 project -- using the magnetic timeline, absolute positioning, either or both.
You can't version projects the same way. You can duplicate edits but then your active projects view gets cluttered with versions. Before, you could just save a file and shove it somewhere out the way.
In FCPX you can duplicate a project in the same location (project view) or Duplicate and move (place) it in a different location. Or, you can just move the project to somewhere else -- either way can be used to hand off a project to another editor or computer,
You can't really send an edit to someone in an intuitive way. Apple has included no option inside FCPX to actually save out your edit. You can copy it to an external drive, you can move it but you can't save a copy of your edit somewhere else on your internal drive to send to someone else. You have to do it manually by going into your projects folder, getting the .fcpproject file and sending it from there. On the receiving end, the person has to create a project folder and drop the fcppproject in and restart FCPX for it to show up and do the same back and forth.
Here's one way that looks pretty good:Managing Your FCP X Events & Projects using Disk Images
Then there's the issue of non-native editing. Sometimes you just want to knock together a proxy clip e.g as a storyboard edit. Regardless of what you do, FCPX will always try to render your footage to ProRes. Constantly rendering, wasting CPU cycles. If all your camera source footage is in DVC Pro HD and FCP 7 can edit natively, why doesn't FCPX do the same? If you jump from FCP to AE or Logic or whatever else, do you really want FCPX burning your CPU up and wasting drive space on a transcode that isn't really necessary? If it plays back in real-time, then leave it the fuck alone.
You can turn off transcoding and background rendering and edit quite nicely in the native codec. If you wish, you can make a selection and render only that -- say to improve playback on a stacked composite or clips with lots of effects. But you can playback edits without any rendering -- maybe slow, but they play.
FCPX has a lot going for it with GPU-accelerated encoding, real-time effects, nice UI (this is important to all users) and is feature-rich but the way it's setup is not going to work for everyone. Users have to decide for themselves what works and if collaborative users migrate to software that they find more efficient while single editors adopt FCPX, which is what seems to be happening, the software design will have defined its audience. If Apple wants an audience of collaborative users, they have to design the software to suit the workflow better.
I think that FCP X can improve their collaboration features (I've been reading up on Final Cut Studio).
I believe that this is in the master plan. One of the advantages that FCP X has is an SQL database as part of every project and every event -- in the future, I can see these individual dbs being incorporated into a master shared SQL DB on a central store for collaboration.
In this way, editors could check out projects/events/clips/edits down to whatever level that makes sense, e.g. editor 1 does color, editor 2 does sound, editor 3 does titles... on the same edited clip segment at the same time.