Skip to content

midiEngine: say on the status line when the sound can't start - #40

Merged
bdbarnett merged 1 commit into
mainfrom
midiengine-flash-fallback
Nov 7, 2026
Merged

bdbarnett merged 1 commit into
mainfrom
midiengine-flash-fallback

Conversation

@bdbarnett

Copy link
Copy Markdown
Contributor

A keyboard that is detected but silent looked like broken keys: the status line named the keyboard even when no SoundFont (or no sampler) had started, so there was nothing playing to hear. The status line now shows the reason until the sound runs, and the face already carries it.

Live keys never depended on a MIDI file; the port is read whether or not one is loaded. Checked on a GIGA R1 with a USB drive as /sd: 109 files list, GeneralUser GS opens, a file plays and the DAC pin swings with it (rms 2316 against 13 stopped), and a chord fed through the same path with no file playing moves it too (rms 1810). With audioeffects removed the status line and face both read the error. Not checked: keys played by hand on the Donner.

With no SoundFont, or a sampler that fails to open, a detected keyboard played nothing and the status line only named the keyboard, so it looked like a bug in the keys. The status line now shows the reason (and keeps showing it when a device appears) until the sound is running. Live keys were never gated on a MIDI file: the port is read whether or not a file is loaded. Checked on a GIGA: with audioeffects missing the status line and face both read the error; with it present, 109 files list from /sd/midi, GeneralUser GS opens and a chord from the keys, with no file playing, moves the DAC pin.
@bdbarnett
bdbarnett merged commit 4252861 into main Nov 7, 2026
6 checks passed
@bdbarnett
bdbarnett deleted the midiengine-flash-fallback branch November 7, 2026 11:53
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