I got the wi-fi extender for the MM and now it’s super enjoyable to edit a patch in VCV while testing with the hardware, really streamlined the process.
However there doesn’t seem to be a way to edit the scaling of MIDI mapping in VCV. So I have to edit these on the MM itself after I transferred the patch, but that means I can’t really go back and forth between VCV and the hardware as every time I transfer a patch the mappings are off (and I use a lot of them)
AFAIK this currently is a limitation of the VCV Midi Map module. Would it be possible to handle MIDI mapping in the VCV MetaModule Hub instead? Or any ideas for a workaround?
1 Like
I would also love this.
Actually I think it is really essential in order to work on more complex patches that incorporate lots of MIDI mappings.
My current workaround is to dial in the ranges on my midi controller (I’m using a Neuzeit Drop).
But that won’t work for MIDI controllers with fixed ranges.
Suggested solution:
My suggested integration would be to have a VCV Rack expander module that is just dedicated for MIDI mapping (instead of trying to cramp it into the main VCV Rack MetaModule).
The expander would look similar as the main MetaModule but instead of having the knobs and the in/out jacks you would have 8 pages of 16 CCs each (resulting into 128 CCs).
Mapping workflow: Similar to mapping of Knob Sets you just press one of the CCs and then press on the knob/button/etc. which you want to map.
Adjusting ranges: Also similar to Knob Set mapping, you could then right click that CC and change the range.
Changing MIDI Channel: To avoid getting conflicting MIDI mappings it would be necessary to be able to define a specific MIDI channel for the expander module.
Bonus: Being able to map multiple dials to one CC (just like you can map multiple different dials to one MM knob with different ranges)
This would also (kind of) solve the issue mentioned here
I think this would be a great addition to the MM!
Cheers
Jan
1 Like