I’ve just started to use the paramater rec function on the muse and I was wondering if anyone else was experiencing this.
If i para rec filter movement on timbre A, it also affects timber B. In this instance i have a bass sound on timbre A and lead on B. I only have timbre selected and I don’t have split or stacked selected. whats strange is it only seems to affect the other timbre when i change over to it and not during the initial parameter recording. Is there any way of doing his so the P record only affects the timbre i’ve selected?
Clear Param isn’t clearing the parameter i’ve recorded so I have to do a clear all which really is not ideal when you have a number of parameter lanes used. Is anyone else experiencing this?
Yeah I was demoing a unit and found this as well. Seems a bit of an oversight. Just like you can record Timbre A and B notes into the sequencer, the PARAM REC should record which Timbre’s parameter was recorded, not apply the modulation to whichever Timbre is active!
Forces you to choose between PARAM REC or Multi-timbrality.
I suppose a work around could be to mod map Macro or Mod wheel to a given param on one Timbre only, and then PARAM REC the controller?
That sounds like a per-timbre state bug rather than a recording mistake. I would first save a copy of the patch, then test with an otherwise identical A/B pair: record one short filter move on A, switch to B without touching the controls, and check whether the recorded lane is still present or only becomes audible when B is selected. For the clear issue, it may be worth noting whether Clear Param is clearing the lane, the recorded data, or just the current selection—those can behave differently in sequencer firmware. A short screen recording showing the selected timbre, lane, and the exact clear action would give Moog support something reproducible. The macro/mod-wheel workaround sounds sensible meanwhile, especially if it keeps the two timbres independent.