DAW/midi timing issue?

Hi everyone,

I've noticed that when using my MPC as a slave to my DAW's clock, and I record a sequence, the sequence doesn't start at the exact time I've programmed on my MPCX.

For example, my first snare hit might be on 1.01.012, but on the DAW, it might be 10-15 ticks early or late.

This has happened on both Protools and Reaper. It happens everytime. It's never triggered at the exact time I have programmed in the MPC, I have to manually go back and slide notes into the correct place on my DAW.

Since it happened on both Protools and Reaper, I have to think something is set wrong in my MPC (?).

Any insights would be greatly appreciated. Thanks!

Hmm I record everything into the mpc them record back into my daw

You could that just seems like a double step .. wait 2 minutes export then another 2 minutes to import.. you can create and record in at the same time IDK old school I guess..

Lamp! Always respect u been that dude since I joined.. I should have explained more I use maschine as a vst and MPC X as standalone.. when i use it i record into my DAW then convert then convert to audio.. better for mixing and adding my custom efx.. when I use analog I still do it the same way.. the software is the same and Cubase is a beast of a DAW.. I wasn't looking at timing of so yes I have not had that problem with network midi driver?

have you tried running a pre-roll /count in, older mpcs prefered this method the get the timing tight from the start of song otherwise it could take a bar or 2 to stabilize, clock in the live isnt great at being slaved tho sp maybe as good as it will get

Caustic Yoda wrote:have you tried running a pre-roll /count in, older mpcs prefered this method the get the timing tight from the start of song otherwise it could take a bar or 2 to stabilize, clock in the live isnt great at being slaved tho sp maybe as good as it will get

That's funny because in Maschine is exactly the other way around it. Crazy we still got issue with MIDI

Maybe it will all change with MIDI 2.0 >>> https://www.midi.org/articles-old/detai ... y-exchange
Extract from link above:
JR Timestamp:
Can MIDI 2.0 provide more reliable timing?
Yes, and not only that the timing for MIDI 1.0 can also be improved. One of the new messages that can work with both MIDI 1.0 and MIDI 2.0 are Jitter Timestamps.

When will AKAI introduce MIDI 2.0 is the only question....

EDIT: ...my KORG M3 sends continuously MIDI clock signals. If the M3 is Master you can see on MIDI monitor in the MPCX the incoming clock "ticking".

[email protected] wrote:Hi everyone,

I've noticed that when using my MPC as a slave to my DAW's clock, and I record a sequence, the sequence doesn't start at the exact time I've programmed on my MPCX.

For example, my first snare hit might be on 1.01.012, but on the DAW, it might be 10-15 ticks early or late.

This has happened on both Protools and Reaper. It happens everytime. It's never triggered at the exact time I have programmed in the MPC, I have to manually go back and slide notes into the correct place on my DAW.

Since it happened on both Protools and Reaper, I have to think something is set wrong in my MPC (?).

Any insights would be greatly appreciated. Thanks!

First of all, how do you have everything set up? Are you running your MPC in standalone mode and synchronizing MIDI clock via Ableton Link wirelessly? Are you using MIDI cables and treating your computer DAW as a separate piece of hardware? What audio interface are you using? What is your sample buffer and sample rate set at in your DAW? What MPC are you using and what firmware is it on?

In the PT or Reaper find how many samples it's late, then set your offset to counter that. If it's 700 samples late, then in PT or Reaper, set your offset to -700. The new MPC's are .5 ms to .10 ms off when slaved and that can vary depending on your MIDI interface and how long your MIDI cables are.

But as stated above, give it 1 to 2 bars of blank space to catch up. (Even with the offset.) But to avoid of that, export the stems and bypass all that. Other options, buy a MPC 4000 or 3000 or get a stand alone MIDI clock generator like ERM Midiclock+ MIDI Master Clock.

[email protected] wrote:Hi everyone,

I've noticed that when using my MPC as a slave to my DAW's clock, and I record a sequence, the sequence doesn't start at the exact time I've programmed on my MPCX.

For example, my first snare hit might be on 1.01.012, but on the DAW, it might be 10-15 ticks early or late.

This has happened on both Protools and Reaper. It happens everytime. It's never triggered at the exact time I have programmed in the MPC, I have to manually go back and slide notes into the correct place on my DAW.

Since it happened on both Protools and Reaper, I have to think something is set wrong in my MPC (?).

Any insights would be greatly appreciated. Thanks!

DeaDeus wrote:Maybe it will all change with MIDI 2.0 >>> https://www.midi.org/articles-old/detai ... y-exchange
Extract from link above:
JR Timestamp:
Can MIDI 2.0 provide more reliable timing?
Yes, and not only that the timing for MIDI 1.0 can also be improved. One of the new messages that can work with both MIDI 1.0 and MIDI 2.0 are Jitter Timestamps.

When will AKAI introduce MIDI 2.0 is the only question....

EDIT: ...my KORG M3 sends continuously MIDI clock signals. If the M3 is Master you can see on MIDI monitor in the MPCX the incoming clock "ticking".

It could be easier for Akai make the multi MIDI IN. If they make the switch to 1 to 1 track architecture they could still work with older MPC program with the bidirectional communication. I'm not sure how it works I imagine it will be easier the communication box to box. So the new Akai architecture could easily read the old one by MIDI. Does it work like this?

TheDoctor wrote:It could be easier for Akai make the multi MIDI IN. If they make the switch to 1 to 1 track architecture they could still work with older MPC program with the bidirectional communication. I'm not sure how it works I imagine it will be easier the communication box to box. So the new Akai architecture could easily read the old one by MIDI. Does it work like this?

Yes, as I understand it - downgrade compatibility is guaranteed by the MIDI team. The bidirectional connection might not be part of it, as this is something the hardware must understand and able to handle. Bidirectional communication can only work if the transportation of data is flowing simultaneously - else we have new jittering.

Multi MIDI in is independently to the MIDI standard - it is entirely a software to hardware issue. If I see the CPU load on the MPCX in a complex composition with a lot of different samples and external instruments, I doubt that multi MIDI is possible for the MPCs to handle this without a huge issue of jittering.
I used for about 11 years the Yamaha RS7000 - rock-solid midi, but no multi MIDI channel recording - but I never missed it, as it is not part of my workflow.
As the MIDI people mention that this new functionality of "Jittering Timestamps" can also be implemented in MIDI 1.0 there would be a slight chance that even than the MPCs are able to handle this.
- But I am not a SW or HW developer (only a musician...) therefore my opinion is personal only and might be wrong...
Jittering is to my understanding the major issue for AKAI - the off-beat sweeping is clearly audible - and as mentioned in another thread, some people even use this as a artistic trick to "destroy" a rhythm (maybe just because they do not know any better )