MIDI in missing note off events [Solved]

I am in contact with Jakob (see https://github.com/moddevices/mod-ttymidi/issues/6). Ok, I have to check at my side and had no time the last weeks. But I hope I can try to help fixing when I have my MIDIboy.

Regards, Holger

1 Like

Hi @ll,

FalxTX has fixed mod-ttymidi. I have just tested on Aruk and it works for my setup. Perhaps someone can also test (HEAD on branch master) and than we can use the up-to-date version from github?

Regards, Holger


Would this be the USB MIDI port not always handling Notes Off events…? Cos I’ve seen that effect. 5 pin MIDI works ok for me…

If so I’ll give it a look. I have an effect on the Behringer Motor 61 where USB notes off don’t always make it throu but 5 pin DIN connector MIDI works ok . . .

No this is just the DIN Midi stuff not enjoying running status the usb issue was to do with limiting the rpi to running in usb1.1 mode.

aaah yes! I remember now…

Strolls of to confirm a negative . . . .

Works like a champ! Obligatory sound clip using DIN midi from the MK 449C in post 1.


and I think the USB Midi issues I’ve been twittering about are solved. . :slight_smile:

If you get stuck notes in USB MIDI devices, Turn on the Limit USB speed to 12Mb/s


OK! Nice to see solved this old issue. I’ve restored the recipe to use the last version and updated the issue in github:

The next night build should include the latest version … :wink:

Thanks Holger!


BUT. I see a flashing blue M all the time now, although the Midi Log is not showing anything in MIDI IN.
Does anyone has the same behaviour?

Have you updated today? Try updating again, specially the webconf. You should see system messages in the MIDI log …

yes. Maybe I didn’t explain my issue properly. I connect a keyboard via tty and don’t generate any events. And nevertheless the M is flashing. I don’t expect anything in the log but no flashing M.

OK! I understand the issue …
Yesterday i committed a change that modifies the behaviour of Zynthian MIDI router, allowing that MIDI System Messages (0xF?) reach the UI. Also, i modified the webconf’s MIDI logger for displaying these messages that didn’t show before. So, the logic explanation should be that some of your MIDI devices are generating MIDI clock or other MIDI System Messages …


I wonder if it’s to do with the fact mod-ttymidi now does running status. Is it reacting to things like Active Sensing do you think?

Yes, now active sense is forwarded to UI too. Perhaps it’s better to block it … what do you think?

Or should we show it in the logs first, so that I can report, what it is?

1 Like

ACTIVE_SENSE messages should be shown in MIDI log already …
The only System messages that are currently blocked are SysEX (0xF0).

BTW, where are you sniffing the MIDI stream?

I selected Midi IN