I reached out Benjamin at Stoermelder about porting his plugins. He is a MM owner and seems to be interested. I am specifically interested in plugins like uMap for knob automation. Let him know what plugins you would like to see @ stoermelder@outlook.com. Also, if anyone can offer porting assistance, I am sure it would be appreciated.
This is a really old post from 9/24 on this subject but it doesn’t look like anyone responded: Stoermelder modules possible in MM?
Great Tony. I just emailed him. For me Umap, Remove Lite, Transit and 8face would be awesome. Thanks.
I thought some of his plugins relied on adjacency to operate and this functionality isn’t available at the moment with the 4MM.
Not sure about that…however, he could ports the ones that don’t require adjacency a la what they did with BogAudio.
I think the other thing that isn’t possible on the MM is for modules to communicate with each other (except through cables) — so things like 8FACE, TRANSIT, and uMAP wouldn’t be possible without a lot of API work from Dan.
would be really great to eventually have the functionality on mm that would allow umap, remove, and strip (as well as others people mentioned) to work! those are super powerful
Yeah, here’s the comment I was thinking of, from Dan on ModWiggler:
Modules aren’t allowed to control each other’s knobs or “talk” to each other except through patch cables, so a lot of the steormelder modules wouldn’t work. But some of them would be great, like 4ROUNDS, for instance.
https://www.modwiggler.com/forum/viewtopic.php?t=277469&start=300
Agree this kind of functionality would be cool.
1 Like
It would be great if that kind of functionality could be added!
Hello everyone, I haven’t worked on my VCV Rack modules for quite some time, but I managed to convert a small selection and make them work on the MetaModule.
You can grab a preview build here:
Release Nightly-MetaModule · stoermelder/vcvrack-packone
Any feedback is much appreciated!
But: some of you might be waiting for my most known modules, these are not included. I’m not sure about them. Let’s see what happens 
8 Likes
Thanks for doing this! Looking forward to using them on the MetaModule.
1 Like
Magnificent, love your work, thank you.
1 Like
Excellent. Any chance you could list the plugins that you’ve included in the beta release pack - the github site doesn’t provide any clarity.
1 Like
I’ve updated the GitHub release with the modules currently included.
3 Likes
That is awesome. Thanks, Ben!
1 Like
Great! I’m happy to include these on our plugins page and module finder whenever you feel they’re ready for testing
1 Like
so awesome to see stoermelder modules ported to MM! thanks a lot!
1 Like
The challange with most of my modules is, that they use parameter-mapping, which is not available on the MetaModule right now (firmware 2.0.2). But the issue lies deeper and is caused by VCV Rack itself:
VCV Rack does have an incomplete interface for handling parameter mappings: They are like an “one way street”, meaning a module can apply new mappings on any module in the patch, but VCV Rack can’t query a module about its mappings or trace back which module holds a mapping for a specific parameter. Only the module whichs holds the parameter mapping knows about it (this is why it works for the virtual MetaModule module and transfering knob mappings to the physical module).
This is also the cause, why importing selections (vcvs-files) forget any parameter mappings. In my modules I implemented several workarounds, like parsing the json-preset for known modules (MIDI-MAP for example), but to be honest it is quite a mess. Even if MetaModule would support parameter mappings which would enable modules like my CV-MAP, TRANSIT or ReMOVE, it would not be obvious for the virtual MetaModule how to transfer any parameters mappings over to the hardware.
I requested this feature (extending the interface for parameter mappings) a few times from the VCV Rack team, but I don’t know if anything ever will be implemented. Maybe for Rack v3.
2 Likes