[Aindreas Gallagher] “doesn’t that kind of mean they’ve just got an adobe style media encoder going as a separate process?
Isn’t it true you can’t handle any of the encoding media before the encode is finished? As in – there is no invisible swap out of the avchd for pro res as FCPX accomplishes?”
Sort of yes and no. It does not have FCPX’s “inviso-relink,” which I do agree is more elegant. It will immediately populate your bin with “.new” clips, which appear online (1 by 1) as soon as each transcode is done. At any time you can tell your sequence to relink with the new media. You don’t have to wait until the whole process is done to relink, you just won’t have them all.
On that note, though, I found that MC7 finally handles AMA media smooth enough to work with, from beginning to end — so long as you have really fast storage. I was editing a TV promo filmed with H264 footage. I did a few tests and determined that editing with AMA footage was in the same realm (cpu usage wise, etc) as editing AVCIntra, which my laptop handles with ease. I ended up not transcoding and found it working just fine. Surprising! When the project was finished, I sent the sequence (not master clips) into the background transcode process, just so I could archive the project. Worked as expected.
As a small side bit: I did desperately want an excuse to try Premiere CC, and actually attempted an edit of the same TV promo in it. True, scrubbing the H264 footage was faster than Avid, but the project used a lot of slow mo speed ramping, to which Avid’s fluidmotion was a better option than constantly making AE comps and placing them into Premiere. It’s weird.. but if Adobe wants their time remap feature to be used in Premiere they really need to add proper frame interpolation such as what AE has.