Pulsar 2 MIDI problems

[synthetic88]

I finally managed to get my Scope system up and running. Here's what I have for now:

AMD Athlon XP XP 2500+
Crap VIA mobo
640MB RAM
WinXP SP2
Pulsar II plus card
Scope 4.5

I have the AES in and out connected to my mixer and MIDI out of my MOTU digital timepiece into the Pulsar MIDI in. When I play notes into the system, they seem to get wildly corrupted. A note on might be off by a few octaves, a note off may become a note on, etc. I was looking at the MIDI Monitor and hitting note 60 (middle C) over and over triggers note 00, 56, etc. This is an old card, would it need a hardware update?

Thanks, -jl

[astroman]

imho that looks more like a connection or communication problem.

you may try the following (with a cable known to function)
connect the physical ports (out -> in) of the card with the cable
there's a virtual midi keyboard in Scope's midi menu - load it into a project
connect it in the routing to midi out
connect a midi monitor to midi in
click on a virtual key and look what the monitor shows

cheers, Tom

[synthetic88]

If I connect the Pulsar MIDI In to Out, plug the keyboard to the out and the in to the MIDI monitor, it looks correct. If I then plug in the MIDI out from my sequencer, the MIDI data looks corrupted. I tried a different MIDI cable, different MIDI port on the interface, even took the MIDI cable to another synth that was working fine and plugged that in. Every time the MIDI input is corrupted, unless it's coming from its own keyboard.



Could it be a driver problem or interupt? I have it plugged into the last PCI slot. When it was in the middle slot, it gave me a "Hardware version 16 detected" error, even after reseating the card.

[synthetic88]

MIDI out from an Andromeda also has the MIDI problem.

[synthetic88]

...and aftertouch sometimes becomes program changes.