Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By kuniklo Mon Nov 05, 2007 2:41 am
mpc sysex bug?

My mpc is hanging on sending sysex. To reproduce:

1. record a sysex patch dump from a synth (I'm using a Nord Lead 2x)
2. play it back

Everything works ok.

3. Go into step edit mode.
4. Select the sysex event.
5. Hold down edit, then press move.
6. Move the sysex message to start on a bar boundary, like the beginning of the first or second bar.
7. Go back to the main screen.
8. Hit play again.

This time, the mpc chokes on playback. From the lcd screen of the Nord it looks like it's sending the sysex message over and over again, in a loop. Can anybody else reproduce this?

Also, it's sending the sysex message even when the track is muted. That's not right, is it?
User avatar

By elektrik_muz Mon Nov 05, 2007 4:09 am
Yeah, sysex is always a tricky issue since almost every manufacturer handles it differently. It gets especially annoying with MPC-type midi database recorders (as opposed to straight-signal-to-memory recorders) because of the extra processing that occurs in between receiving and storing the data. If the receiving device doesn't get the incoming data in exactly the way it thinks it's supposed to, you'll either get nothing as a result or some kind of weirdness as you are experiencing.

My guess is that JJ might need a Nord on hand or some way to reproduce the Nord sysex dump exactly to really get to the bottom of that. If you report it, make sure you make a note of the exact machine you are trying to dump sysex from.

Some sysex stuff works flawlessly with the MPC (DSI evolver for one) others... not so good.
User avatar

By kuniklo Mon Nov 05, 2007 4:44 am
The weird thing is that it works just fine with the nord *unless* I move the sysex event in time. Then it locks up. I'll try it with my Virus and see if the same thing happens there.
User avatar

By arebee Mon Nov 05, 2007 2:50 pm
does it do it if u have the sysex string starting at bar2?

as a word of caution, sysex is so fragile that i would never dump anything so close to the first event in a sequencer, in case it cant buffer it well.....so i use the second bar as a safer option. unles its something particular that u need to happen on the 'down beat' then id avoid having any sysex at the top of a sequencer start.

rB)
User avatar

By kuniklo Mon Nov 05, 2007 4:02 pm
arebee wrote:does it do it if u have the sysex string starting at bar2?


It seems like it's ok wherever I put the sysex as long as I don't move it. Once I move it in the step editor it goes nuts.
User avatar

By The Grublet Tue Nov 06, 2007 2:29 am
I don't even use SysEx, so this may be way off..

but doesn't your Nord think the note 'should be' where it is (on itself), instead of where it actually is (on the MPC after you move it) ???... meaning the Nord is still acting as the master?> or are you routing your MIDI back out of the MPC to control the Nord once you do the dump?

See what I'm saying...? Is it that you have them both trying to be the master? Or are you re-routing the midi in the MPC to control the nord after you dump?... I.E. you just run a MIDI out(A) from the MPC, to the In of the nord, and unplug the cord going the other way temporarily.

Like i said, I could be way off, but let me know.

also, Have you messed with your mono, poly, multi, sysex on/off, etc on the nord?
User avatar

By goobadrum Wed Nov 07, 2007 12:06 am
i don't use sysex either but i thought maybe when you move the info your "bunching up " the data and the synth poos itself.

Why do you have to use sysex ? ,
can't you do what you wanna do with pc or cc?