“When Alban posted elsewhere features that he liked that are unique to FCPX, some people brushed them off as not important.”
Since I am that “some people” I think I ought to clarify the context. Scott Sheriff posted the following in response to a question.
“3. I hear that FCPX is missing a lot of features real editors would be loathe to give up.”
You heard right. No tape I/O, no XML, no OMF, no multi-cam, no ability to open legacy projects, no way to share a project with another editor due to file structure, no way to assign tracks. There’s more, but that should give you an idea.”
Alban then responded by listing all the new features of FCPX that he valued. My response was mainly meant to distinguish between essential industry standard functionality and the given properties of an individual program.
Essential industry functions are those things common to all NLEs – if a facility was going out shopping for a new NLE what are the basic features it would have to have. (I’m talking here about a high end facility that has to accommodate various different clients and workflows.) Scott’s list is full of those.
Alban responded by saying in effect “so what, FCPX has all this …” – and listed a bunch of program specific functions – skimmers, smart collections, etc.
I was trying to point out they are not the same. The industry standard functions are used by every major NLE without exception.
In addition each individual NLE has their own program specific functions that give them their individuality and appeal – Avid’s trimmer and media management, PPro’s integration with AE & Photoshop and the mercury playback engine.
Different people will have different opinions of the program specific functions – some may love the skimmer, some may not.
Facilities don’t have opinions about Multi-Cam and OMF export – either you have them, or don’t bother showing up.
My previous post was trying, badly, to say these 2 types of feature sets are not comparable. You can love the auditions in FCPX all you want, but if you can’t monitor properly, no high end facility will use it.
Obviously all this changes when FCPX gets updated, but for now Scott’s original response was correct, and Alban’s was off the mark.
“In the meantime I too make do with “hybrid” workflows but the time savings I get in FCPX on projects that don’t need the missing features are incredible.”
A description of a project and how long it might have taken you before vs taking you now with X would be helpful, and where in the process you think the time savings are happening.(this is a real question, really would like to learn, not baiting you here.)
Herb Sevush
Zebra Productions