Way to prevent BCF2000 to use running status?

By Nil, 18 October, 2025
Forums

Hello,

I am trying to use a BCF2000 to control a pedal (Two Notes Opus) that does not seem to support running status.

The issue typically occurs when associating a CC number to one of the faders and moving it. From my understanding the BCF2000 sends something with a running status, like:

Statusbyte CCnumber value1 CCnumber value2 CCnumber value3...

But for some reason the pedal understands the first CC change, but then mistakes the Values for CC numbers.

Is there a way to setup the BCF2000 to always send messages with a status byte? I was thinking maybe using BC manager with custom outputs? I'd love for it to have a global setting like the FCB1010 to deactivate it, but have not found anything like that.

Thank you in advance for your answers. Absolutely thrilled about all the work done by Mark van den Berg already, currently reading all the documentations but far from having a deep grasp on it.

Mark van den Berg

1 month 2 weeks ago

As far as I know, the BCF2000 doesn't have a Running Status switch.

Sending status bytes explicitly using "custom output" messages is an interesting idea.
However, my guess is that the BCF applies its Running Status logic to the final output buffer (where both "standard" and "custom" output bytes end up); so then your idea won't work: the BCF will apply Running Status logic to any output. But it's definitely worth a try.

But a variation of your idea should definitely work: you could make the BCF clear or change its Running Status after every CC message.
Note that any custom output occurs after the standard output. So you could try sending your regular CC message as standard output, and simply appending something that clears or changes the running status.
A book I have about MIDI says that Running Status should(!) be cleared by any Exclusive or Common status byte (i.e. F0-F7), but not by any Real-time status byte (F8-FF). So perhaps the best choice, requiring only the status byte itself, is F6 (Tune Request); all the other status bytes in the F0-F7 range seem less suitable for various reasons (e.g. requiring additional data bytes).

Hope this helps,
   Mark.

Thank you so much  for your answer and these suggestions Mark! I haven't tried any of these yet (but I will report if I do), at the moment the problem has been bypassed by using the BCF2000 in usb and going to the guilty pedal through a little MIDI router (H4MIDI WC, really sweet little swiss knife).