Skip to content

midiEngine hears every MIDI input on a computer, and both players answer keys sooner there - #28

Merged
bdbarnett merged 2 commits into
mainfrom
desktop-midi-latency
Nov 3, 2026
Merged

bdbarnett merged 2 commits into
mainfrom
desktop-midi-latency

Conversation

@bdbarnett

Copy link
Copy Markdown
Contributor

midiEngine opened a computer's first input only, which is as likely a software synth's as a keyboard's, and on a MicroPython build carrying usb.core it took the board's USB host path and opened none. It now reads them all, as Synth Station does. Both apps ask a computer's audio output for its low-latency profile; a board's output doesn't change.

…wer keys sooner there

midiEngine opened a computer's first input, which is as likely a software
synth's as a keyboard's, and on a MicroPython build carrying usb.core it took
the board's USB host path and opened none. It now reads them all, as Synth
Station does. Both apps ask a computer's audio output for its low-latency
profile, since the default buffers for playback.
Removing umidiparser's decorators read the source a line at a time, which
MicroPython does a byte per system call: 15 s over a network drive.
@bdbarnett
bdbarnett merged commit 72c33f5 into main Nov 3, 2026
5 checks passed
@bdbarnett
bdbarnett deleted the desktop-midi-latency branch November 3, 2026 05:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant