Sysex, Multitrack and tempo

Hi there.
Got a Mpc1000 a week ago. Looks real cute next to my Access VirusC synth.
I have a lot of songs/sequences that I made for the Virus in Cubase Vst32 5, and I want these to be played from the MPC1000 instead. The most easy way I found out to do this, is exporting the cubasefile (*.all) as *.mid, and load them in the MPC. In the *.mid file I have a track with the sysex-info. When I play back the sequence from MPC, the first 4 bars contain sysex. The thing is, after the sysex-info has been sent, the MPC runs through the next 4-5 bars VERY fast, before slowing down again in bar 10-11. From here, everything works fine (multitracks, sequence etc).
Is seems like the sysex-bars stalls the MPC.
Because of the stalling I have to put in blank bars before the actually song begins. Has anyone found a way to fix this?

... the thing is, that I have tried also to record a midi-dump of the sysexinfo directly from the virus-synth to the mpc. When I play back the RECORDED sysex-info from mpc, the timing works fine! But when I play the transferred sysex (*.mid), the mpc stalls a bit and then skips the next couple of bars. So maybe there is a way, I can optimize the *.mid so the timing-problem doesnt occure?

Moogens wrote:Because of the stalling I have to put in blank bars before the actually song begins. Has anyone found a way to fix this?

I've been doing that anyway, I don't see it as a problem. I'm not sending out major SysEx dumps (yet), so I can't say what's happening there, but I naturally put program and control changes in a short Sequence before the rest of the song. Seemed logical to me, I want all devices set up and ready before the song itself starts...

Thanx. Its not a big problem. Weird though because the recorded mididump (which also is about 4 bars long) should contain the same sysex-info as the *.mid-file. Could go into exploring the sysexdata - but dont think its easy

4 bars of SysEx? Are you sending out whole patch banks? If you're limiting it to just the patches you're using, then it can't be helped, since I think a SysEx dump is one Event in MPC1000 terms.

I'm not doing SysEx yet, as I said, but I think what I will do when the time comes is:
- My Kawai K5000S can play 4-part Multitimbral, a Multi spec is 4 Patch numbers + some MIDI, level & pan info. The most I can use at any one time is 4 Patches + 1 Multi, so I will dedicate fixed Multi and Patch numbers for them, and save each of those for each song as small SysEx dumps.
- If I need to change the sounds in the middle of the song, that means more SysExes, so it will pay to keep them short.
- My Korg DL8000R delay will only use a few patches per song, so that also means a few patch dumps to catch.

That's what I will try, anyway, but I could be wrong ... damn this day job!

Nope, I send a dump of the arrangement I use in the song: a multiprogram of 16 single programs (sounds). In that way I dont have to be worried about missing some of the single programs in the Virus-synth (could have been erased or overwritten by mistake). I dont use all of the 16... maybe 6-8, but I have to dump all 16.

Ups, no... Found out I can set parts unused to off in the Virus. That makes the sysex smaller.