MIDI CC input chokes and fails if data is sent too fast via USB [UNABLE TO REPRO]

I’ve been playing around with a midi solution to @ScottBrio’s request to be a able to zero all the track levels and I think I’ve found a bug.

If too many MIDI messages are sent at once to the S2400 via USB, it seems to break the ability to receive midi messages.

Not sure if this will work universally but to reproduce on my machine:

  1. Connect the s2400 to a computer via USB
  2. Open this html file in any webMIDI compatible browser e.g. Microsoft Edge or Google Chrome
  3. Click the Zero All Faders button.
  4. The S2400 will not respond to midi in (restart to fix).

Hopefully the file makes sense. It is sending NRPN messages to zero the track level on each track. I did a bit of playing around and the s2400 seems to handle 3 or 4 NRPN messages before it fails.

I worked around the issue by adding a 20ms delay between each 9 byte NRPN message. With the delay everything seems to work fine so my guess is that the s2400 is overwhelmed when MIDI messages come in too fast.

On line 25 of the html file, changing the variable choke_s2400 to false to adds the 20ms delays.

EDIT - change the variable to false to add the delay.

1 Like

Sorry for the slow response on our end. I tried your steps to reproduce, but was unable to get the MIDI to lock up. It all worked perfectly.

(Had to set Control Channel USB B / MIDI Ch 16, and make sure CC In was enabled for USB B)