[Iced-Cream]

Scene Mutes 0.1.0-experimental for Analog Rytm MKII (OS 1.74)

MrScruff's rytm-mods 0018-scene-mutes, from rytm-mods-src (cd4ded4), with his code unchanged and its addresses moved from OS 1.73 to 1.74. In scene edit, FUNC + T1..T13 builds the edited scene's mute mask (T13 is FX), and the trig keys show it while FUNC is held. Engaging a marked scene sets the mutes; an unmarked scene, or none, puts back the mutes from before. <CLEAR> and <CLEAR ALL> also drop the masks. Category system, core-ar2 0.7, no dependency on another module, 6 sites, 1002 bytes of .run and 6 of .bss.

What this adds: sdk/analog-rytm-mkii/modules/scene-mutes/ (source, build.json, manifest, README, TESTING, licence, thumbnail), release notes, author-hardware evidence, a rytm-emu capture with its media/capture.json, the source-only package sdk/imports/packages/scene-mutes/scene-mutes-0.1.0-experimental-os1.74.elemod, its records sdk/imports/scene-mutes-2026-11-08.json and sdk/imports/elekloader-scene-mutes-2026-11-08.json, the vendored catalogue copy and a verification record.

Sites: SceneEditView's key and LED vtable slots (ptr), its two clear actions (bytes with a reloc, so no stock opcode is kept), and jmp detours at the entries of the scene-engage and track-mute routines. None is a core, base or other module's site.

Storage: the masks live in the current kit's record in the stored project (+0x832..+0x841, +0x902..+0x90c), bytes stock leaves alone. core-ar2's kit storage uses +0x816..+0x822 of the same record, so they don't overlap, and the module declares no core storage.

How it was checked:

• m68k-linux-gnu-as assembles the source; scripts/build-elemod-packages.mjs + package-elemod-recipe.mjs build the package (the same toolchain reproduces env-reset-amp's committed package byte for byte with --check).
• Against the stock 1.73 and 1.74 files: rytm2_mods' tools/port_os.py Mapper moves all 19 addresses the module names to the ones it uses, and all six site guards match 1.74.
• rytm-emu on OS 1.74, build SM01 (the Modwerk base for core-ar2 0.7 + this module), against the base alone: FUNC + T1, T2 in scene edit lights T1 and T2; engaging scene 1 mutes BD and SD (track_mute_set called from module code), disengaging unmutes them; the base alone does none of it; no faults. Emulator only.
• npm run module:doctor -- scene-mutes: all green. npm run pr:ready: Ready. The package is vendored with npm run elekloader:update -- --overlay sdk/imports/elekloader-scene-mutes-2026-11-08.json; record in docs/verification/2026-11-08-rytm-scene-mutes-library.md.

Hardware (T210, 2026-11-08, OS 1.74, build SMH1 = base for core-ar2 0.7 + analoghealth 1.3 harness + this module): with scene 1 engaged BD and SD went silent while RS and CH played; a hand mute of CH while engaged stayed after disengaging, when BD and SD came back; the mask and the hand mute survived a power cycle; <CLEAR> dropped the mask. CPU 74 to 82 %, heap flat. Not tested on a unit: <CLEAR ALL>, scene engage by CC 92, NRPN or Overbridge, kit changes. The author listened to the takes; evidence tier author-hardware (evidence/hardware-testing.json).

What the guides lacked: nothing.

• Source and media are original or properly licensed; MrScruff credited, full GPL-2.0-only text kept. No firmware, extracted code or tables.
• TESTING.md lists what was not tested.
• Screenshots are real captures (rytm-emu, labelled as emulator).