[Regg Skwarko]

Hello there
I dont know whether or not anyone has actually figured this out yet or if its been fixed in cs6. But for those of you who, like me, doesnt have CS6 and has been tearing their hair out with this problem and can’t google the answer….

I found a solution.

As I mentioned, I was having an extremely frustrating time exporting an OMF from Premiere CS5.5 to ProTools 10, and because I was editing multicam sequences I used nested sequences not realising the dark dark perils that laid beneath.

BUT nevertheless, I found a way out WITHOUT “unnesting”

This is how I did it:

In the project window of Premiere, I selected the desired sequence and right clicked and I chose “Edit in Adobe Audition” and chose “sequence”.

Doing this brings up a dialogue box asking me where to save the file path where Premiere can store and generate its own audio files.
Just so you know Premiere will create its own subfolder with the name of the sequence, so there was no need to create a new folder.

Under the “Selection” bar I chose “Entire sequence” because I had already had a clean timeline with no added bits and pieces.

I chose 5 seconds worth of handles.

I didn’t bother checking “export Preview video” because I had already created a reference picture with 2 sec pip both front and end of sequence for the sound guy earlier on.

And finally, I checked all three
Render Audio Clip Effects
Send clip volume Keyframe Metadata
and to Open in Adobe Audition.

Once thats done Premiere will go ahead and start churning away and then Audition opens up.
From there go to the “File” tab
Go to “Export” and from there you can export either an either encapsulated or referenced OMF.

And VOILA!!
Because Audition is referencing those Premiere generated files you’ll have no problems
well at least my sound engineer hasn’t had any problems so far BUT if he does, I be sure to keep you updated, but in the meantime, feel free and nest all the sequences you want! 🙂

I hope this helps

Cheers guys
🙂

[Regg Skwarko]

Hi there,
I’m having the same problem.

Until Apple comes up with a fix in their updates, in the meantime, rather than Control G-ing it, or shifting the timeline to the right of the gap etc, try highlighting the gap and hitting the delete key.
Its no “right click => close gap” but its something.

Cheers