Ralf Beck wrote:
Am 07.05.2014 22:41, schrieb Clemens Ladisch:
This is a bug in Bitwig.
I agree, but see above. I can't change Bitwig.
You can submit a bug report.
And changing this setting might introduce regressions in other programs that rely on the size of the raw MIDI data.
Being able to receive MIDI data with running status disabled is mandatory for a midi client. So any client relying on running status always on would be buggy.
As buggy as Bitwig?
If there is a conflict between two API behaviours, avoiding regressions wins. Bitwig has no excuse; it has been buggy from the beginning.
Would the patch be acceptable, if i make switching on/off of running status selectable by a module parameter with the current behaviour being the default?
A module parameter would be worse.
Regards, Clemens