This discussion is archived
349 Views 6 Replies Latest reply: Feb 11, 2008 8:50 PM by Ronnie Pudding
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.
ShaneDual 2G G5, 3.5GB RAM, Powerbook 1.67ghz-1.5GB RAM, CalDigit S2VR Duo 1.5TB, Mac OS X (10.4.11), AJA Kona LH, Matrox MXO, 2.0TB Dark Tower SATA Raid, FCP 6.0.2
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.G5 dual 2.7, Mac OS X (10.4.6), Final Cut Pro and (dare I say it) Avid.
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!)
DavidMac Book Pro, Mac OS X (10.4.11)
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.G4, Mac OS X (10.2.x)
Dual 2G G5, 3.5GB RAM, Powerbook 1.67ghz-1.5GB RAM, CalDigit S2VR Duo 1.5TB, Mac OS X (10.4.11), AJA Kona LH, Matrox MXO, 2.0TB Dark Tower SATA Raid, FCP 6.0.2
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.G4, Mac OS X (10.2.x)