Trouble playing back Sys Ex Messages

Hola

I've just gone and got myself a MPC 2500 and I'm finding that it is having trouble playing back system exclusive messages. When it does the machine grinds to a halt or just simply crashes.

Does anyone know why this is happening and how I can fix it?

I would really appreciate any help!

Regards

Richard

What kind of SysEx messages are you traing to play back?

There is something about that in Ch. 5 of the manual.

HI Stilo

It's the set up messages for my two sound modules (Roland JV 1080 and SC 55) before my sequence starts. The same sequences that I am trying to play on the 2500 work fine on my MPC 2000XL and also on my old ASQ 10. It's just the 2500 that doesn't like them.

Had a look in Ch. 5 of the manual but it's a reference to editing Sys Ex messages.

Fudge wrote:Had a look in Ch. 5 of the manual but it's a reference to editing Sys Ex messages.

Well...yes. I thought that's what you are using here?

How did you get them onto the 2500 by the way?

_Stilo_ wrote:

Fudge wrote:Had a look in Ch. 5 of the manual but it's a reference to editing Sys Ex messages.

Well...yes. I thought that's what you are using here?

How did you get them onto the 2500 by the way?

I downloaded the files onto my computer from a SCSI drive and then connected the 2500 to the computer and transfered them via the USB connection.

I've been on to Akai Tech Support today and they didn't have a clue why I'm having problems with Sys ex messages.

I'm not sure, but I guess that simply the 2000XL files dont work on a 2500.

They're standard midi files so in theory they should work on any machine.

I think you're too optimistic there...

Not really; they're not 2000XL files. The SysEx commands he's talking about aren't instructions for the MPC. They're sent from the MPC to his sound modules. It's a standard part of the MIDI spec. It's possible that they got corrupted coming off the 2000XL or the computer.

I'd recommend trying to copy them back onto the 2000XL, and see if they work. First try the version that's already on your computer. If this works, you know that version is OK. Then try the version that's on your 2500: copy that back to your computer, then back onto the 2000XL. If that's bad, I'm guessing that the SysEx files got screwed in the USB copy. You might also comparing the copy you pull off the 2500 to the one that's already on your computer (maybe using this, although I've never tried it). If it comes up different, again, you know the copy you made over the USB connection was bad.

Having said all that, if you repeat the whole damned process, do you get the same result?

Well...I was just saying, if Akai can't manage programming a simple filesystem, while should they do better with standard MIDI?

I would try programming the SysEx messages by hand as described in the 2500 manual chapter I quoted.

I've just done this for my NEW !!!! oh yeah, Access Virus. You load up a MIDI file play it down the wire to the ext device, ext device should start flashing.

Make sure both Ins and Outs are connected to and from device. Make sure that the devices are set to recieve Sysex, in manual of device.


Also check out step edit to see what is in the MIDI file if poss - just to check data is there.

Which ports on the MPC are you using - tried using port 1 in and port A out?

To add a grim note:

I tried to record a sys exe dump into my 2500. I use it with a Korg microX.

I always leave a whole balnk bar before the sequence kicks off with any note data.

I record the sys exe data by starting with the program on the sound module one 'step' away from my desired program, and then, with the 2500 in step edit mode, I turn the microX data wheel one step to my chosen program.

This works, in that the correct data is recorded into the sequence. I know this because I can turn the module one, start from any setup and the 2500 manages to find the right program...eventually, with a horrible stutter, and messing up the sequence. Perhaps there's too much data?

J

Yeah Jonathan, your description is pretty much what is happening to me. I'm now finding that when the MPC plays some Sys Ex messages it actually crashes the modules that it is sending the info to. The sort of data that I'm trying to save is performance stuff like patch, volume and effect settings. Very basic stuff.

Even if I save it straight from the module to the sequencer the MPC just doesn't seem to be handle the info. I've also tried some commercially made MIDI files and the MPC is unable to process them.

As I said I have tried the same sequences on other MPC units and they play fine, only the 2500 can't do it.

Dissapointing that such a simple and basic function is such a problem.

Fudge wrote:Dissapointing that such a simple and basic function is such a problem.

Had this discussion about TI sysex on another board. I've not gotten reliable sysex playback from the MPC2500 although it is one of the few hardware boxes which will record it. I think the problem is you need a bulk sysex mode, not recording sysex strings in a sequence. My Triton Extreme does a fantastic job of sysex dumping in media mode. I think you will find that most hardware sequencers either don't read the sysex at all, or can't play it back without staggering or locking up completely.

Make sure you aren't echoing midi to the device, it might be upsetting it as well.

Not to sound dumb or anything, but what is Sysex messages and how do they differ from regular sequence data?


Thanks!