Repository navigation
[synth] CHRD mode scene change of chord does not change #751
Description
Reported on Modwerk for synth by member_6ff0118f2416 · @timhastie
| Device | Octatrack MKII · OS 1.40C |
| Module version | 0.1.2-experimental |
| Firmware | Running a Modwerk build |
| Build fingerprint | Not recorded |
Configuration
mute-modes0.2.1-experimentalsynth0.1.2-experimentalpreviewvol0.1.2-experimentalsidechain-compressor0.1.2-experimental
Steps to reproduce
1.enable a chord to play, not highlighted but as default.
2. now set a scene change with a different chord.
Expected
goes through the list until it hits the right chord
Actual
i set a specific chord for a scene, but it only plays its default chord setting. Does not respect scene changes for this one setting. No trigger changes were made to CHRD
Everything the reporter submitted is in this issue. Comments and status changes here are sent to the reporter on Modwerk, and the reporter’s replies appear here.
Module maintainer actions
Reply here normally. Registered authors and verified current maintainers can manage reports with new comments; no fork or repository write access is needed:
/modwerk needs-info <question>/modwerk confirm <affected-version|unknown> <reproduction evidence>/modwerk close insufficient_information <explanation>/modwerk close configuration|duplicate|not_reproducible|withdrawn <explanation>/modwerk reopen <explanation>/modwerk resolve <published-version> verified-download
Keep a report open with needs-info while waiting for the reporter. Confirm only a reproduced bug; use unknown for a configuration report. Questions and suggestions can use /modwerk classify question|feature <explanation>. Advanced states: /modwerk investigate <explanation>, /modwerk awaiting-verification <explanation>, /modwerk unconfirm <explanation>.
Only the registered release author can use resolve, after verifying that exact published download fixes the report on their unit. Ordinary closures claim no new firmware fix.
A merged PR alone does not resolve a report. Author release steps.
Activity
timhastie commentedon Oct 24, 2026
Fixed in my standalone line (Octatrick 2.17/2.18, github.com/timhastie/octatrack-modules): CHRD and VOIC can be assigned to scenes and the crossfader morphs through every chord shape. The Modwerk module is still 0.1.2. I will submit the update when Modwerk confirms the new Octatrack base and how modules register with it.
repeat98 commentedon Oct 29, 2026
@timhastie the new base is live: beta base 9b7e0eb3 (#1017 on 28 Oct, then #1026 and #1030). FM Synth registers the same way as 0.1.2, with one
ot_machinesrow frommachine-ports.json. What's new are three opt-in flags on that row (flagsinmachine-ports.json;sdk/machines/octatrack/HOOKS.md,ot_machines; the SRC SETUP items indocs/module-guides/machines.md):SETUP_PAGE: the machine draws and edits its own SRC SETUP page over USB through astruct modwerk_machine_setup(itspageandknob). VECTOR 0.2.5 is the example.SETUP_ALL: encoder E (slot 10) on SRC SETUP edits the machine's own slot. Without it that encoder stays read-only.LIST: for a machine without a pool, a double tap on its track opens the machine list, as PICKUP's does.For the mute,
ev_trig_muted(index 35, #912) is unchanged. Over USB the double-tap list now scrolls and its cursor reaches every row; on card builds POLY8 0.3.2 does that.On versions: my #895 holds 0.1.3, so yours is 0.1.4 as you planned. @jankolkmeier's #884 also says 0.1.3 and makes LFOs and scenes reach the AMP envelope and VOIC/CHRD, which overlaps your CHRD/VOIC scene fix for this issue. Could you two agree which one carries it? My suggestion: 0.1.4 carries it, with Jan credited for what you take from #884, and #884 closes when your PR is up. Jan, is that OK with you?
jankolkmeier commentedon Oct 29, 2026