6 Replies Latest reply: Feb 11, 2008 8:50 PM by Ronnie Pudding
frmrt Level 1 Level 1 (10 points)
I output an OMF of my DVCPRO HD project from FCP 5.1.4 without any issues. The sound mixer received the file, but insists he cannot work with it (in Logic/FCP 5) because it came from an Avid system.

I've never used any Avid products on this project (or elsewhere). Any ideas where the problem is? (Except for questioning the sanity of the mixer--I've already done that.)

Thanks,
David

Mac Book Pro, Mac OS X (10.4.11), FCP 5.1.4
  • Shane Ross Level 8 Level 8 (42,460 points)
    FCP does not import OMF files, so he cannot import the OMF file on his end. And I am not sure that Logic supports OMF import either. I'd pose this question on the Logic forum.

    I have no issues with OMF export for ProTools.

    Shane

  • loyed256 Level 4 Level 4 (2,265 points)
    I believe somewhere around Logic 6 they added OMF support. I'm with Shane in that no problems with OMFs to Pro Tools. FCP doesn't have any export options for OMF like Avid does so you don't really have any choices upon export which really makes it a no-brainer on your end.
  • frmrt Level 1 Level 1 (10 points)
    Thanks to the both of you for the informative replies. It's good to know I wasn't hallucinating when I was doing my edit on FCP. (The sound mixer had actually sent an e-mail to the director and myself saying "you edited this film on Avid, can you please convert it to Final Cut." Bizarre!)

    Regards,
    David
  • Ronnie Pudding Level 2 Level 2 (415 points)
    I've run across this before. My guess is that the sound mixer, for some reason, saw "OMF" and associated it with Avid's media file format instead of seeing it as an audio OMF.

    Why an audio engineer would do that, I have no idea.
  • Shane Ross Level 8 Level 8 (42,460 points)
    OMF stands for Open Media Format. Avid exports this format, as does FCP and a few other NLEs.

    Shane

  • Ronnie Pudding Level 2 Level 2 (415 points)
    Understood. But where FCP's native media format is Quicktime, Avid's is OMFI. When I ran into this same issue, it was because the audio engineer assumed I had sent him Avid-digitized media files instead of an audio output.

    Of course, this same audio engineer tried to open my Final Cut 5 project on Final Cut 4.5 and told the producer that the file I'd given him didn't work. After I'd told him it was a Final Cut 5 project. Go figure.