Bug reports & end-user support for Akai's MPC Software 'controllers' including the new MPC Studio 2, the MPC Touch, MPC Renaissance & original MPC Studio and MPC StudioB lack.
User avatar
By MPCWeapon1 Sat Apr 28, 2012 10:45 pm
xparis001 wrote:
e9000k wrote:The 1000/2500/5000 range of MPC's has serious beat clock sync issues. - you probably have seen this already: http://www.innerclocksystems.com/New%20 ... 0Midi.html

This makes using the MPC as slave unusable, one of the reasons why I sold the 5000 and went onto 4000. <<< OS Update :)

Can you please confirm the new MPC software will slave to Pro Tools accurately via Beat Clock.

I would be looking to run MPC soft alongside Pro Tools HD and sync via Beat Clock. The reason for this is that I want to run the AUDIO OUT of MPC soundcard into my HD Interface to be able to capture the 3000 sound.

Thanks.

E


lol, you've stumbled into a hobby obsession of mine...

this page has more data, and comparisons of other manufacturers:

http://www.innerclocksystems.com/New%20 ... itmus.html

the ren software will be capable of slaving to Midi beat clock, yes.

that being said, if you run the mpc as a plugin, the timing will be sample accurate, though I see why you'd want to do it from one to the other, too.

regarding the page you sent, I've seen that before, and while it's a legit test for timing, it's not really much of a litmus as far as a real-world situation.

The MPC5000's timing is actually the tightest of all the mpcs available. this page makes it look like the 3000 is. the 3000 is tight, yes, but here's why this test is inaccurate.

an MPC4000 uses midi for all of its communication from the sequencer to the voice engine. what this means is it's all linear. If that same test was conducted using 10 tracks of 16th note high-hats, all sent out individual mono outs, the 4000s timing would be affected, simply because its playing linearly, one event at a time. conducting this same test using a 4000 and a 5000, the 4000's highhats would start to flam, but the 5000s would stay right where they are.

another factor is processor speed. while yes, an MPC3000 internally isnt linear eventwise, if you put 32 events on a single clock position, you get the flam effect. The more you pile into the sequencer, the more lagging it gets.

but that isnt necessarily a bad thing, however. All of these factors add up to how a sequencer feels. People love how a 3000 swings. people say when they mute tracks on their 3000 it doesnt "feel the same". these are all deciding factors in how a sequencer "feels". perfect example is actually on this list, the TR909. People always say how sampling it doesnt do it justice and you need to have its sequencer because its "feel" is so good. looking at the numbers, apparently the famous 909 feel is just god-awful timing.



This makes sense of my 4K experience.

Good work.
By e9000k Sun Apr 29, 2012 9:12 pm
I have recorded a demo of what the sync with beat clock generated through innerclock sync lock device and MPC4000 sounds like

thats both clicks PT and MPC playing simultaneously

you can hear a flam on the first click, thats the split moment it takes for the devices to sync up. It does not happen again until you stop PT and hit play it again, ie looping around a few bars is not an issue as its continuous.

MP4K___PT10_Sync.wav - 2.8 Mb