01 / Connection
Connect Web MIDI
Use current Chrome, Edge or Opera over HTTPS. Close Novation Components and other MIDI software first.
02 / Diagnostic monitor
What is the Tracks sending?
| Time | Dir | Channel / type | Message | Bytes |
|---|---|---|---|---|
| Connect an input, then play or sequence the Tracks. | ||||
03 / Bootloader only
Validate and install firmware
First-hardware-test alpha. A failed update may require official recovery. Use a direct USB
cable and stable power. Never disconnect or close this page during transfer.
Build 4694 — latest
v0.6.0 alpha · real DX7 (matches Dexed's engine) loading plain .syx files from DX7/ on the card, up to 256 voices · custom reverb, tape delay, lo-fi and chorus (FX view pad 32) · Performance page (second Mixer press) · strum and Degree pads · pattern repeats ×1–8 · Groove · XT queued switching, chains and Scenes. Emulator-tested only. Flash diag 4695 instead if you're doing the DSP load readings. sha256 ae5ac779…17c5fa69
Build 4548 — last good, re-flash to play
v0.2.20 · pure XT8 (generator/patterns/chord/arp), no DSP. Stable daily driver; pack-switching fixed, project isolation on. sha256 33aad6e77662636910dc1a22e4640b07d62bf28dad34743d228b34ac33d5860b
Build 4660 — SysEx debug monitor
v0.3.13 (same as 4646) + a read-mostly debug monitor for hardware probes with
tooling/ctdebug.py on the laptop. Flash this first for the debugging session. sha256 8a94f392…a82067a9
Pad layouts and button gestures live on the cheat sheet; walkthroughs and recipes in the Generator guide.
The file will be decoded locally and its product, structure, padding and firmware CRC checked before the
install controls become available.
Enter the official bootloader
- Power the Tracks off.
- Hold Scales + Preset + Note while powering it on.
- Reconnect MIDI above and select both ports whose names contain Boot.
Waiting for a validated file and bootloader ports
0%
How this loader behaves
It mirrors Components’ Circuit Tracks transport: update-init and header are sent first, then one firmware block per bootloader request. It stops on timeout, disconnection, cancellation or CRC-error status, and reports success only after the bootloader returns its final viable-composition status.