Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Final Cut –> Protools via OMF

  • Final Cut –> Protools via OMF

    Posted by Lou Borella on June 15, 2010 at 1:12 am

    I’m sending a FCP sequence to a ProTools suite via OMF.
    For some reason ProTools is not seeing the rubberbanding.
    All of the edits are there but the automation is not showing up.
    I don’t understand why this wouldn’t work. The options are there in the export dialogue for Levels and Pan but my audio engineer is not seeing the automation when he creates a new session.

    Is there a minimum Protools version needed? I’m using the latest FCP.

    Is there another way to get to Protools from FCP that will included the automation?

    Thanks in advance
    Lou …

    Lou Borella replied 16 years, 2 months ago 5 Members · 8 Replies
  • 8 Replies
  • Shane Ross

    June 15, 2010 at 1:17 am

    [Lou Borella] “Is there another way to get to Protools from FCP that will included the automation? “

    Automatic Duck Pro Export. But OMF from FCP 6 and 7 should work. Dunno about the version needed of ProTools. is it old?

    Shane

    GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
    Read my blog, Little Frog in High Def

  • Lou Borella

    June 15, 2010 at 1:22 am

    I have to ask the audio engineer what version he is running but I don’t think its old.
    Maybe a version behind but not ancient. Either way its not working.
    I don’t know if its a FCP bug or a Protools bug. I don’t even thing the automation shows up in Logic when I open the OMF on my machine. (I’m going to double check that now)

    I don’t think I should have to buy automatic duck for something that is supposedly build right into FCP.
    (The check boxes are right there in the export options!!)
    Will XML work?
    What about going to SoundTrack first and then to Protools?

  • Shane Ross

    June 15, 2010 at 1:25 am

    [Lou Borella] “I don’t know if its a FCP bug or a Protools bug.”

    Well, not FCP. I export OMFs to ProTools all the time. hundreds of times a year. No problems.

    [Lou Borella] “I don’t think I should have to buy automatic duck for something that is supposedly build right into FCP. “

    Right, just giving you the other option.

    [Lou Borella] “Will XML work? “

    No, because you need to embed the audio. Only OMF does that.

    [Lou Borella] “What about going to SoundTrack first and then to Protools? “

    That doesn’t sound right at all.

    Trash your FCP prefs and try again.

    Shane

    GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
    Read my blog, Little Frog in High Def

  • Jeremy Garchow

    June 15, 2010 at 3:08 am

    Does your first audio clip have any automation?

  • Michael Gissing

    June 15, 2010 at 3:34 am

    The OMF spec doesn’t support dynamic gain (sometimes called rubberbanding). What it does support is basic clip gain, not channel gain changes. Also plugins cannot be exported in an OMF. It is a basic interchange format.

    Automatic Duck does dynamic gain and lots of things that OMFs can’t support.

    XMLs work with Fairlights but I don’t know if ProTools supports it. I suspect not as they are pushing AAF.

  • Shane Ross

    June 15, 2010 at 5:32 am

    [Michael Gissing] “The OMF spec doesn’t support dynamic gain (sometimes called rubberbanding). What it does support is basic clip gain, not channel gain changes”

    Yet, with FCP 6 and 7, I export OMFs that reflect the rubberbanding of audio that I do. So go figure.

    Without the Duck.

    Shane

    GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
    Read my blog, Little Frog in High Def

  • John Pale

    June 15, 2010 at 1:24 pm

    He most likely has a setting wrong in ProTools /DigiTranslator.

    There are several options on how to treat the Automation gain.

    Things are pretty uncomplicated on the FCP side of things, so it’s not likely a problem there

  • Lou Borella

    June 16, 2010 at 10:32 am

    OK I think I fixed this problem (with all of your help).
    I’m not exactly sure what we did but the last attempt at importing the OMF into ProTools worked
    with the automation. I think we switched a checkbox in the import settings in ProTools but we tried so many times that I can’t tell you which setting made the difference. Either way I blame the audio guy (my buddy Steve) for a user error that cost us a few days!!!

    Thanks for the help guys …

    I’m about to post a new topic about FCP to Logic.
    If you have any thoughts please chime in on the new thread.

    Thanks
    Lou …

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