Would a Midi Dump Work?

Is it possible to dump the settings of a patch from a MS2000 to the MPC? I want to be able to change the patch for just one beat, i dont want to keep it stored on the ms2000 permanently.

If it is possible......

Last night I put the mpc to the midi screen where it has the dump options, I left the request number at 0. The MS2000 says that its completed but the patch changes back to the original after turning the ms2000 off and back on.

i think you wanna do a sysex dump, yo need to set the synth upto send the data, and just sequence it with-in the mpc. then save it as a midi file. why dont you just save the patch, and use program changes and bank messages to access this sound.

nanoloop wrote:i think you wanna do a sysex dump, yo need to set the synth upto send the data, and just sequence it with-in the mpc. then save it as a midi file. why dont you just save the patch, and use program changes and bank messages to access this sound.

I would LOVE to know how to do this.
I really would love to know how to do this.

It's really easy I used to do this with my 3000 & XL

7 1 4 Beats wrote:It's really easy I used to do this with my 3000 & XL

What settings do you have to set on the MPC?

does anyone know if this is possible on the 500 or the 1000 models as well? I want to transfer my sounds from my cd3000i to one or the other I am still deciding what i want

this thread is long dead, but i'm using a microkorg (same specs and dump procedures as the ms2000..) and i do this all the time and its **** GREAT! I don't have to store patches on the korg and every song has every tiny tweak already loaded up on the synth with the song.

here's the thing: you want to dump only a single program to the mpc. also, you want to have this dump done onto an empty track (ie, not the track where you've actually recorded the midi performance fro your synth). the reason for this is that sending an entire patch to the synth takes about a second, and everytime your sequence goes around, the jam is gonna lag for as long as it takes to transmit the patch to the synth..... Also, make sure you have 'receive exclusive data' or whatever enabled on the mk. otherwise it'll ignore what you dumped into the mpc when it sends it back at the mk.

So yeah, set up a seperate track that's just gonna be a spot to store your patch. Go to that track in step edit. Hit overdub. Dump your single patch. You won't see anything in step edit unless you push exit and reenter step edit or hit the bar < button. you'll see an exclusive message in step edit. thats your patch (its "exclusive" b/c it means nothing to the mpc though the mk will know what to do with it). now anytime you want to load all those weird little settings back to the mpc, you can either just play back that track with the exclusive message, or play back just the message itself from step edit. Make sure that storage track has the proper midi out and all too. Then go to another midi track you want to record your performance from and rock out (make sure you don't have any pc set for the midi performance track..) Of course it goes without saying that you need to send that exclusive message to the synth everytime you load the sequence since the patch is stored on the mpc and not the mk.

nanoloop wrote: why dont you just save the patch, and use program changes and bank messages to access this sound.

I'm with this post. SYSEX dumps have their uses for backup/file rearrangement purposes but it's a slow, tempermental and fragile standard to work with. Also, some manufacturer's SYSEX is not compatible with certain MPC models and has a tendency to cause weird, undesirable behavior.

I'd really never want to mess with SYSEX dumps during a live performance -- but there's no need. Switching patches in the synth with PC/BS messages is a billion times faster and more reliable.

Still cant get this to work. Could there be an issue with the sysex and the mpc 2000?