Transfer from Pro Tools to Logic using OMF/AAF

In PT consolidate the audio files from the first bar and get the tempo of the song. Then in Logic create a new session and enter the tempo. From the PT audio folder drag the newly created audio files into the Logic session. During this process you will be asked if you would like to use the names of the files when transferred!

I hope this helps!

**** straight this is a huge pain! My logic Pro 7.2 doesn't even let me find the AAF audio files but just says the drive, directory etc isn't valid and i have to skip each file. What sort of works is this...
From ProTools export a MIDI track, an AAF file AND an OMF... that's right ALL THREE! Open logic and first open the midi file. Then IMPORT the OMF file, then import the AAF file. You have to skip all the 'locate audio file crap' one by one with the AAF import but what that gives you is all the automation which mysteriously gets laid in the right place ON TOP of the audio regions that came in with the OMF!?!?!? What you don't get is the correct region names from the original PT session but you get the regions (not correctly named) the track names AND the automation. Totally FREAKY but it works!
Don

Don't have a work around, just the same problem. OMF and AAF give different results - both unusable. The last OMF (from Avid MediaComposer) puts the regions at the right place according to relative timecode. But if the OMF is exported with handles, the region plays from the START of the audiofile - instead of keeping the handle length before and after the relevant part of the region. And even worse; the audiocontent was summed on each track, instead of separated..... I verified the OMF in other applications, and everything worked out well. ProTools with Digitranslator was my choice to get the job done.
The AAF-file from Avid made a whole bunch of new tracks in Logic, but did not import the audio (from a embedded file).

Two years ago I went frustrated away from Logic to continue a film postproduction on ProTools instead. I've been using Logic since its early stages - then C-Lab Notator 1.0 in 1988. I love the application, but when it came to OMF, postconforming and timestamped files from locationrecorders - I had to give up. Logic was not at the mark. And with 7.2 I thought these task finally was implemented....

Isn't the OMF and AAF-routines in Logic pass the Beta-stages yet?

the last time I tried this in digitranslator, it worked fine. Unfortunetly, I forget the exact settings that I used, but I converted a PT session file to an OMF, and then copied the folder with the OMF and all of the audio files onto my hard drive.

Imported the OMF (not open, use import) within Logic, and everything was exactly lined up where it was supposed to be and correctly named.

Where did you get the demo of digitranslator?

The problem is that OMF does not give you the correct region names or the automation. AAF gives you all of that but it doesn't work properly. So far the long winded method i described in my previous post is the best I can find but still the regions are not named correctly. When you ad complex (or any) tempo maps into the equation life gets very much harder with all of this.

"Isn't the OMF and AAF-routines in Logic pass the Beta-stages yet?"

Exactly! This is ridiculous! No one cares about importing garage band sessions. how many people really do that anyway? i don't know ANYONE! But EVRY pro using Logic wants the OMF/AAF thing fixed! Without this Logic can't be called PRO as it cannot be a part of the pro audio universe.
Just crazy!

I guess it will work the way you describe, because the OMF is just functioning as a EDL with clip information. The audio you use is the same (original) files as PT. But the problem starts when a video facility send you a OMF-file where the audio are embedded; iow. one file contains all data - but "packed". I believe the unpacking process of this file in Logic make the error in some cases (or always...). We use embedded files because of the filesize. Sending all the digitized audiofiles for a filmproject could be a huge amount of unneccesary data, especially when sending files online.

I got my Digitranslator demo by borrowing an iLok from a Digidesign dealer. Don't know if the demo is possible in other ways (except when you newly installed ProTools 7 and activate a valid demo when booting).