[Claptom-music]

MIDI controllers with snap mode need the Rytm's current parameter values to pick up after a kit or parameter change. MIDI Feedback adds per-project DIN feedback for seven parameters on each of the 12 drum tracks. It sends settled changes and refreshes targets in the background. The module consumes no incoming MIDI and defines no SysEx messages.

This is the first 0.1.0-experimental release for Analog Rytm MKII OS 1.74. The module source and original media are attributed to claptom-music and carry their declared licenses. The browser catalog pins the compiled module package to a source commit and SHA-256.

MF06 passed the exact-image emulator checks. On a physical Rytm MKII with a PC12 over two-way DIN, claptom-music reported smooth pickup, responsive pattern changes, kit reload, and restart persistence with both PC12 forwarding modes disabled. An earlier MF06 freeze remains unexplained. The pattern-paste emulator sequence also stalled on stock firmware, so it could not isolate that freeze.

The module occupies 3,557 bytes, excluding the core. Load results are observed emulator clocks, including preemption. Physical CPU cycles, masked-interrupt duration, and audio deadline margins remain unmeasured. Hardware and emulator results are separated in TESTING.md and evidence/mf06.json.

Guide feedback. Nothing to change in the module guides. The local Windows compatibility generator hit a path separator assumption, so the PR checks run in Ubuntu.

Validation. npm run pr:ready reported Ready on the submitted commit. The isolated toolchain builds matched and reproduced all 44 checked source-only exports after merging upstream main. The subsequent library fixture update leaves those build inputs unchanged.

[repeat98]

Hi, welcome to Modwerk, and thanks for MIDI Feedback! Snap pickup after a kit or pattern change is a real gap on the Rytm. It also hooks in just the way the base wants: core events and two GLOBAL rows, no stock sites, OFF by default, the switch in core storage. And thanks for keeping the hardware and emulator results apart.

Three things before the first release:

1. Merge main. Env Reset Amp, Ctrl All and Main RMS entered the library since you branched, so the module list in src/devices/library-parity.test.ts conflicts. Keep both sides with MIDI Feedback in its place, then run npm run pr:ready until it says Ready. More Rytm modules land today on the same line, so you may need one more merge just before it goes in.
2. The overlay record. In sdk/imports/elekloader-midi-feedback-2026-11-07.json, source.repo should be repeat98/modwerk, as for the other packages built in this repository. After the merge your commit is in this repository, and that's where elekloader:update looks for it.
3. The freeze. The unexplained MF06 freeze at a pattern change is the one thing I'd like to understand first, since a freeze in the middle of a set is the worst outcome. Has it happened again since a82ff483 (defer on inconsistent queue states)? If you can, please do a longer run on your unit: about 30 minutes of pattern and kit changes with feedback ON and the PC12 connected, plus a few minutes with nothing listening on DIN OUT. Put the result in TESTING.md, freeze or not. If it's still unexplained after that, keep the limitations line as it is.

Once that's in, I'll merge it with a merge commit, since the catalogue pins one of this branch's commits.

[repeat98]

Thanks for the long MF06 run. MIDI Feedback is merged and live: https://modwerk.app/analog-rytm-mkii/module/midi-feedback/

Two Rytm modules landed on the same module list today, so I merged main into your branch once more and kept both sides. If the freeze ever comes back, please open an issue with what was playing.