I have posted the first public version of the Vult Free modules here: Release First public release · vult-dsp/vult-metamodule-plugins · GitHub
I have been delayed with this release for a long time due to irrelevant issues.
This release contains some (not all) of the Vult Free modules available in VCV Rack. Please give them a try and let me know if everything works fine for you.
Oh - it’s already here!
This is such great news - let’s get testing people!
Great!
Really good news. Thanks so much!
I’ll give them a try asap.
What a great surprise! Excited to test these.
I tested an older beta on the first MM firmware. And as result immediately bought a Vult Freak from Leo. They are that good.
Who says porting to MM cannibalises your audience? 
sounding really great thus far ty for these! so many good filters in there…
@vult Thank you so much for taking the time to port your plug-ins over to meta!
At first I thought you wouldn’t do it because the metamodule could be seen as a competitor to your modules but I’m really glad that you thought otherwise. 
I really believe open platforms like vcv and meta, or maybe other digital module formats that don’t exist yet, will be the future of electronic music production and also live music performances will benefit massively from this development. My 2026 modular setup wouldn’t be possible without the metamodule in my rack. Nothing in that size would be able to keep up with what a metamodule can do.
I am 100% sure that in a near future I will add another Metamodule to my rack as it can easily replace two synth voices in my rack. Developers who are joining this trend early on will benefit in the long run massively as customers like me, producers and mixing engineers remember who is doing quality shit! 
I really respect your contribution to the scene over all the years. Your filters were in many of my productions as Dysfaction so yeah I’m excited to see your awesome modules join the meta platform 
Some questions:
Will there be premium versions of your modules and if so how will they differ from the stock ones? Same as in VCV? I think I bought all of your plugins 
oh and how will be the cpu damage for your modules?
Are you coming to the 10th anniversary of superbooth?
cheers
Jan
If it took me this long to port them, it was because of things out of my control. Dan from 4ms was very kind to let me have a MetaModule very early when it was released.
I think that the MetaModule is just a different experience from the modules I sell. If someone needs, for example, a filter like Freak or some modulation like Caudal, the most immediate interface are my hardware modules.
As I mentioned, I did not port them all. Some of them are more challenging to port for different reasons. For example, the CPU consumption, the custom controls, etc. I would have to modify the code and create alternative versions, which run more efficiently on the ARM microcontroller.
Regarding the other paid modules, I need to evaluate as well which ones are easy to port. It’s matter of allocating time to do it.
I ran them all through the CPU tests, and they all passed with very low CPU usage numbers (most were 5-15%).
They look good too!
@vult These modules sound great on the MetaModule, just like they do in VCV Rack.
One very small nitpick: The outputs on Lateralus are listed in a weird order, which makes it a bit awkward to find the one you’re looking for. It would make more sense to list them in numerical order, the way they are on the panel.
Unfortunately the order of the jacks has to match the order they are internally coded in the VCV Module enums, so for existing modules there’s no way (yet) to change that without breaking existing VCV Rack patches. That is, if the enum was re-ordered then opening VCV Rack patches created with an earlier version prior to the re-ordering would make the jacks silently be patched wrong
It could be that the order is defined by how the outputs are declared in the code.
the initial version of Lateralus did not have all the outputs. The 6 dB and 12 dB were later additions. I cannot change them in the code, otherwise the VCV patches would break. I would need some way of changing the order without affecting the numbering.
Oh huh. Would it be possible to add a separate enum in an #ifdef METAMODULE block?
Then the patch in VCV wouldn’t match the patch on MM. So if you made a patch with the 12dB Out jack (out jack ID 0) patched to a mixer in VCV then a different jack would be patched to the MM when you opened it there.
The jack ordering can only be set once, before a module is officially released. Once it’s out there, you really shouldn’t change it. This also goes for params.
I think we could support arbitrary ordering of elements on the MM with a small yml or json file in the mmplugin. It could even be part of the plugin-mm.json (OutJackOrder: [2, 0, 4, 1]). But… that’s OT…
All seems to be working ok - and great to have Basal and Bleak working on V2, such great sounding oscillators.
