MPC tempo clock off?

Weird problem I've run into:

When I'm tracking MPC tracks onto Logic for Mac, I set the bpms in Logic to equal the bpms in the MPC. For ex., 160 on both. But my tracks have been a little off beat lately.. Like I had to adjust the tempo in Logic to 160.070 to match the 160 bpms in the MPC the other day. Any thoughts on this?

Thanks! J.

timestretch should fix that... have you tried inserting some 'chase' time?

try a bar or two, hopefully that helps...

Hmm.. chase time.. what exactly do you mean by that? What I do is record each track along with the first four count-in clicks, then cut each right before the first click and line them up precisely.... I'd be interested to know what you mean by chase time though.. thanks! J

mctravel wrote:Hmm.. chase time.. what exactly do you mean by that? What I do is record each track along with the first four count-in clicks, then cut each right before the first click and line them up precisely.... I'd be interested to know what you mean by chase time though.. thanks! J

Sometimes midi needs to catch up so if you have 4 bars, record 8 and use the second 4....It should be in time be then....It depends though!!!!

mctravel wrote:Weird problem I've run into:

When I'm tracking MPC tracks onto Logic for Mac, I set the bpms in Logic to equal the bpms in the MPC. For ex., 160 on both. But my tracks have been a little off beat lately.. Like I had to adjust the tempo in Logic to 160.070 to match the 160 bpms in the MPC the other day. Any thoughts on this?

Thanks! J.

That's normal, since the MPC tempo resolution only goes to one decimal place (tenth of a beat) but the computer is precise to two or three decimal places (hundredth and thousandth of a beat). I run into that all the time. Just adjust your computer's bpms until it is tight on the grid... it will make your edits tighter.

Ah.. cool.. thanks alot!

I have the same problem with SX. The clocks are just different, no two clocks will be the same. Just adjust the tempo in Logic so it matches.