Game of Thrones London Trailer workflow in X.

[Andrew Kimery]

[Simon Ubsdell] “I wouldn’t particularly recommend this as a workflow, It was a little bit of a pain.””

Here’s the rest of the quote though, “But for me it was much nicer cutting in X for 2 weeks and spending half a day sending it to Avid, than spending 2 weeks in Avid.”

Anytime you transfer an edit from one NLE to another you are going to lose things, especially to/from Avid since it’s the only one that uses AAF as opposed to XML.

[Bill Davis]

Isn’t it interesting that as an editor working at the top of his game, Tom is willing to shoulder some export complexity AFTER his creative work is done – in order to get the benefits the X approach provides him during his actual editing.

Makes you think, huh.

Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.

[Simon Ubsdell]

[Andrew Kimery] “Anytime you transfer an edit from one NLE to another you are going to lose things, especially to/from Avid since it’s the only one that uses AAF as opposed to XML.
“

Yes, agreed – I was just quoting selectively for journalistic effect 😉

However, it remains that the X2Pro export didn’t work for the audio – which should be a matter for concern. I have great respect for what the guys at Marquis have achieved and generally it’s solid enough, but at the same time I’ve had too many failed exports just like this to be entirely happy with the workflow. And this was a really pretty short and simple timeline …

Simon Ubsdell
tokyo-uk.com

[Scott Witthaus]

[Simon Ubsdell] “I was just quoting selectively for journalistic effect “

tsk, tsk, tsk….shame on you! 😉

Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter

[Andrew Kimery]

[Bill Davis] “Makes you think, huh.”

He’s inflexible and stuck in his ways? 😉

[Bill Davis]

Exactly Andrew.

Just like Premiere Pro editors are stuck in THEIR ways – seeking workflows as much like what they’ve been accustomed to for the past 30 years as possible cuz, you know, change is hard.

; )

Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.

[Charlie Austin]

[Simon Ubsdell] “However, it remains that the X2Pro export didn’t work for the audio – which should be a matter for concern”

FWIW, it’s not X2Pro in this case, it’s Media Composer. Until 8.5, more than 16 tracks would cause problems, but the real issue is that -even coming from ProTools – you have to “quantatize to frame boundaries” for an AAF to work at all. X2Pro doesn’t do this and, since X will have lots of edits on subframes, Media Composer won’t open it. Could Marquis fix it? Maybe, but their focus is ProTools and other DAW’s, which happily accept the AAF’s.

I’ve heard of random X2Pro issues but – and this is anecdote rather than data – I’ve never had a problem sending X2Pro AAF’s to mixes… They’re usually very happy with the prep… split out properly, all tracks named etc.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Simon Ubsdell]

[Charlie Austin] “FWIW, it’s not X2Pro in this case, it’s Media Composer.”

Thanks for clarifying, Charlie. That makes sense. It wasn’t clear to me that this was the route.

Coincidentally we recently delivered some GOT trailers and spots to HBO and they were asking for mixes and stems not the original laid audio as it seems they did in this case, hence my confusion here. I was assuming the issue was getting from FCPX via X2Pro into ProTools, not taking an AAF from X2Pro straight into Media Composer – which is obviously not what it’s designed to do, as you say.

Simon Ubsdell
tokyo-uk.com

[Gary Huff]

[Bill Davis] ”
Just like Premiere Pro editors are stuck in THEIR ways – seeking workflows as much like what they’ve been accustomed to for the past 30 years as possible cuz, you know, change is hard.”

Not that hard. Once you actually get over it and look past the glitz, the workflow isn’t really that different, as far as the actual edit is concerned at least.