Repository navigation
tabby-v04.12
The scene chain: each scene's length and what follows it, set on the SCENES page, with a hold. Reinstall to get it (Full backup first; storage does not move).
Classic Tabby tabby-v04.12: the scene chain
- Firmware package build ID:
568ffa35e8faa236(first 16 hex digits). App image 480420 bytes (measured), margin 39037 bytes
below the 519457-byte limit (docs/FLASH-BUDGET.md 35). From tabby-v04.11.2 (5132d1244cb66781): +1184 bytes. - Installing over tabby-v04.2 to tabby-v04.11.2 keeps storage as it is. Take a Full backup first anyway.
- Going back to older firmware: songs saved on tabby-v04.10 or later cannot be read by older firmware. Go back to
an older build only with a Full backup made before tabby-v04.10: install the older build, then restore that backup.
What is new
- The scene chain on the SCENES page. The scenes of a song play in order. For the scene that plays:
- K1: how many times it plays before the next one (1 to 64). The LEN line shows the scene's length in master cycles.
- K2: THEN NEXT (the following scene comes by itself) or THEN STAY (it repeats until you recall another).
- K3: CHAIN HELD keeps the scene that plays whatever its settings say; CHAIN RUNS lets the song go on.
- A pad always wins: the song jumps to that scene and goes on from there.
- Start anywhere. A scene pad pressed while the song is stopped reserves that scene; PLAY starts there (as on the
MC-707). The pad again takes it back. - The settings are part of the song and are saved with it.
Validation on the device (2026-11-16, unattended)
Full backup first, one install attempt: "Firmware ready." after 9.4 s. Scene chain 13 of 13 (the song starts at the
reserved scene, a scene lasts its new length, the next follows, the hold, a pad jump, the save). Clip chains 11 of 11,
CLIP SETTING 21 of 21, recording 25 of 25, STEP page 18 of 18, CLIPS page 40 of 40 twice. 960 notes on one line: 1.86 to
1.90 ms band on DIN and 1.83 to 1.93 ms on USB in three runs. Backup and verify after: PASS.
The timing runs of this evening that showed 2.0 to 3.8 ms were this computer's clock, not the device: the time service
steers the clock the MIDI input is stamped with (between +4 and -25 ppm while it was watched). Measured against the
computer's unsteered clock the device's rate is the same in every run (0.999580 of nominal).