[draadpiraat]

Crossfader 0.1.0-experimental (Digitakt I, OS 1.54)

The crossfader half of Loop & Fade (#1408), split out as its own scenes module at the owner's request. Chosen together with Live Looper (#1408) it gives the same instrument.

• Every audio track and both inputs (IN L, IN R) go in group A, group B or neither on SETTINGS > CROSSFADER. One fader fades between the groups with an equal-power curve; the delay and reverb sends follow it.
• The fader is LEVEL on the Internal Mixer, LEVEL on the pages of FADER ON tracks, or a CC on FX CONTROL CH. FUNC + LEVEL jumps to the middle; pushing LEVEL does nothing on those pages, so a fade never opens the sound browser.
• Settings are saved for the whole unit on the +Drive (/cfw/xfade.a, .b).
• Conflicts: none. It shares no bytes with RAM Machines, the Live Looper or any other Digitakt module.
• Claims: settings:CROSSFADER, LEVEL and LEVEL push on the Internal Mixer and FADER ON tracks, the fader CC on FX CONTROL CH, drive:/cfw/xfade.a, drive:/cfw/xfade.b.

Tests

• Emulator (digiemu c1b5735, CF01, the module alone): the CROSSFADER page, groups, FADER ON, the fader on the Internal Mixer and a FADER ON track, four screenshots. Load +0.5 to +0.7 points of an audio block (modelled). Shared RAM 4,844 bytes.
• Hardware: the combined LF03 build passed every crossfader check on draadpiraat's Digitakt I (2026-11-10, two hours or more). CF01, this exact build alone, then checked out on the same unit (2026-11-12): recorded in evidence/hardware-testing.json, tier author-hardware. Noticed for the next version, not in this one: the fader starts at A after power-on, an optional middle snap was asked for, and the box's position line is a pixel off centre (all in the README's limitations).

What the guides lacked or got wrong

Guides: nothing.

Checklist

• Changing a module someone else wrote: not applicable, this is draadpiraat's own code.
• I read the guide for its category in docs/module-guides/ (scenes.md), and TESTING.md lists what I did not test.
• Source and media are mine, with the full licence text. Nothing comes from Elektron firmware.
• Screenshots are real captures of the current module UI (digiemu, CF01). Emulator results are labelled as such.
• Automatically merge and publish my module update after checks pass.
• I verified the source, licences, UI and qualification reports, including instance isolation and Part/project/reboot persistence where applicable; no required acceptance check is failed or untested.

Validation commands and results

• npm run module:doctor -- crossfader: green apart from the board claim and the catalogue pin (added once this PR is open).

Related to #1408

🤖 Generated with Claude Code

https://claude.ai/code/session_01DjGstighoF133yaiHa5t9d