I am working on a project with a friend who has uses Logic Pro, he sent me all wave files for a project , I then recorded a track and sent it to him. he imported it into his Mac and it doesn’t fit perfectly, the timing is off. After carefully looking at his tracks in Cubase I found they are also off. At the start everything is ok, but as the track proceeds it is increasingly off the quarter note grid… can anybody Help?
Hi,
Do you use the same Sample Rate all the time?
Btw, Cubase sports DAWproject exchange format. If Logic would support our too, it would be easier. 
Yes, same sample rate.
Hi,
Isn’t it shifted by 1 sec by any chance?
no, more than an eight note at 101 bpm, I have a screenshot, but it is not possible to post it here.
Hi,
Did you import the Audio Files to the very beginning of the timeline in Cubase?
Did you set up the L and R Locators correctly while export?
Yes, same tempo on both machines, locators set. I looked at the pool, an there his file have a different tempo 119,81. I don’t know what to think of it. I changed that to the right tempo, but it seems weird. why would a DAW export a mix down of a project and embed false tempo information?
Yeah the initial thought which came to mind was some kind of tempo down to a fractional / decimal place. Obviously both Cubase & Logic can support this, but unlike Cubase, Logic keeps the decimal points hidden from view.
In the case of what you have written above, if you have a session set precisely to 119.81, then Cubase will show that in the transport window down to every last digit. Unfortunately, Logic rounds up or down to the closest whole number and hides the precise BPM from view!
In other words, if I type that bpm within Logic:
As soon as I hit enter the value immediately displays as:
So that’s the first part of consideration. The second part is that Logic usually has smart tempo and “flex time” operations turned on by default. So when a user drags loops etc that set to various BPMs, it will fix it to play at the same rate.
The way Logic most likely would’ve gotten such an odd fractional BPM is if he started the session using a loop at that BPM (such as you noticed in the pool). I believe that Logic will automatically adapt the session to this first added clip. But this is just conjecture at this point, there could’ve been other reasons.
I would recommend that you ask him to doubleclick the tempo field in his transport as I showed above – doing so will reveal the exact tempo down to the decimal if there actually is one – because like I said, Logic might be rounding up or down.
It might help at least to investigate. If it’s nothing to do with that, I would further look into any time warp settings on either end - in your session and in his (Logic calls it flex time). It’s possible any hidden time mapping which is done inside the project is not being exported in the back and forth resulting in timing issues.
1 Like
