If there was something like this for the MM…
i too had requested this back in the day. it would indeed be awesome to be able to load puredata patches, or javascript on the mm!
And one of the reasons, why there is always a disting-nt right beside the MM.
The Disting NT is on my list to pick up and place next to my MetaModule. ![]()
I have both the MM and the Disting NT in my rig. There is a small bit of overlap in the capabilities of each, but for the most part they are very different and complement each other very well. I wonder how many folks have both?
The developer of the “NT Helper” app has recently shown an early version of a Disting NT emulator module for VCV. With that we might be only one step away from running an instance of the Disting NT inside the MM! I say that with my tongue planted firmly in my cheek as there would likely be issues of whether the MM would have sufficient processing power to run such a module.
Edited to add that the VCV module shown is intended by the creator as a development platform for his user created apps and it would not not likely be able to run the native Disting NT algorithms.
My wish is to have a dedicated monitor display (using that USB-C perhaps) + some functions so that in “extended mode”, we can view the modules nice and huge and use MM’s screen as a secondary screen for Knobsets, Scope work and such.
There is development on the Percussa SSP using MAX RNBO development platform for making MAX patches run as stand alone apps. Maybe a template can be made for the MM in a similar vein.
That would be fantastic.
Is there any plans of porting the Vcv Vst host plugin? In that way i guess it would be possible to run Rnbo/Gen patches.
it wouldn’t really be possible to do this…at least not for ‘all’ or even a majority.
vsts would first need recompiling to work (most are x86, mm is arm), and many you dont have the source code for… then you will find many vsts rely on other frameworks (eg. Juce) that would not work on the MM.
practically, even if source code was available, it’d require a dev to ‘port’ the vst over to an MM module, and that would be often significant dev effort (if viable)
rnbo patches (1.4.2+) can be made to run,
since there is an option generate c++ source code, and so you can compile to arm. also there is now (in rnbo 1.4.2+) an option to do a ‘minimal export’ which does not have external dependancies.
however, with rnbo, you cannot use any of the options that generate a UI, you have to use this minimal export / C++
which means you need to create and ‘hook up’ your UI to the DSP code it generates.
as mention before, I have a solution for this that Im working on.
so far, Ive been able to create plugins that do work on the MM (and Mac).
as mentioned (elsewhere) its similar to what Ive done for the SSP with rnbo, so should be an interesting solution for end users.
there could be other possibilities, in particular around pure data, and possibly csound.
with pure data there is a ‘converter’ that generates C++ that was used by the like of OWL, Bela and I believe Daisy.
I messed with an embedded csound library for SSP, that might work - though im not sure of its dependancies (SSP is linux, so is easier to ‘port’ things to)
actually, it could be interesting to look at the various solutions that Daisy offers, as these would be quite applicable to MM development.
Thats fantastic news !!! Running Max patches on MM would be a dream ![]()
you’ll be running rnbo patches, not max patches - similar, but different.
also, unfortunately, C79 charge extra for rnbo (on top of max) ![]()
note: only the developer of an RNBO based MM module will require max/rnbo , not users of that module.
one slight pain of all of this is,
if you are sharing with other users you might need to consider - are you just going to share the mm plugin, or do you want to share the vcv desktop version (both Mac/windows) as well? and do you want the hassle of submitting to the vcv ‘store’?
I might see if I can get this cross compilation done via GitHub actions, which possibly eases things a bit.
personally for testing , Ive just been compiling locally for both MM and VCV (Mac) , so none of this is an issue - but its a consideration if you plan to share.
anyways, venturing off-topic, they’ll be full details when Ive finished it ![]()
