MPC5000 reviews, bug reports and fellow user support on the most recent standalone, hardware MPC from Akai
User avatar
By SimonInAustralia Sat Oct 05, 2013 5:08 pm
ntalec wrote:Let's make it even funnier.
When they were releasing the 5k they threw us a 4k update bone the same way.
So to help the 5k release they made us think we would get a 4k update.
Then to help the Ren release they made us think we would get a 5k update.

Wasn't there some threat of a lawsuit from 4k users to try and get it updated, or promised features added, or something, that lead to Akai having to contract someone else in to program the OS?
User avatar
By Dj Khayos Thu Oct 10, 2013 11:46 pm
Doc333 wrote:So I am reading "beatmaking on the mpc 5000" and just read about the "attack bug" where the MPC REDUCES attack the harder you hit a pad. Is there a patch/fix for this. I assume the work around would be resampling the pad at different volumes with ASDR adjustments then play them at FULL ON, but that seems like a lot of extra work.


Can someone make a video showing this bug, and feel free to show other bugs too.
User avatar
By damien907 Tue Oct 22, 2013 9:10 am
is this bug always in effect, or can you use the mpc without running in to it?

i think i have asked you this before tutor, but i cant recall what the answer was.

is it whenever you hit a pad that this automatically happens, or do you have to go into a certain mode to have this happen?

i would think that if it always happened, the thing would be pretty much useless wouldnt it?
User avatar
By MPC-Tutor Tue Oct 22, 2013 10:29 am
It's a permanent bug, always happens, the V>Att is just set up incorrectly. I've always imagined it's simply a case of the coder accidentally using a '>' instead of a '<' in the code, basically a very quick and easy fix that would have literally taken 5 minutes for them to sort out.

And yes, it makes that feature completely useless on the MPC5000. To my knowledge there is no workaround.

The reason I keep going on about this is that it is so frustrating - such an easy thing to fix yet they couldn't be bothered to spend an hour or so fixing it and deploying the update on their site. It's like they were saving up all the bug fixes for another 'grandstanding' update, but never got round to it.
User avatar
By Jauly Tue Oct 22, 2013 4:21 pm
MPC-Tutor wrote:It's a permanent bug, always happens, the V>Att is just set up incorrectly. I've always imagined it's simply a case of the coder accidentally using a '>' instead of a '<' in the code, basically a very quick and easy fix that would have literally taken 5 minutes for them to sort out.

And yes, it makes that feature completely useless on the MPC5000. To my knowledge there is no workaround.

The reason I keep going on about this is that it is so frustrating - such an easy thing to fix yet they couldn't be bothered to spend an hour or so fixing it and deploying the update on their site. It's like they were saving up all the bug fixes for another 'grandstanding' update, but never got round to it.


Maybe we should scream all together "hello AKAIIII, can you hear us!?" ;)

The more I think about the very strange behaviour of AKAI is that they think if they don't look (close) at the bugs they hope they're not there (->"mythical user-gossip"). Like when kids close their eyes to make something bad disappear.

LOL

So what if we offer Akai to pay like 50 bucks for the 5 minute fix of the attack bug? Why shouldn't they do it?
User avatar
By damien907 Sat Oct 26, 2013 5:13 am
ok, so let me get this strait. i thin there is a little misunderstanding.

you have to go into a certain mode for this bug to be in effect, and if i dont use that certain mode, it doesnt happen right?

what exactly do you have to do to make the bug happen?

i assume its not just always happening, for example, if i turn on my mpc, load up a sample to pad a1 and play a pad a1 it should just play pad a1 like every other mpc right?
if it were always happening, then you couldnt even really make a beat out of the thng because the harder you hit any pad, the more the front of each sample gets faded out right?

so my question is, can i just avoid that certain mode like the plague and be good? i just wont be able to use that feature right?

how exactly do you re create this bug?
By Doc333 Sun Oct 27, 2013 9:15 pm
It's subtle. I would think if yr playing at Full level, it plays the sample as is. But if you turn it off, the attack bug is in effect. I think one way to work around it is to make 2 copies of the sample, one at full level and untouched, the other version is at a lower level and with the asdr adjusted. Takes longer especially if u want a lot of them, but if u want just like one, with a second as a "ghost note" its something u can do.
User avatar
By damien907 Thu Oct 31, 2013 11:12 pm
ah ok, thanks for clearing that up. damn, that makes me really not want anything to do with the 5k. i feel like there was so much potential that they just threw away.