Mitch_Ives
Well-known member
Barry_Green said:FCP has a fundamental conflict (right now) which will prevent it from ever embracing that workflow, until they pluck their heads out of their collective rumps and realize that native MXF files on the timeline is a GOOD thing, not a "bad thing." So far they have refused to do that, instead demanding that you convert your files to Quicktimes, saying stuff like "why would we want to go to an inferior format?" That attitude helps no one. (and, er, you allow .AVI files on the timeline already, so why not MXF?)
I agree with the concept of native MXF support, assuming there aren't any unacceptable compromises. If it means giving up the QT advantage and using the kind of formats PC's frequently have to use, then I'm not interested. My favorite "red-herring" was all the PC editing systems saying "we have realtime support for HDV... no rendering needed". The compromise was going to an intermediate codec, which sucked and missed the whole point of native editing. The Matrox Axio makes similar claims, but it's quality leaves something to be desired, and to do any interesting things in PremierePro, means you're back to rendering. If native MXF involves any compromises like that, then I'd pass.
In any event, it's important to clarify that FCP doesn't convert the MXF files, it just puts a QT wrapper on it... no conversion or processing of the video file is done. This isn't a new concept, as many PC editing systems do the same thing with AVI wrappers when editing many different formats. I know that you know this Barry, but I didn't want any new people getting confused...