Replies: 1 comment 2 replies
-
|
we can add midi write_flush() similar to cdc. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When a midi device is mounted (
tud_midi_mounted() == true) but the events are not consumed by the host (noaseqdump -p 20:0or equivalent running), it looks like midi events sent withtud_midi_packet_writeaccumulates in a buffer.When the host finally starts to consume event, all the notes are received at the same time which can be an issue for a instrument.
What is the standard way to deal with that?
Is there a way to detect that the host is not consuming events earlier than observing the buffer is full with
tud_midi_packet_writereturn value?Is there a way to clear the buffer when it is clogged for a while?
Beta Was this translation helpful? Give feedback.
All reactions