Can you fell 96 tick resolution ?

For example in 120BPM is minimal resolution between notes about 10ms. From my experience you can notice such a time if you play on soundcard with 5ms in and 5ms out interface. But this is live and sequencer is sequencer. So can you notice any unprecise timing on MPC1k sequencer due to 96tick? Can this be issue if you record for example Piano where you can feel every rythmic nuance ?

jura13 wrote:For example in 120BPM is minimal resolution between notes about 10ms. From my experience you can notice such a time if you play on soundcard with 5ms in and 5ms out interface. But this is live and sequencer is sequencer. So can you notice any unprecise timing on MPC1k sequencer due to 96tick? Can this be issue if you record for example Piano where you can feel every rythmic nuance ?

You're confusing latency or inaccurate triggering with resolution

Have a look at these threads

http://www.mpc-forums.com/viewtopic.php?t=22746

http://www.mpc-forums.com/viewtopic.php?t=6697

Isn't there another issue here:

Resolution vs. Accuracy -> -Within- each tick, how consistent is the timing.

For instance, say I just want 4/4 kick drums on my mpc1000. Now, if I put them right on the beats, how much jitter will come between them? It's not enough just knowing that resolution is 96ppqn... because, are those kicks coming consistently at the _beginning_ of each tick?
Or jumping all around within that 5ms interval?
Just knowing the spec. of 96ppqn doesn't tell you that fact.
Only Akai knows for sure, or we could do our own tests with recording wave files.

Not to mention, probably for triggering samples inside the mpc, its more consistent than for sending midi.

That's why someone could claim that one 96ppq sequencer is 'tighter' than another. Also that's why most pc midi timing sucks, unless you're using some fancy timestamping interface. See, even though cubase whatever might be editing notes down to the 480ppq, once you send out the midi/usb there is drift and jitter so your delay might be even more than 5ms!

Quick background-- midi clocks are sent at 24ppqn...which allows 32nd note triplets. The MPC has 4 times more resolution with 96ppqn.

It's downfall, is if *you* play with a swing, then the 96ppqn may not be accurate enough to record the notes, and play them back, exactly where you intended. This is not to be confused with the MPC's "swing" feature, which actually moves clocks around to get that "feel".

It is not a latency thing (though I understand your analogy was made just to point out that 10ms can be heard), but *can* be a +/-5ms thing if you play that far away from the nearest timing pulse (ppqn). If you play right on the timing, then you shouldn't notice it.