Orac module ideas/already exist?


#1

With these new possibilities dropping from gods, got me thinking about organelle very differently and looking around for a few features for modules. Feel free to add other ideas if anyone has them :slight_smile:

Some requests to the clever ones (maybe some exist for port already in patches I’ve missed?) -

  • Sequencer/Arpeggistor/Transposable step sequencer with pattern bank memory? To be able to flip between different patterns. Also wondering whether Orac can multitrack sequence from one sequencer? Like on an Elektron box etc. If so, then Organelle is missing a multitrack sequencer AFAIK?

  • A step sequencer with Step Components/Conditions etc. Like hold the wooden key for a step and the knobs cycle through various options for that step. Like op-z and quantum on iPad. Something like this and with scale and randomise options would be amazing.

  • Some kind of CC snapshot performance module. Where you can assign multilayer CC snapshots to each wooden key. With hold vs toggle option. So for instance you could hold one key for massive reverb with tremolo and pitch shift on a synth. Another key for weird granular delay on a sample. Another to activate freeze globally. And flick between them or hit them all at same time if you liked… Kind of like Octatrack Scenes without the fader. Or could maybe even have it so there’s also a fader kind of function via one of the knobs… And maybe some buttons at far right of keys could be have set bpm sync’d Lfos on them. So you hold one of those first and then when you hold one of the keys with CC snapshot it alternates wet/dry via the lfo. Like have 4 buttons at far right of keys with different lfo divisions/multipliers…

Dunno how feasible any of this is as I haven’t had time to even update my organelle and install Orac yet :frowning: Excited to get on it this wknd. Maybe the cpu or view switching would make some of this stuff too much of a PITA to be worthwhile. But if these kind of modules could be made to flow nicely it’d be huuuuuuge :slight_smile:


#2

I thought to have a master recorder on one of the master slots and then a .wav player to use in one of the chains, pretty much used like a stem. The player could then select newly recorded files from the recorder and apply new effects.


#3

Super exciting times. It’s no coincidence I sold my OP1 yesterday! :sunglasses:


#4

yeah, this is a good point…

so the converted modules came around for two reasons

  1. to give everyone something to get started with :0
  2. to ‘prove’ the platform to myself, by converting a wide variety of modules, and see how long it took.

I actually intended to do about 30 modules (1) , but it proved so easy (2), I kept doing more.

so I do think we will find, as we all play with Orac, that some modules are more suited than others, and I have (re-)discovered a few C&G patches that I didn’t use before, but really like on Orac (e.g tuned delay, rythmicon)

But, a strong reason driver behind is to make modules easy to create, by removing some of the ‘burdens’
So my hope is, after that thru playing with what we have, this will generate new ideas for modules, some wont even be that complex, but will just ‘fit’ the environment nicely.

I do have an idea for this, a bit more generic and needs a bit of work on the Orac, but the basics are implemented already. (no details yet :wink: )

Personally, one thing id like to avoid is modules that require other modules to be present, or modules which assume only one is loaded, or are in a particular slot.
I think this will confuse end-users, so Im keen to keep the user experience consistent.
(also by definition these things constrain users too)

anyway, very early days, I think as we all explore, different ideas will come up…
this is why i was so keen and excited, to get Orac into your hands, to see what you can make of it


#5

You tease! :stuck_out_tongue:

Fair point - how about having a recorder within Orac as standard at the end of all the chains?


#6

yeah, ive had discussions before, about if Orac should have some ‘fixed’ modules (e.g. should clock be part of the infrastructure).
But at the moment, Im hesitating, I recognise this might help the user experience, but it also adds constraints, e.g. who am i to say, some musician doesn’t want a strange clock that speeds up and down with a mind of its own
same with a recorder, im sure many people have different ideas for recording, or where in the chain it can be… e.g. perhaps you want the recorder before the fx.

thats kind of the difference for me , from say the OP-1 and Organelle.

Teenage Engineering have done a fantastic job of tying everything together into a really coherent experience, but ultimately they dictate the workflow/the experience. so thats a constraint (albeit it, in a huge sea of possibilities!)

With Orac, I wanted to keep as much flexibility as possible, letting the musician (and module patchers) choose what they want, and let the cream (best modules) rise to the top.

Of course, I have added a few constraints, in the name of user experience (and to make module patching easy!).
so for sure, there are always compromises to find the right balance… and Im sure we can improve on this over time, as I get more feedback etc


#7

Standard request but an sp404 vinyl sim/wonky BOC type effect module would be cool… Can possibly build one already with the available modules but for convenience and easy tweaking it’d be great to have it inside of one module.


#8

So - a thought from the night :slight_smile:

poking about in orac, organelle and mutable source code yesterday gearing up for a few of my own orac modules…

it occurs to me that having the chains come together in a Mutable frames mixer

https://mutable-instruments.net/modules/frames/

might be very exciting!

(obviously the ‘coming together slot’ could be any mixer - and I guess you already have implicit mixing in there? so even just having an explicit mix module could be kind of useful - or can you midi control the levels of the chains anyway? not explored that part yet )

don’t know if that’s an easy or hard thing right now but thought I’d put the idea out there!


#9

Yes, one can already midi map master volume IN and OUT and individual module main volume; all this (and midi Thru) on the routing modules.


#10

Sounds like a custom router module to me, based on frames (saying this without actually having looked at the inside of router modules)

Sure would be ace!

(Would be way cool to have some sort of touch strip input for each of the four channels which always reflect the levels)