The Button Expander in VCV and on MetaModule: different behavior! The Expander button behaves as expected in VCV: for example, when used for the toggle buttons on all Mutable Instruments clones. There, three or more switching states are often cycled through in series, using just a single pushbutton for each. What works exactly as expected in VCV—by switching through any number of states for the buttons on the module—no longer works in the MetaModule! In that case, a Button Expander button can only pass on two fixed states! 0/100%, or possibly “one after the other” via the “toggle” option, but nothing more! Is there a firmware fix for this? As a workaround, I had to use the sliders again, and the Button Expander is still useless for me.
Why hasn’t anyone noticed and pointed this out yet?
The cycling through states in the Mutable Instrument clones is due to the difference between those modules in the Metamodule vs. in VCV. The MM version uses flip switches, and the VCV version uses momentary buttons.
I’m working on a feature that lets the button expander cycle through values. It’s not as straight-forward as the toggle feature, but it should work.
Great news! I would love to use the buttons expander to cycle through parameters on ports that use switches! Thank you so much for adding this function!
If you feel like previewing the feature, try this out:
The new mapping type is called “Step” (vs. “Normal” or “Toggle”). If you map a button to a switch that has 3 or more distinct positions, then it should automatically enable Step mode for that mapping. You can edit it on the same Knob Map page as before.
It really does work now, as expected, with the Mutable Instruments “Rings” (VCV: Resonator). Thank you very much for this update!
I changed the mapping here directly on the MetaModule to “steps.” Will this setting also be available in VCV in the future?
Great!
Yes the next VCV 4ms plugin release has an option in the context menu to select Step, Toggle, or Normal mode.