Reviews and questions about the entry-level MPC500
By ADSR Fri Jul 04, 2008 5:48 pm
maybe i just dont get it or maybe i have been spoiled...

i love my MPC200. it is the center of my entire synth studio and has been for a while. i know that machine inside and out, and program changing on my MPC2000 is a breeze. i bought an MPC500 cause i have been doing a lot of traveling and, while i like it and it does what its supposed to do, i seem to be frustrated by its little limitations more then i should be. i have been hooking the 500 up in place of the 2000 when i get back into the studio, but it does not do program changes of external synths on the fly like the 2000 (or does it?), and it does not save the program change as part of the sequence like the 2000 (or does it?). the 500 manual is VERY limited in regards to program changes, but it is a huge part of my music making with the MPC being the backbone of my studio. is there a way to change programs on the fly and am i missing something in the saving of sequences? please help...i have been doing the synth thing for 2 decades and i cant believe that Akai would not make something so easy in its older models so difficult in its newer ones.

thanks
By brazeca Fri Jul 04, 2008 8:36 pm
According to MPC500's midi implementation chart, it can transmit and receive program change data.

I am not sure about whether MPC500 saves program change messages into .seq files or not. But in the step edit mode you can insert program change events into your sequence tracks, with program numbers starting with 1 and ending with 128. So, it does do program changes. And it works with my microkorg perfectly.

I think, since it is possible to insert PC events, then they should be saved in .seq files as well. You may try saving your MPC 500 sequences as standard midi files: they must contain PrCh events, if there are any.

Also, check midi channels settings on tracks in MPC 500 sequences, where PrCh events are supposed to be. Maybe they are being transmitted via wrong channels and don't go to the right destinations... And you may also wanna double check midi implementation charts for your synths. Some devices (made by Korg, for instance) have program assignments with numbers 0-127. So, to have the expected sound to be selected, when inserting a PrCh event into a MPC 500 sequence, you have to add 1 to the program number stated in the synth's patch list. Again, it works with my microkorg.
By ADSR Sat Jul 05, 2008 12:30 am
thanks, brazeca...

i understand how program changes work on the 500, but it seems that i have to stop playing the sequence, go change the program from the 500, and then start the sequence again to see how it sounds. if it does not sound right, its back to square one. on the 2000, i can scroll through program changes on the fly right from the main screen while the sequence is playing. this is especially helpful when i am triggering a drum kit from my drum machines and want to compare. i understand there will be limitation on the 500 (with the screen especially), but i want to know if i am missing something in trying to do the changes on the fly while the sequence is running...
By brazeca Sat Jul 05, 2008 10:11 am
Not at all, ADSR. Now I see what you were up to :)

Yeah, MPC 500 is kinda limited, I totally agree. And, in comparison with older MPCs like 2000 it is quite unsophisticated, when it comes to MIDI sequencing. It can't transmit MIDI Time Code signal, for instance, only MIDI Clock, which makes it impossible to sync it as master to advanced DAWs like Logic or Cubase. And you have to stop the sequence which is playing before you can make any detailed MIDI-editing in step mode. So, you'd better adjust your workflow a bit when working with it.

Anyway, it is a wonderful MPC, only because you can put it in your backpack or in a laptop bag and make beats everywhere. It's something which is impossible with the 2000, is it?