#7

has anyone got the links to Timo’s Max externals?

BTW: Ive also ported the MI code over to pure data - Windows/Mac/Linux (arm and intel)


(and as someone mentioned elsewhere to Axoloti)

on Arm, Ive also done some patches, that run on the Organelle, and rPI.

currently Ive done, Clouds, Elements, Braids, Warps - Rings is done (iirc) but Ive not done the demo patches for.

porting these externals over to Max, I guess should be fairly trivial… but no point, if someone has already done it - Im actually a bit tempted to just create a bunch of VSTs instead :wink:

4 Likes
#8

VSTs would be even better!

#9

Quoting Olivier, the creator himself:

[…]Clouds won’t make clouds unless you patch attenuated random sources to its CV inputs (corollary: your Doepfer mini-case with Clouds and an Intellijel audio interface is not what I would call a good starter system).

Maybe you should experiment a bit with Clouds’ CV inputs. I mean, nothing wrong with using it like a “static” FX module imho, but I think there’s a lot to discover, that one does not suspect being there, going beyond that.

3 Likes
#10

Haha I knew someone would pull that quote up. I guess I actually do a lot of twiddling of clouds in lieu of cv.

#11

They are included in the “unfrozen” version. But he seems to have only compiled the mac-version, so no luck for linux/windows users.

#12

Sorry I should have been clearer , I meant the source code for the max externals.

#13

Damn…always a bridesmaid, never a Shades port.

3 Likes
#14

could you point us to any tips on how to begin with these… I really don’t understand what it means when it says you can use ‘make install’
in the terminal window?
not even sure which files to download from the github… do i just use the ‘clone or download’ button and put everything somewhere?

any pointers welcome!

#15

sorry, i don’t have the bandwidth to explain how to build these things…
(it requires you to have various developer tools installed etc… and that is not simple on some platforms)

I’ll try to release some binaries builds asap, though I’m pretty busy at the moment.

#16

There’s a dark force that makes me quote Olivier in these situations sorry :smiley:

4 Likes
#17

You could open the M4L in Max 7 then use BEAP signal to VST parameter & a DC coupled interface to do CV manipulation of parameters no?

also this reminds me of my favourite Eurorack joke:

Q: Whats the difference between Mutable Instruments Modules and a VST?
A: Rogan knobs.

1 Like
#18

I was poking around the braids one by clicking the “view in max” when it was on a track in ableton…didn’t seem like anything was compiled in a way I couldn’t get access.

#19

@jlmitch5 those would be the compiled binaries. He’s looking for the source code for the externals. That’d be C/C++ code.

1 Like
#20

Ah gotcha, yeah everything I was seeing was basically interface “code” (“midi signal gate and pitch is split and sent to this other place” kind of stuff)

#21

yeah, not talking about patching at all. source code = text files

1 Like
#22

Thanks for your work.
Using MI4PD sources could port clouds external to Max in Windows 10 x64.

Still experimental so you can get some bugs and crashes while testing.
Feedback is appreciated:

1 Like
#23

cool @xnamahx

btw:keep an eye on my repo, as Ive got a few ‘bug fixes’ planned for it.
and Ive recently committed a fix for Braids where I noticed one of the parameters was not ranged correctly.

also is worth noting, as Im not really targeting windows/mac os as a primary platform, Ive not really cared about sample rate.
the issue is :
the MI code is based on a a fixed sample rate (as its hardware!), these assumption are in quite a few places including various tables… the only fix for these on a variable sample rate platform is to re-sample, but Id didn’t implement this, as on things like a rPI/Organelle this would be too cpu intensive, but of course this is a non-issue on desktop/laptop (this is exactly what things like VCVRack do, I believe)

upshot is, you probably want to resample from current sample rate (up or down) to 48k.
(of course if you happen to be using 48k, it a nop )

#24

Is this in some way relatable to the issues I have reported over at the blokas.io forums? I noticed some strange behaviour with the “Shape” parameter when adapting your Organelle patch to work with rPi/Pisound.

#25

no :slight_smile: that’s to do with some oscillators requiring something done a little differently.
(i need to review the code to remember what exactly!)

the issue was, when I created these I was ‘flying blind’, as I didn’t have the modules, and VCVrack didn’t exist… so I wasn’t actually sure what some of the functionality was, and so what the code was doing… so I left a few corner cases out.

I now have a few real MI eurorack modules, so have a better feeling for how they all work, so I can fix these little oddities. However, I will probably do Plaits first, as I have the Plaits eurorack module, so I can easily verify its functionality first hand. (with Braids, I’ll just use VCVrack as a reference when I get around to it :slight_smile: )

#26

Well, I’ll gladly “upgrade” the pD patch to Plaits, so don’t worry about that! Thanks for your work on this one btw.!
And now let’s close this matter (or open a new topic), because I guess we’re derailing the thread here a bit (sorry about that!).

2 Likes