How can software read the live state of a Digitakt II (telemetry)?
Fields we decoded (offsets in the decoded 111,616-byte buffer)
- 88,760 u16 big-endian: master length (1 = INF).
- 88,762 u16: change length in steps.
- 88,764 u8: master scale index (0=2×, 1=3/2×, 2=1×, 3=3/4×, 4=1/2×, 5=1/4×, 6=1/8×; order inferred from data and menu order).
- 88,765: scale mode (1 = per track).
- 89,096–89,111: kit name, 16 ASCII bytes.
- 89,116 + 2·(t−1): track level of track t (1–16), one byte, followed by 0.
A tempo-related u16 sits at 88,758; its scaling is unverified, so we do not publish a formula.
Clock and timing (measured)
- 24 ppqn MIDI clock; at 140 BPM one tick is about 17.9 ms.
- Every 0x58 reply (127,577 bytes, 2,660 USB packets) blocked clock on the same endpoint for 125–161 ms: 14 of 14 gaps over 50 ms contained exactly one such burst.
- Fix in software: fewer readbacks (we measured about 0.9 readbacks per second before trimming) and shared, hash-checked snapshots between readers. Never synthesise missing ticks.
- Audio attack of track 1 relative to the preceding received clock tick: median 6.95 ms (MAD 2.45 ms, 461 onsets).
What is not readable
Song row lengths were not in the working buffer or in project settings, and the device sends no Program Change on pattern change. We learn row lengths from the timing of fresh readbacks instead.
The device can return an OLED framebuffer screenshot over USB (30–70 ms per shot in our tests), see reading the OLED.
FAQ
Why does my Digitakt II MIDI clock stutter when I request dumps?
Large SysEx replies share the USB endpoint and stalled clock for 125–161 ms in our measurements.
Where is the track level in the Digitakt II kit?
At decoded offset 89,116 + 2·(track−1) of the working pattern+kit buffer (observed).
Observed on / Status: Observed on Digitakt II OS 1.16/1.17, October 2026, macOS host, USB. Offsets are from our own decoding; mark anything you build on them as unverified.
Deutsch
Den Live-Zustand liefert die Working-Pattern+Kit-Abfrage (0x68 → 0x58). Darin stehen Master-Länge, Change-Länge, Skalierung, Kitname und die 16 Spurpegel. Jede Abfrage blockiert die Clock auf demselben USB-Endpunkt für 125–161 ms, also sparsam lesen.
Related
- What does a Digitakt II SysEx message look like?
- How do you feed Digitakt II Overbridge multichannel audio into an AI listener?
- How can a vision model read a hardware sampler's OLED screen?