You kick ass man. This is gonna be perfect for my guitar pedal setup. Using a ton of midi pedals (chase bliss) and the program change for the presets is perfect. I was gonna try and make my own patch that did this particular thing but now I don't have to haha.
Thank you so much for Orac and for these guides! I'm going through this one while following along and learning the features little by little. I have a couple questions I was hoping to ask about... 1) Is there a way (via presets or another method) to have modules save associated files recorded to them? I tried out the Overloop patch, and it seems to be working, except that if I close Orac (or the Overloop module within Orac) and load it again, the recordings are gone. 2) I'm having a little trouble managing presets. I was able to save a new one on the Organelle, load it later, and also save it as the default preset to load. However, when I access my files on my computer, I don't see that new one (in orac>data>orac>presets). Also, when I delete old presets on my computer (also in orac>data>orac>presets), they disappear on my computer but still show up on the Organelle. Is there a different folder where I should be managing presets? Or is there some other issue here? Thanks for any help with all this!
not sure overloop is saving recordings, you could edit the module to add the functionality ?! save on the main menu determines which preset will be used at startup. the presets are stored off the user directory, ,something like ~/media/data/presets iirc
This might seem like a ridiculous question, but i've been going round in circles trying to figure this out... How do you stop the demo beat that plays when you start up orac??? It took me ages to even figure out how to download orac, just seems so complicated doing anything with it :/
wonderful video! intuitive ui really! i've been messing about and got a lot of good sounds out of the pi! quick question, tho: how do we get orac to process incoming audio? many questions: does it default to soundcards with inputs, and, with how many channels? i can hear audio-in on my (not pisound) audiocard with a guitar (which is a uca202, with great success), but I don't have enough experience with either pd, organelle, etc. to 'just get how this works'... i've been messing about, but don't know if there are certain patches that accept inputs, and others that don't, or if you need to put a certain setting at the S1 or S2 modules to allow this to happen, or if I need to fiddle with my sound settings in patchbox to get pd using my soundcard properly... I'm sure I'll get it eventually, but someone (not nec. Mark) answering, who's succeeded in processing incoming audio, would save me some fiddling in hdmi/linux audio settings time!
btw, my goal is to get this system working with osc to an oled screen, and i've had some success... after the weekend i'll let others know where to find some useful code for interacting with pi orac, once i've had a chance to take a closer look at the pd patches
so by default the routers (in S1) mutes the audio input on all chains to avoid 'noise' when audio inputs are not in use. all you need to do is go to S1, switch page to (e.g.) Chain 1 Gain , set IN L & R Gain to 100%.then put an FX, say r_reverb into a1 (chain 1) , and check that it works. hardware: it defaults to sound card you have specified - but thats a patchbox thing, not sure if it allows you to specify different soundcard for input and output. its 2 channels if you want more this is simple - copy one of the router modules, and add more input channel... this was discussed a bit on the Blokas forum already.
@@brkruse cool, are you basing this off the osc display protocol (i.e. how it works with the pd/lemur stuff?) good luck, I think this will be an interesting addition for many that are into diy.
@@TheTechnobear i'm a long time listener, first time caller... i actually tried to build up a debian build from your github to port (I'm guessing) organelle_ui to debian (from arch), for organelle's mother C program. I am actually a teacher in China of critical thinking courses (sometimes that's audio design stuff), and it is near impssible to get organelle here. and, to boot, i came late to the organelle party... but I was very interested when I found out about organelle and followed your substantial progress in developing the open source elements (though I was not as successful to get a fully working (headless) pi build of organelle for my students). I am, now, of course curious to see how much is working on patchbox (again, pisound is likely made here but impossible to find in China, so i've sttled for the available behringer unit). It is funny that all of these toys are built in China, but we can't buy them without import tax and headaches. My only goal was to make a shareable way for my students to write and connect to pd/organelle community, and some of them have shared patches written using the desktop patch. My goal has always been to get this working on a pi and to be able to teach open-source sharing to the advanced students in my classes, who will go on to do bigger projects, I'm sure. I should ask you: how relevant are the osc messages in organelle to orac on patchbox? I think we can now have a headless system for our student orchestra if everything is sending. Thank you for your work!
@@brkruse so Orac started off, because when I got the Organelle and started writing patches, I realised I was spending more time writing and debugging the 'UI' , than I was writing the DSP code, furthermore - the UI code was specific to the Organelle, but I wanted to be able to be able to develop it on my Mac (esp. the dsp code) so it seemed natural for me, to abstract the UI , as 90% of the time, we just wanted 'parameters' for the DSP code... e.g. wet dry amount, osc transpose, osc waveform. once that was done, I knew I would then be able implement different UIs, and also expose them over a network via OSC. the point is, if I were you, id not try to replicate the Organelle - its the wrong level of abstraction, you're better off taking the orac modules and parameters and then you can use this on a rPI, desktop or whatever.... this is how I work, most of the work I do on Orac, is done on my mac with a Push 2 controller as the UI, but I know whatever i do there, will then also work on the Organelle (and its display), or a rPI with the PD/Lemur osc display - because the UI is abstracted. rPI - yeah, there is no need for a PiSound, you can use any audio interface - and there are quite a few PI 'hats' available too... I recommend the PiSound because I have one, so i know it and am really happy with it.... but use whatever you can get your hands on :) Orac is about people using what they have , rather than buying other expensive gear .
It’s the same as any other organelle patch .. copy file to usb stick or sdcard ( via wifi) to patches directory , then refresh menu ( or restart organelle) and click on ‘install Orac’. This is what you should be doing with all zip/zop files on the organelle
@@TheTechnobear Thanks. your statement mentioning that the installation process would not be covered in this video but in a separate one (that you provided no links to) gives the impression that much more is involved. Hence my question. Glad to hear it is so simple.
have been trying to figure out how to install ORAC on my organelle2 for months... can anyone point me in the right direction?? I can't seem to find a simple installation guide anywhere. At this point I would be willing to pay someone for some clarity so I can finally use this instrument in the way that I hoped to when I bought it. Thank you!
@@wolvesandguitars How I did it: the manual has a very good section about loading patches onto your organelle by wifi, start by reading that. Then download the orac2.0 patch from Patchstorage, you'll get a .zop file, which your computer doesn't like, but that's okay. you upload the .zop file into the organelle like the manual explained, then on your organelle, go to storage -> reload, and you'll see 'install orac2.0' as one of the options, press it and it should work after!
Is there a way to "midi unlearn"? For example, I mapped knob 1 to parameter 1, but now I want to map knob 1 to parameter 2 instead. I have tried going throgh the process again, but I end up mapping knob 1 to parameters 1 AND 2 :(
@@TheTechnobear in my example, the midi control would be the knob, right? BTW, is youtube comments the best place for me to ask questions about orac? Or is there a better channel/platform?
a sound source for what? not sure I understand? Orac can pass thru audio, and/or it can pass input audio into FX modules, or synth modules, so there are sampling modules that will record that incoming audio, so you can play it back (keys/sequencer) ... and yes you can create your own modules, that take the LR as input - and then your pure data code does whatever it wants.
I assume you are using the rPI? the GUI you see, is the 'remote interface' which you run on your desktop. the idea is that you can configure Orac remotely and save presets, and setup midi learn for control. then you can use the rPI without a screen, just treating orac as an instrument, rather than as a computer :) (sorry I didn't cover the installation/setup of the remote client, I thought it was relatively straightforward, but it has led to some confusion)
TheTechnobear thx. So I am connected remotely. When I Vnc into the computer , I just get the desktop, but I would like to get the pd GUI so that I can run the midi learn, but nothing is showing. I am hearing the sound
@@TheTechnobear Not straightforward at all. Is this puredata? Installed on the rPi or on the remote computer? How do you connect over the network? None of this is obvious or easily discoverable...
BoxOfSnoo this is the pure data patch from orac remote clients Generally I install it on a desktop computer, but you could install on the rPI if you prefer. Once install you just need to make sure the host address at bottom of patch is pointing to the rPI running orac. Note: you can use IP address if hostname is not working on your network. ( above assumes you already have rPI connecting to your network correctly )
Great this help, it's really useful. I'm enjoying Orac a lot, it has many possibilities. And especially your patches of Mi4pd. Thanks again.
You kick ass man. This is gonna be perfect for my guitar pedal setup. Using a ton of midi pedals (chase bliss) and the program change for the presets is perfect. I was gonna try and make my own patch that did this particular thing but now I don't have to haha.
Ahhh is it not editable via the organelle's gui? Still awesome work regardless. Would be nice though
I guess what I mean is if there is a way to switch module slots to edit I have no idea how to do it haha.
Nvm... I figured it out lol. For anyone who doesn't know, you press the encoder knob and one of the keys at the same time
Thanks for this guide to your wounderful software. I especially appreciated the modulation bus explanation.
Mod bus implementation is class
Is there a way to access this GUI in the full release of ORAC 2.0? I can't seem to find it. My main.pd doesn't display it like this.
Thanks! Awesome stuff man.
Great thanks for a great thing 😊
Hi, how do you get to the empty slots using the Organelle? Thanks
Thank you so much for Orac and for these guides! I'm going through this one while following along and learning the features little by little. I have a couple questions I was hoping to ask about...
1) Is there a way (via presets or another method) to have modules save associated files recorded to them? I tried out the Overloop patch, and it seems to be working, except that if I close Orac (or the Overloop module within Orac) and load it again, the recordings are gone.
2) I'm having a little trouble managing presets. I was able to save a new one on the Organelle, load it later, and also save it as the default preset to load. However, when I access my files on my computer, I don't see that new one (in orac>data>orac>presets). Also, when I delete old presets on my computer (also in orac>data>orac>presets), they disappear on my computer but still show up on the Organelle. Is there a different folder where I should be managing presets? Or is there some other issue here?
Thanks for any help with all this!
not sure overloop is saving recordings, you could edit the module to add the functionality ?!
save on the main menu determines which preset will be used at startup.
the presets are stored off the user directory, ,something like ~/media/data/presets iirc
Mind blown...
This might seem like a ridiculous question, but i've been going round in circles trying to figure this out... How do you stop the demo beat that plays when you start up orac???
It took me ages to even figure out how to download orac, just seems so complicated doing anything with it :/
the main menu 'save' is for saving which preset is used at startup... so load an empty preset, then hit save.
@@TheTechnobear Thank you!
wonderful video! intuitive ui really! i've been messing about and got a lot of good sounds out of the pi! quick question, tho: how do we get orac to process incoming audio? many questions: does it default to soundcards with inputs, and, with how many channels? i can hear audio-in on my (not pisound) audiocard with a guitar (which is a uca202, with great success), but I don't have enough experience with either pd, organelle, etc. to 'just get how this works'... i've been messing about, but don't know if there are certain patches that accept inputs, and others that don't, or if you need to put a certain setting at the S1 or S2 modules to allow this to happen, or if I need to fiddle with my sound settings in patchbox to get pd using my soundcard properly... I'm sure I'll get it eventually, but someone (not nec. Mark) answering, who's succeeded in processing incoming audio, would save me some fiddling in hdmi/linux audio settings time!
btw, my goal is to get this system working with osc to an oled screen, and i've had some success... after the weekend i'll let others know where to find some useful code for interacting with pi orac, once i've had a chance to take a closer look at the pd patches
so by default the routers (in S1) mutes the audio input on all chains to avoid 'noise' when audio inputs are not in use.
all you need to do is go to S1, switch page to (e.g.) Chain 1 Gain , set IN L & R Gain to 100%.then put an FX, say r_reverb into a1 (chain 1) , and check that it works.
hardware: it defaults to sound card you have specified - but thats a patchbox thing, not sure if it allows you to specify different soundcard for input and output.
its 2 channels if you want more this is simple - copy one of the router modules, and add more input channel... this was discussed a bit on the Blokas forum already.
@@brkruse cool, are you basing this off the osc display protocol (i.e. how it works with the pd/lemur stuff?)
good luck, I think this will be an interesting addition for many that are into diy.
@@TheTechnobear i'm a long time listener, first time caller... i actually tried to build up a debian build from your github to port (I'm guessing) organelle_ui to debian (from arch), for organelle's mother C program. I am actually a teacher in China of critical thinking courses (sometimes that's audio design stuff), and it is near impssible to get organelle here. and, to boot, i came late to the organelle party... but I was very interested when I found out about organelle and followed your substantial progress in developing the open source elements (though I was not as successful to get a fully working (headless) pi build of organelle for my students). I am, now, of course curious to see how much is working on patchbox (again, pisound is likely made here but impossible to find in China, so i've sttled for the available behringer unit). It is funny that all of these toys are built in China, but we can't buy them without import tax and headaches. My only goal was to make a shareable way for my students to write and connect to pd/organelle community, and some of them have shared patches written using the desktop patch. My goal has always been to get this working on a pi and to be able to teach open-source sharing to the advanced students in my classes, who will go on to do bigger projects, I'm sure. I should ask you: how relevant are the osc messages in organelle to orac on patchbox? I think we can now have a headless system for our student orchestra if everything is sending. Thank you for your work!
@@brkruse so Orac started off, because when I got the Organelle and started writing patches, I realised I was spending more time writing and debugging the 'UI' , than I was writing the DSP code, furthermore - the UI code was specific to the Organelle, but I wanted to be able to be able to develop it on my Mac (esp. the dsp code)
so it seemed natural for me, to abstract the UI , as 90% of the time, we just wanted 'parameters' for the DSP code... e.g. wet dry amount, osc transpose, osc waveform.
once that was done, I knew I would then be able implement different UIs, and also expose them over a network via OSC.
the point is, if I were you, id not try to replicate the Organelle - its the wrong level of abstraction,
you're better off taking the orac modules and parameters and then you can use this on a rPI, desktop or whatever....
this is how I work, most of the work I do on Orac, is done on my mac with a Push 2 controller as the UI,
but I know whatever i do there, will then also work on the Organelle (and its display), or a rPI with the PD/Lemur osc display - because the UI is abstracted.
rPI - yeah, there is no need for a PiSound, you can use any audio interface - and there are quite a few PI 'hats' available too... I recommend the PiSound because I have one, so i know it and am really happy with it.... but use whatever you can get your hands on :)
Orac is about people using what they have , rather than buying other expensive gear .
I am unable to locate any videos on your channel explaining exactly how to install ORAC on an Organelle, can you please provide a link to such?
It’s the same as any other organelle patch .. copy file to usb stick or sdcard ( via wifi) to patches directory , then refresh menu ( or restart organelle) and click on ‘install Orac’.
This is what you should be doing with all zip/zop files on the organelle
@@TheTechnobear Thanks. your statement mentioning that the installation process would not be covered in this video but in a separate one (that you provided no links to) gives the impression that much more is involved. Hence my question. Glad to hear it is so simple.
have been trying to figure out how to install ORAC on my organelle2 for months... can anyone point me in the right direction?? I can't seem to find a simple installation guide anywhere. At this point I would be willing to pay someone for some clarity so I can finally use this instrument in the way that I hoped to when I bought it. Thank you!
any luck ? im spinning in circles.
@@wolvesandguitars How I did it: the manual has a very good section about loading patches onto your organelle by wifi, start by reading that. Then download the orac2.0 patch from Patchstorage, you'll get a .zop file, which your computer doesn't like, but that's okay. you upload the .zop file into the organelle like the manual explained, then on your organelle, go to storage -> reload, and you'll see 'install orac2.0' as one of the options, press it and it should work after!
Is there a way to "midi unlearn"? For example, I mapped knob 1 to parameter 1, but now I want to map knob 1 to parameter 2 instead. I have tried going throgh the process again, but I end up mapping knob 1 to parameters 1 AND 2 :(
Unlearn - Activate midi learn then turn midi control to zero
@@TheTechnobear You mean moving the bar in the gui? Or the knob?
@@Alberaan the midi control ( not UI)
@@TheTechnobear in my example, the midi control would be the knob, right? BTW, is youtube comments the best place for me to ask questions about orac? Or is there a better channel/platform?
could one create a module that was solely using the l r input as a sound source?
a sound source for what? not sure I understand?
Orac can pass thru audio, and/or it can pass input audio into FX modules,
or synth modules, so there are sampling modules that will record that incoming audio, so you can play it back (keys/sequencer)
... and yes you can create your own modules, that take the LR as input - and then your pure data code does whatever it wants.
Stupid question here. I installed and the sound turns on, but I don’t see the GUI u have on the screen. How do u get that?
I assume you are using the rPI?
the GUI you see, is the 'remote interface' which you run on your desktop.
the idea is that you can configure Orac remotely and save presets, and setup midi learn for control.
then you can use the rPI without a screen, just treating orac as an instrument, rather than as a computer :)
(sorry I didn't cover the installation/setup of the remote client, I thought it was relatively straightforward, but it has led to some confusion)
TheTechnobear thx. So I am connected remotely. When I Vnc into the computer , I just get the desktop, but I would like to get the pd GUI so that I can run the midi learn, but nothing is showing. I am hearing the sound
@@TheTechnobear Nevermind I got it. This is amazing! Thx
@@TheTechnobear Not straightforward at all. Is this puredata? Installed on the rPi or on the remote computer? How do you connect over the network? None of this is obvious or easily discoverable...
BoxOfSnoo this is the pure data patch from orac remote clients
Generally I install it on a desktop computer, but you could install on the rPI if you prefer.
Once install you just need to make sure the host address at bottom of patch is pointing to the rPI running orac.
Note: you can use IP address if hostname is not working on your network.
( above assumes you already have rPI connecting to your network correctly )