AKAI MPC5000 Software Release Notes

Yo! I really wanted to purchase the MPC5000 but the Just Blaze comments and a few others really detered me. I ended up buying a computer but making music on computers just ain't for me. I figured by now AKAI had did a few updates so I contacted them and expressed my concerns. Below a copy of an email they sent me and software release notes. If you own an MPC5000 and have these updates is the machine still buggy or did AKAI address the issues.

(Email Reply from AKAI)

The MPC5000 is tested rigorously each and every day to help iron out anything reported to us. There have been 2 firmware upgrades since the release and I have attached the release notes on all specific items that were fixed.

Anytime an issue is reported to us we are quick to inform our engineers and get it resolved.

Is there any particular feature or issue you may be worried about? Unfortunately there can be a lot of misleading information in forum posts and I’d be happy to clear up any concerns.

Feel free to e-mail me anytime you have a specific question and I’ll be glad to answer.

Thank You,



AKAI MPC5000
SOFTWARE RELEASE NOTES
Version: 1.02
Date: 8/05/08
New features/Changes:
1. Additional support for manufacturing.
2. MIDI Transport commands are now sent when received.
3. Fixed loading MPC2000 Programs.
Bug fixes:
1. Fixed issue where FINE LOOP window was actually FINE TRIM window.
2. Fixed a memory leak in disk mode causing the unit to freeze after heavy disk mode usage.
3. Fixed bug where FULL LEVEL was not correctly represented in OTHER-PAD page.
4. Fixed bug where Solo "S" not being maintained when soloing an audio track
5. Fixed bug: After assigning a new recorded sample to a pad, the previously assigned sample's name that
has been purged shows as being assigned again with no sample.
6. Fixed Bug: Excessive auditioning of HD samples creates a corrupted AUDTION file and eats up RAM
7. Fixed Bug: Track not activated when notes are recorded until track is reselected
8. Fixed Bug: used in MULTI mode, midi input to both A and B causes sounds to cutoff or sustain
9. Fixed Bug where recording 2 Songs and playing back first one loses HD and CD
10. Fixed Bug: Unable to playback audio from NOW time of measure 255
11. Fixed bug where hardware revision letter was off by one in Diagnostic Mode.
12. Fixed problems selecting MUTE and SOLO in Track Mixer.
13. Fix problems in STEP and GRID edit, where note variation value was not correctly limited.
14. Fix problems with importing/exporting MPC1000 format programs related to note-to-pad mapping and
velocity to pitch setting.
Version: 1.01
Date: 4/30/08
New features/Changes:
4. Additional support for manufacturing.
Bug fixes:
15. 'Selected Pads:' and 'Mode:Replace' doesn't replace not selected pads.
16. MMC Record and MMC Exit Record do not work properly.
17. Gate at 1% in Arp Mode sounds the same as gate at 100% for steps of 1/32(3) or higher.
18. Samples assigned to L & R of paired individual outs cutting each sample OFF.
19. When recording with TC OFF, early first note ends up in second measure.
20. Crash in main mode, only on MIDI port C.
21. Stereo monitoring not being updated after recording a mono sample.
22. Values will jump to current knob settings without touching knobs when messages sent to MIDI C or D.
23. Pitch Shifting & Auto Chopping a wav sample corrupts play pads.
24. Start note only played once in a looped sequence when last note overlaps the loop.
25. Possible Crash at 95% CPU usage and above.
26. PAN resets on loop boundary for synths.
27. Sound from one sequence hanging after going to the next sequence.
28. Possible crash when using Q-link controllers.
29. No MUTE indication for mute automation.
30. Voice stealing in SYNTH mode: clicks and crackles.
31. START and END settings in FINE not consistent with range numbers after pressing TRACK.
32. Unable to record mix changes after UNDO.
33. Punching In the numeral digit to next SEQ freezes the Now: time count b4 hitting the enter button.
34. Digital noise when punching back in AFTER end of song.
35. Upon boot up the UNDO light comes on when loading onboard ROM set.
36. Trim changes made in the FINE window can't be auditioned directly.
37. Disarming track while recording (with intention to punch out) and rearming track while continuing to
record (with intention to punch in) loses initial recording.
38. Screen freezes when viewing a nonexistent event type when playing.
39. Metronome still sounds when punching out in HD record mode.
40. Overwriting HD Tracks to CF Card doesn't generate the overwrite message.
41. Touching any function button while unit performs long pitch shift type operation could interrupt the
process.
42. Last sliced sample of Auto Chop is always distorted upon playback.
43. Overwriting multiple tracks generates multiple overwrite messages to HD.
44. Recording new HD Tracks over previous ones doesn't totally erase the old sound data.
45. Unable to turn off MUTE for audio tracks.
46. Progress bar non-functional for certain streaming engine tasks.
47. MIDI transpose not working properly.
48. Qlinks set to MIDI Channels causing random playback.
49. Samples being rerouted to individual ADAT out of next pressed pad.
50. When overwriting .ALL file and reloading it, any tracks recorded over still have original recorded notes
on them.
51. In the 'Loop Measures' window, 'Total Bars' does not calculated correctly when 'Last Bar' = 'End'.
52. No progress bar to indicate CDRW is being burned or erased.
53. Jerky playback of automated Continuous Sample Track or long sample.
54. Frequency parameter in Frequency Shifter effect can not be returned to zero.
55. Original file chopped and converted as sliced sample takes on end time of region 1.
56. Significant sluggishness on scrolling thru grid edit on long sequences.
57. HD recording input has crackles on the right channel.
58. TRIM and LOOP endpoints can be unsynced, causing editing errors.
59. SOLO missing on MPC in TrkMIX SONG mode.
60. HD automation not followed when started and stopping song.
61. Streaming Engine progress bar only goes to 50%.
62. Transpose should have a destination pad, not an amount pad.
63. Renaming sequence does not update the display correctly
64. Viewing inserted real-time step edit events clunky.
65. When discarding, deleting, or extracting, sample endpoints are off by 1.
66. Disk mode folders are not correctly alphabetized.
Version: 1.00
Date: 3/7/08
New features/Changes:
1. Initial Release.

IMO ... most of the cats at NUAKAI dont even really know how to work a MPC, even the new ones they got. A lot of the stuff that you may call about, they have never tried, so basically, the person you are talking to doesnt use the machine like we over here would use them(some of us, as our everyday job). Make music off a computer, depends on what ya doing. I know me, i luv my drums from the MPC, and keys from elsewhere. But theres no other way for me, The MPC or no other way at all. The 5000 is ok, its not everything i was hoping for, but it does do mostly what its supposed to do, check the bug thread for more info at the top of these 5000 threads to see what they still need to fix.

But as a MPC user, their are different MPC's for different needs. Check and make sure, this is what you want, or if its another one that you are interested in. But definitely, a MPC for me, no other way... Im rocking two since i dont wanna sell my 2000XL

Anytime an issue is reported to us we are quick to inform our engineers and get it resolved.

I can t believe it !!

Is that a joke ?

I already adressed them more than one issue & most of them are still not resolved !!

there can be a lot of misleading information in forum posts

One more joke ?

They d better read the forum, they ll find a lot of things to improve their machine !!

tomazzzi wrote:

there can be a lot of misleading information in forum posts

One more joke ?

They d better read the forum, they ll find a lot of things to improve their machine !!

Your both right here, there really is a lot of misleading but true stuff going on in these forums. For a person looking to see if the 5000 is right for them it may look bad, but akai needs to be reading those same post so they can fix it and wont have to worry about on lookers seeing stuff like that on forums.

there can be a lot of misleading information in forum posts

I believe 95% of the v1.01 bugs listed as 'fixed' in the above list were first spotted and reported on this forum. It's a shame some people feel the need to undermine the massive job we're doing here - tech support, pre-sales advice, free bug testing, the list goes on...

So true....

Now i begin to understand why people are so angry about NUKAI team ....

Looks like a bunch of noobs that doesn t listen to their customers at all & think WE ARE the noobs !

Listen to me AKAI just learn how to use your machine then you ll find there s a lot of stuff to improve & still a lot of bugs to solve !!!!!

Anytime an issue is reported to us we are quick to inform our engineers and get it resolved.

Pure lie !

I reported like 10 issues with full descriptions of the bugs & how to reproduce.

They only soved one !

They only answer to emails when you r about to buy but once you have bought & need help NO answer anymore !!

( i never been agressive, impolite or something like that in any emails i sent them, every emails were fully detailled to help them the most i can )

Anyway it s still a great machine with a lot of fun playing with but please AKAI DO YOUR **** JOB & don t lie to your potential customers just to sell your beast.
Also you d better look on this forum CAREFULLY you ll find a lot of USEFULL infos especially on the bug reports & feature wishlist threads.

MPC-Tutor wrote:I believe 95% of the v1.01 bugs listed as 'fixed' in the above list were first spotted and reported on this forum. It's a shame some people feel the need to undermine the massive job we're doing here - tech support, pre-sales advice, free bug testing, the list goes on...

justin baro and akai customer service are both quick to say that the forum is full of "misleading information."

that's like Dell saying that CNet is bogus.
these folks just don't like to be faced with their flaws.

Personally, I believe there is both good and bad information about the 5K in this forum. I would say that 90% of the bad info being written about the 5K in these threads are from people that don't own or use the 5K. The few users here that own and write about the 5K here have done an outstanding job of sharing factual information. I just hope it continues. I am sure Akai/Numark will continue to improve the OS of the 5K.

I would love to own the 5k!

I've always thought that it was a great looking machine ever since I first layed eyes on it.

If only the price can come down a bit then I will happily buy into it.

what up earlobe i gotta say im kinda pissed at your username aite one

Askia Shaheed wrote: I would say that 90% of the bad info being written about the 5K in these threads are from people that don't own or use the 5K.

you are probably right.. but as tomazzi said, the ones who akai listens to are those people. not the ones who own them.



Anyways, it's clear that akai's priorities is with selling people any damn thing whether its physically flimzy or buggy software wise.

Seriously though, besides all the bugs and what ever, I think for almost 3 thousand dollars, they could have made it in a metal case. metal is not that expensive, and even if they added an extra 50 bucks... people would spend that extra for an aluminium case. I mean they will spend the cash on black pads, blue screens, and other crap.

they could have made it in a metal case. metal is not that expensive, and even if they added an extra 50 bucks... people would spend that extra for an aluminium case.

The case is already metal but they should have made the knobs & qlinks better.

mr_debauch wrote:

Askia Shaheed wrote: I would say that 90% of the bad info being written about the 5K in these threads are from people that don't own or use the 5K.

you are probably right.. but as tomazzi said, the ones who akai listens to are those people. not the ones who own them.



Anyways, it's clear that akai's priorities is with selling people any damn thing whether its physically flimzy or buggy software wise.

Seriously though, besides all the bugs and what ever, I think for almost 3 thousand dollars, they could have made it in a metal case. metal is not that expensive, and even if they added an extra 50 bucks... people would spend that extra for an aluminium case. I mean they will spend the cash on black pads, blue screens, and other ****.

This is the mis-information I am talking about. The case of the MPC 5K (as well as most MPCs before it) is metal with the side panels being plastic. The MPC 3000 is this way and so is the MPC 4000. Pretty much all workstations are built this way. Making the 5Ks side panels out of metal will do nothing but make it heavier. Its already weighing it at 18 pounds (8 kg).

Are you sure your own/use an MPC 5K?