Enable input monitoring?

Thanks so much mate. Puts my mind at rest. I’m going abroad with work for 4 months and want the simplest setup possible to just jam. Can’t really be bothered with a mixer, just want to take headphone out from Organelle and hear my OP1 if needed.

Yes Ghostly I’ve seen you around too, and you’re videos of OP1 and Organelle caught my attention. How are you finding the two? I’m rrally interested to find out what workflow you are finding best with the two machines.

i really just can recommend to start with PD and organelle. i own a OP1 as well, but since i started with PD and this blue fella i rarely use the OP1 except to record stuff to the OP1 4 track-recorder :smile:

thanks @ringhof , all this talk of OP-1 always makes me have a bit of GAS, always sounds like the OP-1 and Organelle are a great combo.

that said, the OP-Z is fairly imminent, so id really like to see what thats capable of, what it will bring to the Organelle table…
my guess, is after initial comparisons to the OP-1, its going to turn out to be very different ( so complementary rather replace OP-1) - so will be a case of what suits your ‘needs’ more.
(and then the whole visuals side is going to be interesting, perhaps inspirational for OTC :wink: )

1 Like

Understood mate. I plan on doing just that. But ultimately my aim is to use the organelle as an FX processor at the end of my instrument chain, not as a synth. So I will be plugging op1, vocals or guitar into it. Clean input monitoring is kind of essential for times I’m not using Organelle as an FX processor so I don’t have to keep patching and in patching gear.

Honestly the OP1 changed my musical life! Before I owned one I was obsessed with seperating everything down to each hi hat and kick in ableton, post processing etc. As a result I rarely made any music. Since the op1 Ive embraced the lofi side and experimentation. I’ve even bought an old cassette four track recorder to capture my ideas instead of using a computer. There’s something really inspiring about it and ‘loose’ rather than snapping to grid etc.

I’m actually in the process of selling my elektron (Digitakt + Octatrack) gear because I just want to go back to basics. Simple little setup with portable devices, couple of FX pedals. Do you think the organelle will fit into this philosophy?

1 Like

i agree with getting rid of PC while in a musical process.

but don’t underestimate the ability to chain things like synths and FXs as well as midi messages together in PD/Organelle :japanese_ogre::star2: its a beast

1 Like

@lescour1 going back to bypass/monitoring

the option I detailed, is of course not a ‘true bypass’ , since the signal is still coming into the organelle and out (so adc > dac) , this is cool most of the time, but as mentioned you have to be careful of gain, and also it’ll introduce a tiny bit of latency. (not that you’ll ‘feel’ it)

if your interested in ‘true bypass’ , this thread might interest you.

(its not easy, but perhaps something to consider in the future)

though honestly, I think , if i wanted to do this, Id add a small mixer as adds a bit more flexibility.
so you could use OP-1 into Organelle directly for a portable setup, and the mixer when you need a bit more control/options.


Simple setups.
yeah, I feel you … as a bit a geek, when i started on this journey into music, I bought things based on them giving me options, so now I have so many options both in hardware and software at times it can be ‘stifling’ , where to start? what to use?

honestly, i think the answer for me, is to be more disciplined/focussed… have the options, but choose in advance what to use, and don’t keep thinking ‘what if’ , (thats my plan at least)
so Im not really into getting rid of anything, just trying to learn to pick n choose better.

Organelle - hmm, well it definitely adds a lot of options, so can ‘replace’ quite a few things, and is great for experimentation. I think like many instruments that are really flexible they work best in setups with ‘less’ in them, since you can then focus on IT. if you have tons of gear, the danger is you just keep dipping in and out of it.
(that said, I keep coming back to it, so it does draw you in :slight_smile: )

Octatrack, Ive been eyeing up an OT.
honestly… if i were you, if you can , id try using it with the Organelle for a while then chose to sell or not.
the reason is… the Organelle does one thing at a time, so the recording/sampling into an OT will be fun, similarly it can sequence, but using the OT to sequence could also be fun… and then finally as above, having a mixer could be useful.
I think it would be useful , to see how you like it perhaps the OT+ Organelle might be more useful than the OP1+Organelle - depending upon what your up to , and how portable you want to be.
(I guess the digitakt could be used as a smaller alternative to the OT, but you know that choice better than i do )

of course, if you want to do backpack stuff, then yeah, OP1+Organelle is really a winning combo.

See my post about enabling input monitoring (you’ll have to modify mother.pd) : TB - UpdateOS 2.2 TB Beta - closed -> use official OS 3.0

Thanks mate. Sorry for ignorance as I’m a very new user but can i just confirm that following these instructions I can permanently enable audio monitoring on all patches, but there’s no way to turn on/off? Is that a correct assumption or am I missing the point?

I don’t have my organelle yet to play with these scripts so I’m just stabbing in the dark here!

Thanks for detailed reply mate.

Yes I do consider myself a fairly experienced Octatrack user, and it would kill me to sell. But to explain abit about my background…im in the military so do a fair bit of travelling away, as well as courses and then going back to my permanent residence at weekends. In my accommodation on camp I have my full setup / studio of sorts with OT and DT, Analog Heat etc. The problem with this is when I’m away way from the studio for away way few days I tend to not make any music. I take my OP1 with me and mess away way round abit with ideas, with the mindset of ‘that’s not finished, il work on it later when it back in the studio’. Inevitably ‘later’ never comes and I ultimately end up with a bunch of loops and half finished ideas. Also the problem exists that when I do fire up the Elektron gear I’m able to create quite complex beats and nice loops using vocal looping etc, but they always stay as half finished ideas. The gear is so deep and complex before you know it’s midnight and I leave it.

I guess what I’m trying to say, is the most productive I am is with small peices of gear i can patch in different combinations, composing on the move with gear I can fit in a backpack.

Throw family commitments in there too, as I get older I feel that its essential I have a setup where I can quickly get ideas down when I’ve got an hour or two spare whilst the wife is watching TV or whatever haha.

1 Like

Actually there’s a way to turn monitoring off : load another patch. It will reload mother.pd and thus monitoring defaults to off. As turning monitoring on is not very straightforward anyway, i didn’t bother to program the turn off.
As you can probably see in the run.sh, you just have to make a copy of it in another folder and modify theses lines:

# Activate audio passthru
oscsend localhost 4000 /audiothru i 1
oscsend localhost 4001 /oled/aux/line/2 s "audio passthru ON"

to :

# Deactivate audio passthru
oscsend localhost 4000 /audiothru i 0
oscsend localhost 4001 /oled/aux/line/2 s "audio passthru OFF"

OK mate. So if you were using organelle standalone away from computer you would make 2 x patches…one with audio enabled and one with it deactivated?

Sorry, i meant that to deactivate monitoring once it is enabled, for now you have to load another patch or reload the same patch, as this will also reload the mother patch and thus default monitoring to off.

If you want to deactivate monitoring without exiting the current patch, you’ll have to make a modified copy of the system script that enables monitoring.

In all honesty I would leave mother.pd alone and just add monitoring in on a patch by patch basis.

You could assign a controller (knob or aux or footswitch or external MIDI) or have a version with and a version without as you suggest.

1 Like

Haha I’m glad someone else is talking my language. Honestly I think some of these guys are too clever for thier own good :smile:

I’m happy just editing each patch and saving 2 versions. …one with monitoring on, on with monitoring off. I can always just mute OP1 if I don’t need it to be heard

sorry @batinste , I was wrapping up the 3.0 release when you posted this, so it slipped by mind :slight_smile:

@oweno seems like a simple thing to add to mother.pd and have some control of…

I thing rather than a simple on/off , Id prefer audiothru to be a percentage… so you can determine the level you want to monitor at … 0 = off 100 =full input, and yeah put a line~ on it, so that it has a small fade, so you dont blast someones head off quickly :wink:
sure you can think its duplicate if a patch already has a monitor feature, but the patch (in a new version) could then either remove this option from its parameters, or interface directly to the mother.pd to control it. (this is actually useful, as for some patches, you might want quicker access directly in the patch)

Could this be in the overarching menu structure then? Maybe an Audio Settings sitting beside WIFI Settings and MIDI Settings?

It would be easy to make it controllable from the patch. Either set the passthrough at loadtime or set it from the parameters of the patch or from audio settings.

For minimum added latency it shouldn’t use throws~ or sends~ (i’ve just thought that the current mother/patch mechanism adds a block of latency, hum… I’ll see what i can do about this :stuck_out_tongue: )

thats kind of the idea of the setting menu… and where ive just added Pedal settings (3.1b3)

I think audio settings is possibly another one that could be added, not only could it have this passthru option, but potentially later could be used for other audio settings that are available thru the OS (e.g. amixer settings to do with gain, even potentially audio interface)
however, im a little cautious…

Organelle is built to allow patches to do anything they want, so theres always a bit of care needed not to ‘force them into a box’… also lots of settings makes a product look complex

an example… Midi Settings allows midi channel to be set, but it really difficult to explain to users (unsurprisingly) that this only affects the mother.pd behaviour, patches can also (and do) hard code midi channels.

its a tricky one though… as also many users want to do things which are technically possibly, but they don’t want to do using a ‘terminal window’, as they have no linux experience.
(id expect 3.x will see lots more users using Wifi, simply because its much easier to do now)

so balancing act… make it easy to use, not overly complex, flexible and let patches do whatever they want.

i know it will work as others do (e.g. midiInGate), so basically the osc message is converted to a send, then the receive sets the level… so the patch can just do a send if it wants to force a setting.

one area i can see where patches will want to turn off input monitor, is when they have a Mix Dry/Wet setting … e.g. on an fx, then input monitoring really doesn’t make much sense.

I guess this goes back to @lescour1 use-case, which is input monitoring for synth patches, but not fx patches…
(unfortunately we do not know when a patch is each, and some patches are both … like Wrps, this can be synth, fx or some weird hybrid )

Yeah all this stuff is too deep for my own perdonal use at the moment. Being new to PD and not yet with organelle in my hands it’s all over my head abit.

As stated my plan is to have organelle at the end of my chain with instruments going into it. Most of the time my goal is to manipulate the incoming audio via FX. However there will be instances I use organelle as a drum machine or synth for accompanying my vocal and / or OP1. In the latter instance I would require input monitoring on that patch to save unecessary cabling and mixer ins/outs.

These are just ideas at the moment of course. My plan may change when I start using one