digi-roll dump diffing lab

← device console
Help us understand your box’s patterns One experiment at a time. No coding.
Every request here only reads your box. Snapshots and experiments are saved on your computer. Make the requested edits yourself in a scratch project.
Customize or share a checklist

    Stuck, or want the longer version? Read the walkthrough · Open a mapping issue
    → make ONE edit on the box →
    New box capture target ·
    No experiments saved. Send your captures — you can stop after one experiment.
    1. This collects your saved snapshots and notes into one file.
    2. Open mapping issue in your browser.
    3. Drag the ZIP from Downloads into the issue’s text box. Wait for the upload to finish, then post the issue or comment.

    Downloading does not send us the file. No need to unzip it or paste its contents. Email replies do not attach the files. Download before closing or reloading this tab.

    Own a box digi-roll can't read yet — Digitone, Digitakt (gen-1), Analog Rytm, Analog Four MkII? You can help map it, and nothing here ever writes to a box: this page only sends read-only requests. Connect → Probe dump protocol → post the report to the thread. If the probe finds a family byte, go further: Capture baseline, change exactly one thing on the box (add one trig, turn one knob one click), Capture + diff, write what you changed in the note, then Export pair and attach the file. Each pair teaches us one byte-level fact about your box.
    Connect a box, capture a baseline, poke exactly one thing, capture again. Each diffed byte is annotated with the struct region it lives in — unknown regions are the interesting ones.
    Lab notebook