-
Native OMF export support needed
-
Apple would really have to pump up Logic Pro X to get anybody excited about it. I think it would have to be fully integrated with FCPX, but that probably won’t happen. Logic Pro X is destined for a dumb down. Pro Tools will soon go to 11, with RTAS out-the-door, AAX in, 64 bit, offline bounce, and probably a lot of other stuff. 11 will quell all the other sequencer wannabees. Pro Tools and Reason are my audio apps of choice. I tried a bunch of other stuff, and retired them all. Logic is still on my plate but not for long.
-
[Lemur Hayop] “Apple would really have to pump up Logic Pro X to get anybody excited about it. I think it would have to be fully integrated with FCPX, but that probably won’t happen. Logic Pro X is destined for a dumb down. Pro Tools will soon go to 11, with RTAS out-the-door, AAX in, 64 bit, offline bounce, and probably a lot of other stuff. 11 will quell all the other sequencer wannabees. Pro Tools and Reason are my audio apps of choice. I tried a bunch of other stuff, and retired them all. Logic is still on my plate but not for long.
“Logic already had its dumb down from 7 to 8. Does anyone remember “the enviroment”? Now all thats in the background. I don’t see how they could make Logic any more user friendly? Everything is basically done in the background except busses and sends which are still really intuitive. What are they gonna do, get rid of the mixer? Its already pretty streamlined and neat, especially when you look at the competition. The only thing they should do with Logic in Logic X is improve the audio editing. Bring it more inline with Pro Tools in that respect.Other than that, theres not much to do there. Maybe thats why there hasn’t been need for a big update in a while.
Neil Goodman: Editor of New Media Production – NBC/Universal
-
[Shane Ross] “Tapes are rolling of each sporting event…don’t kid yourself.”
Not to cut with though Shane. Fox still wants to have a backup recoding (not in the truck) for archive but we don’t go to the shelf for that to cut.
[Shane Ross] “NFL films, still shoots film. “
I run side by side with them Sundays and I hope they will forever, but doubt they will. I hear you though.
-
[Michael Gissing] “this thread is about workflows where OMF matters”
The thread is, but I was speaking about his comment on Apple “catering to the DSLR crowd “
-
[Neil Goodman] “What are they gonna do, get rid of the mixer?”
Neil,
They’re working on a way to get rid of those troublesome tracks.
Franz.
-
Quite honestly I don’t know if I’d use an audio facility that is still on Pro Tools 6.1 or earlier.
https://www.avid.com/us/products/DigiTranslator
Actually we were using a guy that was several versions behind…He didn’t know how to export M&E stems at the same time as the stereo mix (which wastes a lot of time on an hour show), or when a compressor was breathing for that matter either.
All exports from Avid we do are AAF these days as it contains the RTAS plugin information – it’s nice for the sound mixer to get an approximation on reverbs etc or at least know they should be there if the producer misses it.
I’m sure X2Pro will get there in the end with regards to handles etc. I’d rather Apple not rise the price of OMF licensing which I’d assume would be around 200 dollars on FCPX. (Gee remember it cost 2 grand on M100?)
I’m hoping there will be busses on the new ‘roles’ mixer – as all I need to do on some line record programmes is slap a compressor/limiter on the master to make sure the audio is legalised.
Why not just buy Xto7 and export to FCP7 and export the OMF from there?Jon
-
Perhaps this is relevant or not, X2Pro v2 feature list announced. Coming in “August”.
https://us1.campaign-archive2.com/?u=480c02edc83b008592a0592f6&id=864e6d96d0&e=3b163f123b
For my purposes, getting an FCPXML to FCPXML friendly programs (such as red cine x pro) is easier than try to get an XML of all native content from Pr to other programs via XML.
Walter Biscardi has blogged about Avid difficulties when using AMA (I know, it’s AMA).
All the audio mixers I’ve spoken with are just fine with AAF. OMF does seem to work in Premiere, AAF is trickier.
So while X needs a bunch of work, it’s already working for certain and specific workflows/applications.
Resolve, RCXPro, Autodesk Smoke 2013 are included in that list. Rcxpro allows translation to other interchange formats as well. I’m not saying it’s perfect.
I wish someone would build a conform tool for all formats that works like rcxpro, but it must not be worth it or we’d have it already.
Jeremy
-
[Jeremy Garchow] “So while X needs a bunch of work, it’s already working for certain and specific workflows/applications. “
That’s all well and good, but I have yet to get a sequence from X into 7 without the audio having issues or other random clips come up missing. For example, audio that’s missing from a clip and randomly placed 11 hours down on the timeline. And yes the folks at IA are aware and have been trying hard to fix the issue.
The bottom line is the XML from FCPX. I have yet to hear from a single developer who likes it or thinks it’s good. My suspicion is the timeline design is the culprit, since clips are no longer locked into a direct relationship with a fixed time ruler. Rather, they are linked to each other. Regardless of whether you want OMF or AAF, it still gets back to Apple supplying the developer with a substandard, non-standardized starting point, which is far from mature and still keeps changing.
As far as working well with Resolve, I’ve had issues with those round tripped projects, as well.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “The bottom line is the XML from FCPX. I have yet to hear from a single developer who likes it or thinks it’s good. My suspicion is the timeline design is the culprit, since clips are no longer locked into a direct relationship with a fixed time ruler. Rather, they are linked to each other. Regardless of whether you want OMF or AAF, it still gets back to Apple supplying the developer with a substandard, non-standardized starting point, which is far from mature and still keeps changing.
As far as working well with Resolve, I’ve had issues with those round tripped projects, as well.”
I understand. It’s not perfect. It’s the reason I have stuck to FCP7 for paying gigs.
FCP7 XML didn’t start out perfect either. It took a little while, and it took a lot of developer insight and help. For v1.1, FCPXML is just OK at this point, but it’s v1.1.
And
There isn’t another workflow that is perfect out there. Sure there are better working ones with other NLEs, and they have more capability (such as EDL) but there are still road blocks and hoops to jump through, and these are much more mature applications.
The developers I have talked to don’t like FCPXML either. Along with everything else, it’s just way different than the XML of old.
Plus, it simply frustrating when this stuff doesn’t work.
-
[Jeremy Garchow] ” and they have more capability (such as EDL) “
Someone at ProApps engineering just threw up in their mouth. 😉
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up