Problems with OMF import not finding audio?

Question

Level 1

5 points

Problems with OMF import not finding audio?

I've been trying to export five show reels from a low budget feature film I worked on using OMF to migrate from Pro Tools LE v6.4/DV Toolkit v2.0 to Logic Pro v7.1.1. The original files were edited on a Pro Tools III and (at the end) on a Pro Tools HD v5.x system. But the v5.x PT session files all open fine in PT LE v6.4.

I tried AAF export on three different show reels. I tried both AIFF and Sd2 audio file types on these AAF export attempts. Logic says it can't find the audio files and freezes - even though I can see the exported audio files right in the folder I exported them to. I have to force quit Logic just to clear the lockup.

Forced to work with OMF, I’m having problems with OMF import not finding the audio. I’ve tried exporting a consolidated version of the audio, where the audio is part of the OMF file (and under the 2GB total file size limit the OMF spec imposes), and I’ve tried to export just the Pro Tools LE session only, referencing the original audio from/that resides in the Pro Tools LE session audio folder.

I've been successful on Reels 3 (SDII), 4 (AIFF), & 5 (SDII), but I’ve had no success with Reel 1 or 2. There's something weird going on there because it's not consistent.

On Reel 1 and Reel 2 Logic says it can't find the audio files - even though I can see the exported audio files right in the folder where I exported them.

When I go to the desktop and look at/point to the exported audio folders, there's audio there, it looks like the right amount of files in the folder, and the folder size is about right - approx. 1 GB.

But when Logic tells me it can't find the first file, the name it gives/says it's looking for looks like the temp name given to the file during PT/OMF export - not the original file name nor the final renamed Avid Hieroglyphics file name that appears in the final exported audio files folder. For example:

R1315-47-48%20Audio%20519/R1415%47-48%206058n%218aaHOtcSk

Is the name given in the Logic OMF import “File Not Found” dialog box

Whereas:

R2318-47-48 605!2rGaqeRtcSk

Is a sample of one of the names in the actual Pro Tools LE Audio Files folder.

When I point Logic to that folder where the exported audio is located, all the file names are "ghosted out" - they cannot be selected. In fact, even the “open” button itself is ghosted out when the folder - where the exported audio is located - is selected.

In this latest attempt, I even re-opened this exported Reel 1 OMF folder back into Pro Tools LE v6.4/DV Toolkit v2.0 to check the OMF export. The session file and all the associated audio files all imported correctly, with all the file names showing as the names they were in the original PT LE/PT III/PT HD session e.g. “sfx explosion.L” or “Mus-Troy’s Castle.R” – no R2318-47-48 605!2rGaqeRtcSk type of names were present in the audio regions bin.

I’ve gone to the desktop to make sure the permissions on the audio folder and the audio files themselves are all “read-write”. I’ve made sure that Logic Pro is set as the application to open AIFF and Sd2 files.

In the exported OMF Audio files folder there is a file named “msmFMID.pmr” which I believe is the media data base file that Avid and Pro Tools use to “find” the edits and real names of the audio files. These OMF files all open up correctly in Pro Tools.

However, even on the show reels that did successfully open up, no automation translates across, nor did the audio end edits or fades on the music tracks (and probably the other tracks as well – but it was most obvious on the music tracks). According to the OMF spec, these – other, very important - aspects of the mix are supposed to translate across.

Finally, there's still the split stereo re-grouping/re-linking limitations in Logic. Although dragging a fader of a stereo group in latch or write mode writes automation to the pair, grouping does not really re-link the split stereo files i.e. so that any editing done to one - break point automation, fades, trims etc. - does the same to the other side.

This basic type of split stereo editing simply does not seem to work at all in Logic v7.1.1. And it makes it way more time-consuming and not worth trying to use Logic to continue working on this film.

Any suggestions or the nitty gritty truth (that’s just the way it is - this just doesn’t work in Logic etc.) would be greatly appreciated. Thx.

Tone

Dual 2.7 G5 Mac OS X (10.4.6) 4.5 GB RAM, Logic Pro 7.1.1, MOTU 1296

Posted on May 31, 2006 7:03 PM

Reply

Answer 1

Jun 1, 2006 5:24 AM in response to Tone Sanchez

it sounds like OMF version 1 was used to export the first 2 reels. try getting them re-exported and being sure that they are version 2. also there is a slightly known (by me anyway) issue regarding the use of 1) non-alphanumeric commands such as % or $ or £ or & (that sort of thing) and 2) very long file names in OMF.

i use OMF for importing and exporting quite often and only ever have problems with the chaps at the other end. you always have to remember to get them to ignore frame rate, because not all info is saved to the OMF file fom logic. the other thing to remember is that logic does not time stamp the files on export, so the files are in relation to bar 1.1.1.1 or the beignning of your song. therefore when they are imported they are always put in their correct relative position with the start of the PT or avid media composer project.

Reply

Answer 2

Tone Sanchez Author

Level 1

5 points

Jun 1, 2006 9:37 PM in response to Rohan Stevenson1

Thanks for your response.

I used DV Toolkit v2.0 which imports and exports OMF from within the Pro Tools LE application. So I'm pretty sure that it's OMF v2 and not v1. OMF v1 was a stand-alone application that did not require one to open or even have the Pro Tools application installed on the computer.

I exported each one of these show reels myself from PT LE v6.4/DV Toolkit v2.0. I've tried OMF export with consolidated audio and just the session file only, referencing the original audio that is in the associated Pro Tools Audio Files folder.

I don't recall ever using any non-alphanumeric commands as I know that usually makes problems.

As far as very long file names goes, I probably have some names that go to the 31 character limit. However, the three reels that did successfully convert had all the same files and consequently the same file names.

Moreover, OMF changed all the names to the Avid style names - which do have non-alphanumeric characters. But as I said before, so do the three show reels that did import successfully into Logic Pro v7.1.1.

I am not exporting OMF from Logic. I am only going from Pro Tools LE to Logic Pro v7.1.1.

I know that Logic is not using the media data base file that is in the exported OMF audio folder because the file names in the reels that did import successfully all have a default name that references the name of the OMF export.

However, when I re-import that same exported OMF file back into a new PT LE session the names come back exactly as they were in the original PT session. Therefore, I think it is fair to assume that Logic is not adherring to the current full OMF spec.

Any other tips or info you may have regarding the limited way Logic imports OMF would be greatly appreciated.

Thanks for your input and help.

Dual 2.7 G5 Mac OS X (10.4.6) 4.5 GB RAM, Logic Pro 7.1.1, MOTU 1296

Reply

Answer 3

Jun 2, 2006 3:10 AM in response to Tone Sanchez

R2318-47-48 605!2rGaqeRtcSk

the exclamation mark "!" is non-alphanumeric. it is also very long. i believe 7.2 has fixes for problems with non-alphanumeric and very long characters and also for more than a certain number of regions in an OMF file.

i haven't had to import a lot of OMF's - certainly not routinely, but whenever i have, i have not encountered any problems. not so long ago, i had to get a PT session into logic and the PT setup did not have the DV toolkit. we actually managed it by using the old OS9 OMFtool (which i can send you if needs be) and downsaving the PT version. worked perfectly and in classic as well.

Therefore, I think it is fair to assume that Logic is not adherring to the current full OMF spec

it sure doesn't. and it's a bit annoying. eg no control over framerate or timestamping. BUT in general it does work provided you are not giving it anyting tricky.

when you export the OMF, i think you need to check settings that convey information other than just the audio files themselves. i think the 'extra' info is being written to your audio files which a PT app can understand but logic can't. if you disable whatever extra info is being written to the file and make sure you have no non-alphanumeric symbols, and your filename length is a 'sensible' length, that ought to get it to work properly.

finally, when logic imports the OMF it is creating files as you say. i know they are greyed within the finder window within logic, but can you open these files with something like QT and get them to play? because if you can't, then they are corrupted, and that likely happened at the OMF creation phase - though i wouldn't swear to it.

Reply

Answer 4

Tone Sanchez Author

Level 1

5 points

Jun 2, 2006 11:14 AM in response to Rohan Stevenson1

Thanks for your response. Yes, I agree on the long names. I will try OMF export again, this time shortening the OMF export name - that would be the "R2318-47-48 605" part. I have no control over the "!" or any of the other non-alphanumeric characters as that is being done by PT LE 6.4/DV Toolkit v2.0 during the OMF export.

I haven't considered downsaving the file to v4 and trying the old OMF v1. But since automation, fades, pans or anything else are not coming over, it might be worth a try. I think I have a disc or CD with that older version on it. In case I don't, thanks for the offer. I'll let you know on that one.

Does Tiger v10.4.6 still allow "classic" mode? I didn't think so. If not, I'll have to dig up a drive with OS9 on it and try this on my old G4.

when you export the OMF, i think you need to check settings that convey information other than just the audio files themselves. i think the 'extra' info is being written to your audio files which a PT app can understand but logic can't.

Agreed.

if you disable whatever extra info is being written to the file and make sure you have no non-alphanumeric symbols, and your filename length is a 'sensible' length, that ought to get it to work properly.

I'm not sure how to do this. I'm not setting up or requesting anything frrom the OMF export window, just SDII audio.

On this latest attempt, I used an OMF export that I re-imported back into a new PT LE session. Then I exported that session only, telling OMF to reference/point to the original audio. This process actually opened up the other problematic Reel 2. That time, everything came across except the main dialog track. So I re-OMF exported just the main dialog track and imported that OMF file into Reel 2 and that worked out OK.

This next time out I'm going to try to shorten the export name, and export Dialog, Music and Effects separately on 3 different OMF exports. Hopefully, that will work.

, but can you open these files with something like QT and get them to play?

Yes, I can play them right from the finder AND if I double-click one, it opens in Logic - because I made Logic be the default program for all AIFF and Sd2 files - and they play fine from within Logic as well.

Which is why I don't understand why this last show reel is not coming across. Well, I'll just have to try all your suggestions with the ideas they gave me and hope for the best.

Again, thanks for your help.

Tone

Reply

Answer 5

Jun 2, 2006 2:48 PM in response to Tone Sanchez

just for the record i have never managed to make OMF that only referenced material work. it always had to contain the audio data itself.

secondly, you will need the OMF version1 and version 2. and yes classic works perfectly well with tiger. i use it all the time.

Reply