volker böhm

hi - for anyone interested in running mutable instruments' plaits module inside maxmsp you can try out this new external. It's an alpha version built for macos. Feel free to report any bugs or problems you have to vboehm (at) gmx (dot) ch (not to mutable instruments!).

This is a temporary link. As soon as we have a stable version, it will be released as a package (including source code).

https://vboehm.net/xchange/vb.mi.plts~.zip

This was possible because Olivier Gillet generously open sourced the complete code base of mutable instruments' module line - thank you very much, Olivier!

ps: rings and elements are in the making...

hi - for anyone interested in running mutable instruments' plaits module inside maxmsp you can try out this new external.  It's an alpha version built for macos. Feel free to report any bugs or problems you have to vboehm (at) gmx (dot) ch (not to mutable instruments!).
This is a temporary link. As soon as we have a stable version, it will be released as a package (including source code).
https://vboehm.net/xchange/vb.mi.plts~.zip

This was possible because Olivier Gillet generously open sourced the complete code base of mutable instruments' module line - thank you very much, Olivier!

ps: rings and elements are in the making...


hi - for anyone interested in running mutable instruments' plaits module inside maxmsp you can try out this new external.  It's an alpha ver

-sharing-mutable-instruments'-plaits-module-macro-oscillator

That's great to hear !! Really looking forward to being able to get the stable version source code and compile it for windows ;)

very good work, this all sounds good. but the calibration of some knobs on some instruments react little weird. and considering the trig input, it looks for a gate which is not very practical nor precise. it would be nice that it could react to the trigger amplitude, allowing some dynamics.

It would be so great to have access to the instruments in the form of codeboxes in gen, it would be perfect to tweak and tune it to my needs. I would rellay enjoy to cross-modulate two or more of these too, but with externals it's not possible to make feedback-loops with just one sample delay, or at least it's not as convenient than using History.

beautiful work nonetheless and I'm looking forward to try your versions of rings and elements

edit : I noticed some fair amount of latency when in triggering mode.

very good work, this all sounds good. but the calibration of some knobs on some instruments react  little weird. and considering the trig input, it looks for a gate which is not very practical nor precise. it would be nice that it could react to the trigger amplitude, allowing some dynamics.
It would be so great to have access to the instruments in the form of codeboxes in gen, it would be perfect to tweak and tune it to my needs. I would rellay enjoy to cross-modulate two or more of these too, but with externals it's not possible to make feedback-loops with just one sample delay, or at least it's not as convenient than using History.
beautiful work nonetheless and I'm looking forward to try your versions  of rings and elements

@bertrandfraysse - thx for your feedback!

is this in comparison to the original module or is it a more general assessment? 

In the first case, I would be interested to get more info about the actual differences, as I don’t have a unit myself to test it against.

In the second case, you might be right, but right now I’m focussing on getting as close to the actual behaviour of the original module as possible, reguardless if some idiosyncrasies proof to be useful or not.

thanks - fixed. Have corrected it already for rings and elements, but forgot to change it in plaits.

you might like to look at what @.quasar has posted already in this thread

https://cycling74.com/forums/need-help-adapting-plaits'-grainlet-oscillator

but the calibration of some knobs on some instruments react little weird. 

is this in comparison to the original module or is it a more general assessment? 
In the first case, I would be interested to get more info about the actual differences, as I don’t have a unit myself to test it against.
In the second case, you might be right, but right now I’m focussing on getting as close to the actual behaviour of the original module as possible, reguardless if some idiosyncrasies proof to be useful or not.

and considering the trig input, it looks for a gate which is not very practical nor precise.

It would be so great to have access to the instruments in the form of codeboxes in gen, it would be perfect to tweak and tune it to my needs.

you might like to look at what @.quasar has posted already in this thread
https://cycling74.com/forums/need-help-adapting-plaits'-grainlet-oscillator 

Have you done this with Clouds by any chance : )

hi, i've done:
plaits
rings
elements
warps
frames
marbles
braids (in the making...)
... but no clouds, so far.



Amazing! Should I go back in the forum for the other externals or is there a link to where they can be downloaded?

links for plaits, rings and braids below. These are alpha versions for testing.

the others need (even) more testing, documentation and decision making, before I can put them up.

https://vboehm.net/xchange/vb.mi.rngs~.zip

https://vboehm.net/xchange/vb.mi.brds~.zip

links for plaits, rings and braids below. These are alpha versions for testing.
the others need (even) more testing, documentation and decision making, before I can put them up.

https://vboehm.net/xchange/vb.mi.plts~.zip 
https://vboehm.net/xchange/vb.mi.rngs~.zip 
https://vboehm.net/xchange/vb.mi.brds~.zip 

Wow these look great! Ill be watching for your updates. Has anyone done a OSX version of Marbles?

just realized that I started this thread pretty much 1 year ago - how time passes...

well, if anyone is still following this, here is an alpha version of the clouds module:

https://vboehm.net/xchange/vb.mi.clds~.zip

well, if anyone is still following this, here is an alpha version of the clouds module:
https://vboehm.net/xchange/vb.mi.clds~.zip


Haha... actually every project related in any way to programming is consuming more time than predicted. But I have to say, that I really appreciate your work and I’m keeping fingers crossed for further progress.

Haha... actually every project related in any way to programming is consuming more time than predicted. But I   have to say, that I really appreciate your work and I’m keeping fingers crossed for further progress.

Hey ! Really enjoy the work you are putting into this project. I am myself getting bit stuck on a gen~ adaptation of the Bandlimited Wavetable Morphing Algo (clicks when morphing due to the integration / differentiation dsp process I guess). I might get around to it but in the mean time I wondered if you were kind enought to be willing to share the source code of your plaits external adaptation ?

That would be great ;) Anyway it is no bother if you cannot !

Hey ! Really enjoy the work you are putting into this project. I am myself getting bit stuck on a gen~ adaptation of the Bandlimited Wavetable Morphing Algo  (clicks when morphing due to the integration / differentiation dsp process I guess). I might get around to it but in the mean time I wondered if you were kind enought to be willing to share the source code of your plaits external adaptation ?

What is the likelihood that this ever gets W10 support? :(

This is awesome! I would love to see the entire mutable instruments collection in Max. I have been using VCVRack a lot lately. I was thinking about trying to port some of them to Max. This gives me inspiration. Thank you for your hard work!

I'll put the sources up on github asap. just need to find the time to clean up (most of) the mess...

someone else can try a windows port from that - not me.

btw the latest versions and work in progress can be found here from now on:

https://vboehm.net/2020/02/mutable-instruments-max-port/

I'll put the sources up on github asap. just need to find the time to clean up (most of) the mess...
someone else can try a windows port from that - not me.
btw the latest versions and work in progress can be found here from now on:
https://vboehm.net/2020/02/mutable-instruments-max-port/


Hi Volker, any chance that i can build this stuff for Windows? thanks

Hey Alfonso - I guess this shouldn't be a big problem. The code has not been optimized in any direction.

just a quick heads up - current state of developement (including a few new objects) can be found here:

please note: this is still WIP (including documentation, help files etc.) - so things might possibly chance (without notice...)

just a quick heads up - current state of developement (including a few new objects) can be found here:
https://vboehm.net/2020/02/mutable-instruments-max-port/ 

and (finally!) sources on github:
https://github.com/v7b1/vb.mi-dev 

Mac catalina M4L user here. trying to check out these externals but receiving "vb.mi.brds~: cannot be loaded due to system security policy" message in Max console. tried turning off Gatekeeper but that didn't help. does anyone have a workaround for this?

If anyone achieve to build these wonderfull externals on windows, I would really happy to know how to do it...

Sorry if my question looks stupid, but shouId I use the Min package to build it?

If anyone achieve to build these wonderfull externals on windows, I would really happy to know how to do it...
Sorry if my question looks stupid, but shouId I use the Min package to build it?

windows builds are completely untested right now and will very likely not work with out tuning.

Should be possible to achieve in the future, though.

shouId I use the Min package to build it?

no, if you clone  the repository with --recurse-submodules
a version of the max-api from here will be included.
windows builds are completely untested right now and will very likely not work with out tuning.
Should be possible to achieve in the future, though.


it would be nice to make gen versions of them, or some of them, did a bit but it's above my head

Hey everyone, I'm still trying to build this on windows with no success.. :( 

If someone have done this, can I ask him to explain what we need to do? 

Hey everyone, I'm still trying to build this on windows with no success.. :( 
If someone have done this, can I ask him to explain what we need to do? 


these will work (as I've no idea how to use them!) but I built these from Volker's Github page this afternoon using a wacky combination of msys and Visual Studio 2019 (and luck/naivety !).

https://ilovecubus.co.uk/pete/vb.mi_win64.zip

vb.mi.clds~ for sure definitely works as I used 'my' compiled .mxe64 as a successful drop in replacement for the 'mac only' external required for Nube to work (a max for live device using the Clouds module - 

I can't 100% guarantee all these will work (as I've no idea how to use them!) but I built these from Volker's Github page this afternoon using a wacky combination of msys and Visual Studio 2019 (and luck/naivety !). 

https://ilovecubus.co.uk/pete/vb.mi_win64.zip 

vb.mi.clds~ for sure definitely works as I used 'my' compiled .mxe64 as a successful drop in replacement for the 'mac only' external required for Nube to work (a max for live device using the Clouds module - https://bit-01.net/free/  )

Does anyone know if these work in 64bit OSX Big Sur?

I'm using them quite bit, but will likely be forced to upgrade soon...

I'm using them quite bit, but will likely be forced to upgrade soon...

Thanks in advance

Here's a mac build of the externals that should support Apple silicon (M1) machines natively when running Max 8.2 and up.

vb.mi-macOS-Fat-externals.zip

I'll test them whenever my machine gets upgraded.

Or does anybody have a already running and updated version of the device for M1 usage ?

Bildschirmfoto 2022-08-01 um 14.49.27.png

Can anybody explain what I did wrong ? 
Or does anybody have a already running and updated version of the device for M1 usage ? 

See the brown object? What's the error message in your Max window?

vb.mi.rngs~: could not load due to incorrect architecture

Are you on an M1 machine? My first guess (and it would be a guess, since you haven't told us what kind of machine you're running it on, etc.) is that. You're trying to run an external that's not been compiled for M1 on an M1 machine.

Well I did certainly tell that, I asked if anybody has made a working build in my post. 

But to make it clear, I am on a Macbook with a M1 Max Chip.

And I use Ableton Live 11 Suite with 11.1.6 as the build from 13 06 2022. 

Could it be also a problem that the externals can't be located? 

I used the linked file from above an tried to replace the original with it, under the impression of making it work with a M1 Chip. Atleast thats what I thought I do.

Well I did certainly tell that, I asked if anybody has made a working build in my post. 
But to make it clear, I am on a Macbook with a M1 Max Chip.
And I use Ableton Live 11 Suite with 11.1.6 as the build from 13 06 2022. 
Maybe this helps. 

Could it be also a problem that the externals can't be located? 
I used the linked file from above an tried to replace the original with it, under the impression of making it work with a M1 Chip. Atleast thats what I thought I do. 

[sharing] mutable instruments' plaits module (macro-oscillator)