PlanetZ forums - scopeusers.com

dante wrote:Yep thats what the DX7 did after the coffee stain. Yes MIDI was being output, and received in sequencer, but the data itself was garbage. Which suprised me because I thought it never would have made it into the sequencer at all if the MIDI xmission was throwing away rubbish at the hardware level. I know sysex is checksummed, but maybe bad performance data can get through if the key bytes are still coming in 'legal' combinations.

A screenshot of the Scope MIDI monitor would be usefull here.

Several ways MIDI data might become corrupted, especially if using a aged controller keyboard.
MIDI is a electric signal like a clock pulse representing 0 & 1 while interpretation requires a status byte.
Too long cable runs round the edges of the clock pulse beyond recognition as do old electronic components inside the controller keyboard like converters and opto couplers and aged related passive components like caps.
Cheap MIDI cables might cause ground loops and all kind of crossfeed too,- wires not being separately shielded or overall bad shield, cable not being twisted.
Many don´t know there´s a spec existing for MIDI cables and shops sell crap as MIDI cables.
For the basic MIDI, there are only 3 wires incl. the ground needed, but some controllers transmit power over 1 of the pins of a DIN jack if a 5 wire DIN cable is used as a MIDI cable and the receiver doesn´t like to see that eventually.
I myself, I power my EES M3 Velocity Transformer from Yamaha KX76 by using a short 5-wire DIN cable.
Any logical chip (CMOS) inside the controller might crap out,- who knows ?

If I look at the frontpanel LEDs of my Sycologic MIDI matrix switchers in the racks and at the frontpanel LEDs of my to computers connected MIDI interfaces, I see MIDI clocks and Active Sensing at the inputs all over the place not causing any issues like stuck notes or such.
I never filter out any MIDI data as a general rule, only on demand and for specific tracks in a DAW ...
Channel AT if I don´t need it, MIDI Prg.-Changes, SysEx and Active Sensing for the VSTi tracks ...

Bud

send only the mididata to a destination that is for this destination_
split wherever its possible_
specially keep the clock clean from other signals_
--
in case of the stsxk the midi is only triggering some host interaction;
if there are probl. with them check the host;
--
good vibes