Rights I see it now. That clears it, thanks.

On GitHub - pichenettes/eurorack: Eurorack modules

We do not recommend you to keep the original name of the Mutable Instruments module for your derivative works.

1 Like

No unfortunately no idea. I’ll send you my revised macro B version later. I have completely rewritten the Lua script and added another trigger command in the supercollider file. This was certainly not necessary, but it helps me to understand the Norns scripting in a better way.

I should also pay more attention to the use of MI names. “Oscillator code from Mutable Instruments” is her preferred form of citation. This is based on the discussion regarding the Arturia Microfreak.

2 Likes

I saw that you’ve rearranged the screen (or that what i think I saw), so i figured some rewriting might have taken place. These things are so much fun.

In addition to the stereo fixes I’ve added MIDI channel selection. From what I see and from the good work already done, there would be some good possibility to expand these and also maybe bring some of the other MI engines in.

2 Likes

Recently finally got around to trying these, super excited by the sounds! I am not sure if things are fully working, I have everything mapped to knobs on my Nanokontrol and the parameters change but none of the on-screen dials (except the ones controlled by the 3 Norns knobs) actually move when I change things. Is this normal / can I fix it?

1 Like

which script were you using?

1 Like

All of them (ie the Modal Synth, Macro oscillators etc that come with the install - haven’t tried the ugens in pedalboard or adding them to any other script)

1 Like

i’ll load them up and poke around today, unless @okyeron beats me to it :slight_smile: it’s probably something simple.

1 Like

the midi event probably isn’t triggering a display redraw (or getting the param state)

3 Likes

Tried again and Resonate-R does update the knobs when midi-controlled, the others don’t.

EDIT: also, Macro osc B script only seems to work in the right channel

I’ve been wondering since the ER-301 has become open source and is in Lua, if anyone here has a 301 and would consider porting these engines over to it?
I think a resonator would be fantastic in the 301, anyone keen to give it a shot or point me in the right direction?

This is the development topic for the 301:

Developing for the ER-301

3 Likes

this project is a thin wrapper around MI module DSP routines to make them usable from supercollider, and thence from norns.

there is nothing to stop someone from attempting to wrap the same routines in custom er-301 DSP objects. but the projects will have no overlap aside from wrapping the same stuff.

and, i have no idea if it is a reasonable goal. the er-301 DSP object interface is rather different, uses a per-frame callback, i don’t know how many resources a custom Object can allocate, and it would take a little bit more work than has been done on the SC wrapper to make it performant.

API:

example object implementation:

2 Likes

Thanks for the info!
I didn’t think it’s would be overly easy. It definitely looks beyond my skill level.
I may repost this on the 301 forum to see if anyone is interested and able to make this happen. If not I’m
Hoping someone can code up a tasty resonator with a similar vibe to rings!

I’ve submitted a PR that fixes the UI redraw when changing params (either through midi or the menu). It might not be the most elegant thing ever, but it’s working fine on my end :slight_smile:

2 Likes

I’ve no time to look at this for a week or two. Please bug me again in a couple weeks if I otherwise don’t get to that. Thx!

3 Likes

Still would be amazing to get the on-screen knobs to update while midi-controlled, want to use these live but it’s too confusing playing blind :slight_smile: @okyeron did you ever get a chance to look at @MentalSandal 's PR?

No, sorry. Been super busy. :frowning:

1 Like

Sorry I forgot to mention that I’ve only modified resonate-r, but it should be easy to implement the callback in the other mi-engines. I haven’t done it yet because I’d like to get confirmation it’s working for other people.

Here is my fork if you fancy giving it a go :slight_smile:
I’ve tested it with my model:cyles as a sound source and controller (which is remarkably well suited to this script) and also a launch control XL. Feel free to flag any issues you may encounter!

1 Like

Ah yeah had a look and realised that :slight_smile: Cool will have a go with your fork and try editing others similarly if I get it to work.

1 Like

is the installation process in the open post still the way to go?
Btw, I’d love helping you test and develop these engines if needed, is there a todo-list/trello somewhere?

2 Likes

I used that process last week and it worked fine!

1 Like