faderpunk-tools
Two personal companion apps for Faderpunk: a preset bank that recalls whole layouts, and a debug scope for punkapp developers. Both run in the browser and talk to the device over Web MIDI — nothing to install. Chromium with SysEx permission required; close other tabs that hold the device ports.
- Presetpunk Preset bank — a layout layer on top of on-device scenes
- Scopepunk Debug scope for punkapp devs — per-app MIDI traces, profiles, monitor
Presetpunk — a layout bank on top of your scenes
Scenes give you instant recall inside a layout. Presetpunk adds the layer above: the layouts themselves.
A browser editor that keeps whole Faderpunk layouts as named presets and pushes any one of them to the device over SysEx. It picks up where the module’s scenes leave off: scenes for everything within your current setup, presets for moving between setups.
That extra layer is the point. A preset carries the full slot assignment, every app’s parameters and the global config, so recalling one can hand you a different instrument — and once it’s loaded, the device’s own scenes take over from there as usual. Build the bank, reorder it, keep it in the browser, take it to the next session.
The device stays the source of truth: Pull from Punk captures whatever you just patched, and pushing back works whole-preset, per-slot, or live while the patch runs. Instruments and a MIDI CC catalog keep a preset readable months later, and the printable cheatsheet gives you a fader-by-fader reference to keep next to you at a live gig. English, German, French.
Scopepunk — a debug scope for punkapp developers
A developer tool: visually verify what a Faderpunk app actually emits, instead of guessing from a patch cable.
A debug scope for punkapp and firmware development, not a performance tool. It shows what your code is actually sending — per app, live.
Developing on hardware is otherwise blind: change a curve, flash, then guess from an LED and a patched-in module. Scopepunk draws notes, CC, NRPN and clock as separate labelled traces per app, so a wrong channel, a stuck value or a drifting clock shows up in the first second.
Views follow the questions you have while debugging: All to spot the misbehaving app, Focus to iterate on one, Compare for phase and clock-division bugs. Averaged waveform profiles reveal a modulation’s real shape when single frames are too noisy, and an audible monitor puts CC streams through a wavetable when your ears are faster than your eyes. One caveat: USB MIDI carries no CV, so Scopepunk sees only what an app mirrors with MidiOut → USB — CV-only apps stay dark. Demo mode works without hardware.