You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
midir receives the events that were sent before listening started (in a burst)
midir does not receive any new events
In practice, this means, whenever the reception of events fails I have to:
Stop my midir application
Physically disconnect the MIDI device
Physically reconnect the MIDI device
Restart my midir application
It haven't checked whether physically disconnecting/reconnecting can be achieved in software but in any case this problem, unfortunately, is very annoying and poses a problem for real-world user applications.
The text was updated successfully, but these errors were encountered:
I guess you're using the (default) ALSA backend? It would be interesting to know if this behavior is the same when you use ALSA (also alsa-rs) directly, because I can't think of anything we do in midir that would provoke this behavior. And I don't think that any other backends behave that way.
I can see the events when I use aseqdump on the device (a MIDI pedal) but when I use midir I see the events issued just before my programme ran, and then it hangs.
If I run aseqdump at the same time as my programme, my programme never gets anything.
Reproduction on Linux:
midir
starts listeningResult:
midir
receives the events that were sent before listening started (in a burst)midir
does not receive any new eventsIn practice, this means, whenever the reception of events fails I have to:
midir
applicationmidir
applicationIt haven't checked whether physically disconnecting/reconnecting can be achieved in software but in any case this problem, unfortunately, is very annoying and poses a problem for real-world user applications.
The text was updated successfully, but these errors were encountered: