Huge amount of midi data: Pulsar 2 crashes

[JyGius]

Hi all!

I have a pulsar 2. Whenever the midi in of my pulsar 2 receives
a lot of midi data (active sensing or sySex)... my system crashes....
I tryed of lot of things with no results.... Likewise,
I can't record sySex into my sequencer. When I start the sySex dump
on a hardware synth I see the midi led flashing (into cubase) but when I hit record cubase records nothing. After a couple of minutes my system crashes...

I tryied to raise up the PCI Latency Timer from 64 to 96.

I have no irq conflicts.

Any idea?

Many thanks.

[garyb]

you'll likely have to use a different interface for sysex, or slow the data...active sensing must be filtered. sorry...

[Paulkaiju]

Same problems here (SFP 3.1).

Lots of Midi, it all freezes but the midi and sound Jams up.

Maybe need to lower the latency or it's just my Pulsar 1?

Maybe you need to uncheck sysex in Cubase > MIDI filtering? It's usually checked.

A few year ago I was sucessful in updating my Korg's (Ms2000) firmware via scope.

I recently tried updating another synth and it failed.

[astroman]

in Sounddiver this could be fixed by slowing down transfer rate.
I'd also suggest an external midi interface - it's a reliabel solution and only a few bucks instead of endless trial and error
but PCI latency is not related to 'latency' at all - it only means the maximum duration of the time slice for which a device may occupy the bus

cheers, Tom

[JyGius]

Hi all!

Yes, but if I load a midi sysEx file in cubase I can load it in
my external synth using the physical midi out of my pulsar with no problem.

Strange...


Many thanks guys