OMF/FCP import/export mess: Why is DP mangling OMFs?

Digital Perfomer in the context of television/film scoring and post-production.

Moderator: James Steele

Forum rules
This forum is for discussion related to the use of Digital Perfomer in the context of television and film scoring and post-production.
Post Reply
dix
Posts: 3029
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Francisco
Contact:

OMF/FCP import/export mess: Why is DP mangling OMFs?

Post by dix »

I'm normally I'm a composer, but offered to mix a friend's short film. The OMF created from FCP that he sent was an unusable mess. I've mixed a few films before and the Embedded OMFs that showed up were usually fine, with pans, fades etc. intact. This one had nothing to do with the picture (all kinds of garbage on it - multiple scene takes, slates etc). I had sent him the spec sheet that I've used before (provided by audios - thx!), but clearly there's something more he needs to know. I'm not familiar enough with FCP to know what to tell him. Does anyone know what I could tell the editor to get him on the right track?

Here's audios's spec sheet, but I have a feeling there's some other FCP operation that needs to be done before doing the OMF export.?

Thanks!
-------------------

For OMF exports

Picture Elements

Quicktime movie in H.264 that includes dialog only audio in 16/48K AIFF MONO.

- It should have a head and tail 2-pop
- Program should have 5 seconds of black prior to first audio or first picture.
- First video or “black” should start on the hour @ 01:00:00:00
- Time code window should start running at 1st frame on the QT movie.
Timecode can be drop frame or non-drop frame as your project stands now. Just indicate the frame rate on the packaging or email communications. Ideally the visual burn-in of timecode is located at the very top of “Title safe”.

Audio Elements

- OMF type 2 (Embedded)
- 300+ frame handles
Last edited by dix on Fri May 20, 2011 6:04 pm, edited 1 time in total.
14-inch MBP M1 Max (2021), 13.6.x, 64GB RAM, UAD Quad Tb Satellite, 4 displays ::: 2009 4,1 > 5,1 MacPro 12-core 3.33 ghz , 10.14.x, 96GB RAM, GeForce GTX 770 , NewerTech eSATA/USB3 PCIe Host Adapter, UAD-2 Quad, ::: 15-inch MBP (2015) 10.14.x, 16GB RAM ::: Lynx Aurora (n) USB ::: DP (latest version), Vienna Ensemble Pro danwool.com
User avatar
MIDI Life Crisis
Posts: 26256
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: OMF/FCP import/export mess

Post by MIDI Life Crisis »

If it were me, the first thing I'd do is ask him to make sure of the type of OMF (it seems you have covered that as type 2 but you want to make sure he knows what he's doing.)

In the event he is totally in the dark, or there is a system incompatibility of some sort, you might request a 'checker boarded' set of tracks to work from. I've used this method on high end projects in the past when the systems just did not want to talk to each other.

Basically, he will provide audio tracks that are on separate tracks (usually 3 or 4). Then you can mix is and deliver a stereo aiff and with the 2 pop and end pop as reference, he should be good to go.

Why is it that 'professional favors' ALWAYS end up being the most difficult tasks to accomplish? Never fails. And it usually ends up that the people who get you to do the favor for zero dollars are the most demanding in the end and second guess everything you do? OK, that's off topic, for sure, but is it really? I'm not so sure. It seems to me that people who pay you because they respect you as a professional extend that respect (for the most part) into the collaborative process. Not always, but more often than those who don't want to pay you seem to be quick to try and beat you down for the stupidest things.

Yeah, I've got a few axes to grind and will never work for free again. EVER! The only exception is that I will 'barter' with fellow artists who have skills I can use or collaborate where I am a producer with a real back end or something of value to gain. But favors such as these are a thing of the past. It took a long time to realize just how much time and energy they waste, and frankly, if I am going to waste time at all, it will be with my buds and not with the leeches. IOW: it's either a pro setting or I'm not playing.

:)
2013 Mac Pro 32GB RAM

OSX 10.14.6; DP 10; Track 16; Finale 26, iPad Pro, et al

MIDI LIFE CRISIS
barreltone
Posts: 159
Joined: Thu Oct 21, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Denver
Contact:

Re: OMF/FCP import/export mess

Post by barreltone »

Doing the OMF export from FCP is a pretty simple process, so I would be surprised if he is missing a step. He may just have a lot of garbage in the timeline.
Is it possible that the "handles" (300+ frames is like 10 seconds on either side, of course) he provided just made for some junk within the OMF?

Or is it possible that he had a different timeline open and gave you an OMF of the wrong one?
Mac Pro 8 core Nehalem,OS X 10.6.8, MOTU 896HD, DP 7.24, Finale 2009, MSI, Izotope Trash, Spectron, Ozone 4, Alloy, Rx2
User avatar
zaratero
Posts: 453
Joined: Tue Aug 05, 2008 4:50 pm
Primary DAW OS: MacOS
Location: Gasteiz

Re: OMF/FCP import/export mess

Post by zaratero »

My biggest issues lately have been related to fade ins and disabled clips in the FCP timeline. Some systems had to reactivate (or delete) all disabled clips that contained a fade. Those fade times would add up making the the sync and the OMF useless after a few of them delaying everything.
http://www.cueaudio.org
Macpro 3.1 Octocore-16Gb RAM-OSX10.8 - DP 7.24
Macbook pro Core2Duo-4Gb RAM-OSX10.6 - DP 7.24
dix
Posts: 3029
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Francisco
Contact:

Re: OMF/FCP import/export mess

Post by dix »

Thanks. Clearly, the editor is newer than even I am to all this, so these responses might help him find a clue.

barreltone, I don't think it's the handles that are the problem. I'm hearing entire takes sequentially on the tracks ("scene 1 - take 1, scene 1 take 2…"). It's much more than a sync/drift issue. More likely a different timeline was exported. I was thinking there might be a Consolidate Project step that he left out. ..dunno.

I'll probably take another stab at an OMF and also have him give me the tracks rendered with head and tail pops - what MLC calls checkerboard tracks I think (although I'm not sure why it's called that). However, one of the reasons I took on the favor is that I'd like to get more serious about film mixing and reckoned this'd be a good guinea pig, so I'd like to do it the "right" way as much as possible, using conventional standard procedures. That was the idea anyway! :)

Thanks again.
14-inch MBP M1 Max (2021), 13.6.x, 64GB RAM, UAD Quad Tb Satellite, 4 displays ::: 2009 4,1 > 5,1 MacPro 12-core 3.33 ghz , 10.14.x, 96GB RAM, GeForce GTX 770 , NewerTech eSATA/USB3 PCIe Host Adapter, UAD-2 Quad, ::: 15-inch MBP (2015) 10.14.x, 16GB RAM ::: Lynx Aurora (n) USB ::: DP (latest version), Vienna Ensemble Pro danwool.com
User avatar
MIDI Life Crisis
Posts: 26256
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: OMF/FCP import/export mess

Post by MIDI Life Crisis »

It's called checker boarding because the cues alternate like the red and black of a checkerboard. When a cue in track A ends the cue in track B starts, etc.

Cal your guy export an AAF? I've has good results with those in DP.
2013 Mac Pro 32GB RAM

OSX 10.14.6; DP 10; Track 16; Finale 26, iPad Pro, et al

MIDI LIFE CRISIS
dix
Posts: 3029
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Francisco
Contact:

Re: OMF/FCP import/export mess

Post by dix »

I've never worked with AAFs. Is there an advantage over OMFs? Is it any simpler on the export end? Thx!
14-inch MBP M1 Max (2021), 13.6.x, 64GB RAM, UAD Quad Tb Satellite, 4 displays ::: 2009 4,1 > 5,1 MacPro 12-core 3.33 ghz , 10.14.x, 96GB RAM, GeForce GTX 770 , NewerTech eSATA/USB3 PCIe Host Adapter, UAD-2 Quad, ::: 15-inch MBP (2015) 10.14.x, 16GB RAM ::: Lynx Aurora (n) USB ::: DP (latest version), Vienna Ensemble Pro danwool.com
User avatar
MIDI Life Crisis
Posts: 26256
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: OMF/FCP import/export mess

Post by MIDI Life Crisis »

My understanding is that AAF files compute fades and other data but it is more than that. The OMFs I get also seem to comoute fades so it is a little confusing. From here:

http://www.joyoffilmediting.com/?page_id=329" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;
AAF. Advanced Authoring Format created by the AAF Association, a trade organization, and beginning to be used by editors working on digital systems. An expanded OMF, an AAF contains EDL information plus audio and video media as well as metadata and data on an increased number of complex effects and titles and can operate with a variety of different media types such as QuickTime and MXF. Avid, Quantel, and other manufacturers’ proprietary information can be encoded in the metadata for exchange only within the manufacturers’ equipment.
From the same site (before you ask... ☺ ):
EDL. Edit Decision List. The EDL contains the reel number and time code numbers for each edit in the final offline cut, the EDL is used to recreate the offline cut during online. It is used by the online editor to conform the show.
2013 Mac Pro 32GB RAM

OSX 10.14.6; DP 10; Track 16; Finale 26, iPad Pro, et al

MIDI LIFE CRISIS
dix
Posts: 3029
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Francisco
Contact:

Re: OMF/FCP import/export mess

Post by dix »

Okay. This appears to be a DP issue.

I reexported the OMF from FCP and got the same awful results when I imported the file into DP (I even tried importing into DP6 and DP5), however the OMF opens in Logic just fine. From Logic I can render discreet tracks I suppose, but I'd lose the handles.

Does anyone have any further ideas as to what the problem could be? It is a rather large OMF. 1.9gb with a ton of audio files. DP seems to be not recognizing the audio file names correctly. Files with completely different names from different parts of the project often sound identical. A soundbite marked "debbie dia" and "ocean fx" sound exactly the same for example. Why is DP goofing this up so badly?

Thanks!
14-inch MBP M1 Max (2021), 13.6.x, 64GB RAM, UAD Quad Tb Satellite, 4 displays ::: 2009 4,1 > 5,1 MacPro 12-core 3.33 ghz , 10.14.x, 96GB RAM, GeForce GTX 770 , NewerTech eSATA/USB3 PCIe Host Adapter, UAD-2 Quad, ::: 15-inch MBP (2015) 10.14.x, 16GB RAM ::: Lynx Aurora (n) USB ::: DP (latest version), Vienna Ensemble Pro danwool.com
dix
Posts: 3029
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Francisco
Contact:

Re: OMF/FCP import/export mess: Why is DP mangling OMFs?

Post by dix »

Bumping this. I'm still hoping to iron this out in DP. Has anyone else had DP mess up OMFs on import like this?

Thanks.
14-inch MBP M1 Max (2021), 13.6.x, 64GB RAM, UAD Quad Tb Satellite, 4 displays ::: 2009 4,1 > 5,1 MacPro 12-core 3.33 ghz , 10.14.x, 96GB RAM, GeForce GTX 770 , NewerTech eSATA/USB3 PCIe Host Adapter, UAD-2 Quad, ::: 15-inch MBP (2015) 10.14.x, 16GB RAM ::: Lynx Aurora (n) USB ::: DP (latest version), Vienna Ensemble Pro danwool.com
barreltone
Posts: 159
Joined: Thu Oct 21, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Denver
Contact:

Re: OMF/FCP import/export mess: Why is DP mangling OMFs?

Post by barreltone »

Sorry, dix, but I've never had this happen with an OMF. And I've pretty much only opened OMF's from FCP. Admittedly, I just upgraded to DP7 pretty recently and I haven't tried with that, but every OMF worked flawlessly for me in DP6.

Did you export it yourself from FCP, or did your friend?
Mac Pro 8 core Nehalem,OS X 10.6.8, MOTU 896HD, DP 7.24, Finale 2009, MSI, Izotope Trash, Spectron, Ozone 4, Alloy, Rx2
dix
Posts: 3029
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Francisco
Contact:

Re: OMF/FCP import/export mess: Why is DP mangling OMFs?

Post by dix »

Thanks.

I didn't export this second OMF myself, but I was present when it was output, so I'm sure it was the correct timeline.

It's a PIA, but the workaround is to open the OMF in Logic and then output another OMF (as mentioned above, OMFs from the project open in Logic np). The Logic-generated opens in DP correctly.

Still no idea what's going on here. Could it be that DP doesn't like OMFs that are so close to the 2gb limit?
14-inch MBP M1 Max (2021), 13.6.x, 64GB RAM, UAD Quad Tb Satellite, 4 displays ::: 2009 4,1 > 5,1 MacPro 12-core 3.33 ghz , 10.14.x, 96GB RAM, GeForce GTX 770 , NewerTech eSATA/USB3 PCIe Host Adapter, UAD-2 Quad, ::: 15-inch MBP (2015) 10.14.x, 16GB RAM ::: Lynx Aurora (n) USB ::: DP (latest version), Vienna Ensemble Pro danwool.com
Post Reply