v0.7.3 — A key you press must never be ignored in silence

A key you press must never be ignored in silence

Declare a keyboard whose range isn't the one the size chip assumed, and Keys looked broken.

Every key still sounded — the engine routes on the raw incoming note and never consulted your
declared range — but the drawn keyboard has no element for a key outside it. So nothing lit up, the
roll had no column, and from the other side of the screen that reads as "my keyboard stopped
working".

Now a note outside the declared range says so, once, and says what to do:

C1 is outside the 61 keys you told Keys you have, so it sounds but does not light up.
Sound → Your keyboard → "Press my keys instead" sets it from your actual keyboard.

"61 keys" is not one range. Plenty of controllers sit somewhere other than C2–C7, and many have
their own octave buttons that move where they start — so the size chips are a shortcut, not a fact
about your hardware. Press my keys instead reads what your keyboard actually sends, and it's the
only answer that can't be wrong.

The notice stays quiet while Detect is armed, because there, pressing a key outside the current
range is exactly what you were just asked to do.

If your keys have stopped lighting up right now

You don't need this update to fix it. In Keys: Sound → Your keyboard → Press my keys instead,
then press your lowest and highest key. Or pick 88 keys to put it back how it was. Your playing
was never lost — it was sounding the whole time.

---

947 assertions across the thirteen checks that need nothing plugged in.

SHA-256 bb23d94b89e971d73148ce784083f679a2c625b5b0755b6f817343873e4bc58a