Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Native OMF export support needed

  • Native OMF export support needed

    Posted by Oliver Peters on July 9, 2012 at 5:02 pm

    There is currently no reliable way to get an export of OMF. AD broke after the first update. No native support. No direct third party support. Xto7 has had an ongoing battle with the nature of FCP X’s XML files. So my translations have been spotty where audio is concerned. Apple really needs to step up to the plate on this one. Either fix the stupid XML files or build in native support. And no, Roles isn’t the answer, except as a last resort.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

    Michael Gissing replied 13 years, 10 months ago 15 Members · 52 Replies
  • 52 Replies
  • Shane Ross

    July 9, 2012 at 6:31 pm

    [Oliver Peters] ” No direct third party support.”

    Oliver…surely you know about X2Pro…

    https://www.x2pro.net/

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

  • Oliver Peters

    July 9, 2012 at 6:33 pm

    [Shane Ross] “X2Pro…”

    That’s only AAF. Not OMF.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Shane Ross

    July 9, 2012 at 6:36 pm

    OK. And ProTools works with AAF. Trying to export to another audio app that doesn’t have AAF support? Older ProTools (I know those audio guys can be running ancient hardware and software)

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

  • Oliver Peters

    July 9, 2012 at 6:53 pm

    [Shane Ross] “Older ProTools (I know those audio guys can be running ancient hardware and software)”

    Older ProTools version.

    But, my bigger point is that by leaving this to third parties to solve, Apple effectively washes their hands of any problems. They simply aren’t taking ownership of a problem that’s in their court – namely a functional XML interchange. On one hand, they want us to believe they value the pros, but on the other, they don’t tackle the pro users’ requirements very well.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Shane Ross

    July 9, 2012 at 7:01 pm

    I have long given up the notion that they care about us broadcast pros. They don’t include the tools we need to collaborate and get done what needs to be done. By leaving it to third party people, they are washing their hands of us.

    And yes…I know Bill will come in and say how many broadcast shows he has done with FCX. Fine, it works for him and a handfull of other people for broadcast stuff. But the high end pros they are touting…LEVERAGE…couldn’t do a dang thing with FCX if it weren’t for third party support. And it’s not like Apple will add this later, like they did with early versions of FCP where we relied on the Duck to export right. They won’t do it.

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

  • Lemur Hayop

    July 9, 2012 at 7:06 pm

    I feel your pain. X2Pro only works with three specific versions of Pro Tools: 8 with Digitranslator, 9 (full product), and 10. That leaves the other 101 audio sequencers out of the picture, including crucial apps such as Logic, Cubase, DP, Nuendo, Sonar, etc. OMF was essentially universal, AAF not so much so, and X2Pro extremely niche.

    There’s nothing that can be done. Third parties and hackers apparently aren’t interested in this aspect of video post-production. X2Pro is all we have. Red Giant just bought Singular Software (Plural Eyes) so who knows where audio is going. Rumors say Logic X is supposed to integrate more with FCPX but that’s hearsay and it might not be that good after all.

  • Craig Seeman

    July 9, 2012 at 7:15 pm

    [Oliver Peters] “Older ProTools version.”

    Tangential but that points to Avid’s problem
    (runs and hides now)

  • Oliver Peters

    July 9, 2012 at 7:17 pm

    [Craig Seeman] “Tangential but that points to Avid’s problem
    (runs and hides now)”

    What? For making an industry-standard product?

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Craig Seeman

    July 9, 2012 at 7:24 pm

    [Oliver Peters] “What? For making an industry-standard product?”

    Many professional users of Avid products don’t upgrade. It’s just one small part of their current financial situation. A lot of Pro Tools users were outraged at the hardware upgrade costs.

  • Shane Ross

    July 9, 2012 at 7:25 pm

    How is that Avid’s problem? This is an OLDER version of ProTools. The new ones work fine with AAF. The old ones only did OMF. And the current version of Avid exports older OMF, or newer AAF…thus ensuring compatibility with older versions.

    Apple drops old tech before old tech is ready to be retired. NO TAPE CAPTURE? How do they possibly think that no one captures tape, or outputs to tape today? That’s how out of touch they are.

    They are catering to the DSLR crowd who keep importing and trying to edit the H.264’s native and then complaining that it doesn’t work…because they don’t bother to learn anything about how the NLE works. That crowd is HUGE…the tapeless and direct to web crowd is HUGE…so Apple is now catering to them. Not broadcast professionals. So why broadcast pros continue to try to use an app that isn’t designed for their workflow needs is beyond me.

    Whatevs

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

Page 1 of 6

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy