MPC5000 reviews, bug reports and fellow user support on the most recent standalone, hardware MPC from Akai
By colonyrecords Fri May 09, 2014 6:59 pm
I feel the need to share this, not sure if someone has already pointed this out.

I have had my 5000 for about 3 years now and it has always had bad midi clock. My last hope was to purchase the innerclock sync gen (not cheap) to resolve the issue. The sync gen helped with the midi jitter but still couldn't fix the random midi clock start delay the 5000 has. The sync gen fixed all midi clock issues with my other equipment except the 5000. I was just about to give up and sell the 5k when I thought to try an older OS (1.02). Mines came with 2.0 so I never even thought about any other OS's. After loading 1.02 I can say the 5000 now syncs perfectly when using midi clock, no more random midi clock start delays. How could akai screw up midi clock so badly with the 2.0 OS, didn't they check this stuff before releasing it.

Long story short, if you are pissed off about bad midi clock on the 5k downgrade to os1.02. Only problem is you will lose a lot of features but for my uses having a functioning midi clock was more important.
User avatar
By wavemartian Sat May 10, 2014 3:40 am
I know! I wanted to try this myself. So i put OS 1.02 on, made a 2 bar beat, no problems, did it three times. Put OS 2 back on, and back to funny business. It seems like when the click gets to 1.00 position it momentarily stops, then gets a push to catch up, the thing is, it is bloody RANDOM which is the biggest pain. In all honesty, there will not be an update, as so many members in the past have pleaded for. Even JJ can't help us. i feel the pain
By colonyrecords Sat May 10, 2014 10:19 am
I think I will just live with OS 1.02. I will miss multi pad editing but not sure what other features are gone.

I can't prove this but I swear this has something to do with the issue. On the mpc the timeline unit at the top ends in 3 digits .xxx . When os 2 is midi clocked all three digits count upwards. With os1.02 when it is midi clocked, the last digit e.g .xx(x) isn't used only the .xx digits. It's like os 1.02 knows to drop the sequencer resolution (maybe to 96ppq) when midi syncing. That's my theory anyway, not sure if it makes sense.

Can you check this behaviour on your 5k?
By colonyrecords Sat May 10, 2014 10:24 am
Man I don't think I would ever buy another akai product after this 5K experience and the level of support they give to their customers, I just can't see myself ever supporting the company in the future.
By colonyrecords Sun May 11, 2014 1:26 pm
Just can't win with the 5k. So now with os1.02 it syncs to midi clock perfectly but I have a new issue. If I hit the rec buttons while already syncing to midi clock (seq already playing), it starts to skip timing. This means I have to program everything on the mpc before even attempting to sync with midi clock. My goal was to sequence on the mpc while also working along side the DAW audio tracks.
By CoinOP! Tue Jun 03, 2014 5:49 am
Stop busting balls and let Nukai be!! Yeez!!!

Why distract them from making amazing products like MPX8/16 or Rythm Beast...

Stop it!