Critter & Guitari Organelle

[shreeswifty]

And the hits just keep coming in organelle country

[looks at bob corrigan] ahem

[widdly]

Interesting. I’d be very interested in your approach. I’m hoping to integrate a lemur patch with the organelle pd stuff and I want to find an approach that will work without having to modify every organelle patch. I’m hoping to add cv inputs as well.

I’m hacking up an organelle clone on an Rpi. At the moment it does everything an organelle does but I’m looking to extend it to take advantage of the extra cores on the Pi. I’m using a coloured TFT screen, an arduino via usb serial doing the knobs and buttons and a 6 in 8 out audioinjector sound card.

I’ve added an osc message to stop/start a pd patch inside mother.pd so it doesn’t need to exit and reload the pd application each time the patch changes. I am running 3 instances of pd~ inside the mother.pd, each running a different organelle patch. Each pd~ runs a modified mother.pd with different osc address. I’ve modified the mother c++ application to have an array of menu and app objects so it can maintain the state of 4 different organelle’s and switch between in response to a button press. I’m having a bit of trouble getting around the way the organelle uses the tmp directory for running patches but I’ll get there. I’m thinking I might need to write a script to parse the pd files in the patch directory to replace references to /tmp/patch with /tmp/patchx where x is the pd~ instance it is being loaded on.

Next step is CV/Gate inputs and outputs. I’m thinking I could make these appear as midi sources in pd and extend the organelle midi channel menu to allow the selection of a cv/gate source/destination instead of a midi input/output.

edit… Found your github page. nice!

[TheTechnobear]

sounds like a cool project @widdly
p.s. /tmp/patch… be aware, Im talking with owen about extending/changing this… basically as id like to separate data/preset storage from the patch directory.

interesting comments on the multi core aspect, not something I’m tackling at the moment, though its is something ive considered a little on how id tackle… one though I had thought was to ditch mother host from launching the PD application, and instead have mother host use libpd, so this would enable it to track multiple patches correctly… basically acting as a PD host (something like the way a DAW hosts VSTs) … but thats a non-trivial task.

generally though, I think Im trying to solve a similar issue as you, but in a different way…

In no way am I trying to clone an Organelle (no need I have 2 ) on other platforms,
rather I see the problem as one of hardware abstraction in patches

The issue I have, is I don’t think PD patches should be written so that they hard code the control interface… imagine if VSTs assumed a certain display size, or having 4 knobs… no, I patches should abstract this, and then it is the ‘controller’ that should have code written that can ‘render’ that patch in the most appropriate way.
again the VST example is very relevant… whilst they can render their UI, they also present a unified parameter list… and this is how things like automation are possible.
(amusingly, MEC, which oKontrol is part of, also runs as a VST, so theoretically, I can allow you to control oKontrol parameters from your pi/Organelle from the mec VST running on your PC/mac in a daw )

… its also why I think OSC is useful, so not only is there a PD external, and C++ api for interfacing, but also a ‘wire interface’.
(btw: im happy to talk to other developers about the osc messages, and how they might be improved)

why is this only coming up now?
I don’t know, I was genuinely surprised when I first looked (2 months ago?) at PD that there was not some kind of standardised parameters/preset system, that all patches used.
but I think the reason is, most PD patches were written for PC/Mac with screens, but here - we are interested in headless patches, patches controlled either remotely, or from midi devices, etc etc, perhaps this use-case is just now relevant to more people on different ‘micro’ platforms.

(as a side note, any talk I’ve made of a oKontrol touchscreen interface for the Pi actually has had a lukewarm reception, its a nice to have, but musicians seem more interested in getting physical control integration)

of course, my approach requires patch developers to adapt, and to ‘buy in’, which i will only be able to convince if they see big advantages e.g. easy to implement, and nice interface for users … so thats my first target.

fortunately, as I developed a whole bunch of Mutable Instrument patches which seem quite popular, I can use those as these guinea pigs… to let developers and users alike see the advantages (or not).
if they think it looks cool, and they like , they can use … if not, then perhaps it will inspire something else, this is what open source is all about (for me)

anyway, Im excited by the response so far… seems others also think this is an important piece of the puzzle for these kind of hardware setups

anyway, less talk , more coding!

p.s. another side of this , for me, is its not just about PD!
e.g. after then next Axoloti firmware release, I plan to build an oKontrol interface into axoloti, so that Axoloti’s parameters are exposed onto the same infrastructure… so then ‘controllers’ build to use oKontrol to control PD patches, will then be able to control axoloti patches as well…
as I said, its all about abstraction

[bobbcorr]

It’s starting to look a lot like Christmas

[shreeswifty]

hahah.

My mom and i always use that but we sing
It’s starting to look a lot like Chicken

[Willogese]

that sounds to be amazing, I support your ideas, they truly are amazing, guitar is the only instrument which calms me down. i search for https://rxcoupons.org or such sites because of my nerve issues and lack of money. but it is amazing! you should try to make this project real!

[TheTechnobear]

So… not only have I been writing software, and partnering my Organelle up with other controllers…
Ive just upgraded its little beating heart

before : 1 core, 512kb ram… after 4 cores , 2gb ram, internal wifi

really happy, was a bit of a risk (and I will be monitoring core temps), but is working perfectly…

Ive yet to do any performance testing, but I suspect it will be similar performance to my rPI3. the main difference being its got 2x ram, and a 32 bit rather than 64 bit process (a9 vs a53).

cost… really good, I found cheapest way to get the new microSOM was via a cubox i4Pro, and which I can even reuse with the old microSOM… and cost me 150 euro, not bad at all.

[misuba]

Organelle transplant! This is hot stuff (hopefully not literally)

[TheTechnobear]

so been doing some tests… against a factory organelle.
for same PD patch the quad core is running cooler, about 6C (10%)… I’m assuming because some ancillary tasks (only about 2-3% cpu) are booted off to a 2 or 3 core… so looks like its fine.
(and when I pushed it with parallel compiles it recovered pretty quickly)

however, which brings up a technical linux question…
so Organelle sets the cpu scale governor to performance , which basically means no cpu scaling…
this is to be expected for a musical device (you don’t want to start scaling back processor speeds whilst processing audio)

the question is, the text says its a static frequency, but does it really not even scale back if it hits critical temperature?

I ask, because I do often compile things on the Organelle, which obviously creates high cpu loads for a prolonged period, and I’m now wondering if i should really disable performance scaling whilst compiling.
(its not really a 4 core issue… as the same is true for a single core… but just i happened to be monitor temps whilst doing parallel builds ;))

[jasonw22]

I am still stuck on “the Organelle has a user-replaceable CPU? How forward-thinking!”

[TheTechnobear]

another month, another way to use your Organelle

Question for today: is Organelle a Synth? a Sequencer? an FX unit ? a Generative synth?

the answer is yes, and, today mine has taken on a new role - a video synthesiser, in the shape of C&G’s Etc

more details here:

OTC - ETC on Organelle

You gotta love C&G, not only great hardware, but their open source approach allows you to take things in new directions.

btw: I have checked with C&G before doing this, and they are ok with it.

note : this runs on a vanilla Organelle, not just my supercharged one.
note2: this is now released on patchstorage here, install instructions on the above thread.

[TheTechnobear]

a quick shout out to @ghostly606 for doing a much better demonstration of the possibilities of OTC, than I did , thank you…
as a developer, the greatest gratification comes from others using your efforts

and again thanks to C&G for their whole attitude/support … a great example of why we need to support the small/boutique guys!

[TheTechnobear]

So Ive got supercollider working on the Organelle with all the hardware working, keys, knobs, oled, and its launched in exactly the same way as other (PD) patches, so user doesn’t care if its PD or SC.

and really liking supercollider for patching, its so compact… perhaps because I’m not really a GUI Patching type programmer

heres an example of what a patch looks like so far

// initialise
~voices = Dictionary.new;
~cutoff = 5000.0;
~oled.screen(1,format("Cutoff % Hz",~cutoff.asInteger));
~oled.screen(5,"Test Patch Loaded");

// create knob callback
~knobfunc = {
    arg func, msg, knob, value;
    if(knob==0, {
        ~cutoff = value.linexp(0,1,50,20000);
        ~oled.screen(1,format("Cutoff % Hz",~cutoff.asInteger));
        ~voices.values.do({
            arg  v;
            v.set(\cutoff,~cutoff);
            }
        );
    });
};
// register knob callback
~knobs.addDependant(~knobfunc);

// create keys callback
~keyfunc = {
    arg func, msg, key, vel;
    if(vel>0 , {
        if(~voices[key]!=nil,{~voices[key].set(\gate,0);});
        ~voices[key] = Synth.new(\testSynth,[
            \freq, (key+59).midicps,
            \cutoff, ~cutoff,
        ]
    );
    } , {
        if(~voices[key]!=nil,{~voices[key].set(\gate,0);});
        ~voices[key] = nil;
    };)
};
// register key callback
~keys.addDependant(~keyfunc);

// a boring synth
SynthDef(\testSynth,
    {
        arg freq=440,gate=1,cutoff=440;
        var sig,env,amp=0.3;
        sig = Saw.ar(freq);
        env = EnvGen.ar(Env.adsr(),gate,doneAction:2);
        sig = sig * env * amp;
        sig = LPF.ar(sig,cutoff.clip(10,24000));
        Out.ar(0,sig!2);
    }
).add;

a breakdown of whats its doing is here

a few more features to add, but its getting close to being released as a v1.0 (or 0.2 )

thanks to help on the supercollider thread here… loads of great tips, the ‘addDependent’ stuff was really useful for a newbie like me.

[TheTechnobear]

OK, its released into the wild … well patchstorage anyway.

more details here

Basically, you’ll need to :

• Install SuperCollider with SC_Installer
• Install my latest Organelle ‘firmware’ - 2.2 TB 17 ,
  this provides the ability to launch SC patches
• Download the sample SC patch, put in your Patches directory , run it, and then explore it

support includes:
audio in/out with vumeter, master volume control, oled, led , knobs, keyboard, other inputs.

[kisielk]

Sweet. Now I really want to get an organelle.

[TheTechnobear]

yay, OS 3.0 is released

Organelle OS 3

[bradfromraleigh]

Looking forward to using this - I had two failed upgrade attempts last night but I’m thinking there was an issue with copying the file on my machine. Will try another computer tonight.

[TheTechnobear]

if you have issues post on organelle forum, let us know what version of the OS you currently have installed , and also exactly what th error is.

for testing I did install on both a ‘clean’ organelle with 1.0 and 2.1 on it.

[bradfromraleigh]

Thanks! I wasn’t going to post over there until I ruled out my computer as a potential culprit. For whatever reason, the drive took minutes to eject after I copied the file. Very unusual. I’m thinking the problem is on my end.

The update looks great though! I’m curious as to the doors the wifi support may open for this thing.

[sakul]

you already made me buy an organelle with your previous contributions.

chapeau and thank you so much!