pulseaudio -k
E: [pulseaudio] main.c: Failed to kill daemon: No such process
1 Like
I haven’t still installed Orac, but yesterday I tried to use MODEP with touchOSC and it works only connecting the iPad directly to MODEP WiFi LAN
1 Like
this happens when the osc address is not correct.
note: you need to reload the lemur project for it to pickup the new address !!
(this catches everyone out!)
the network name is
patchbox.
note: the full stop after patchbox, it won’t work without it.
(that or as @Giedrius pointed out you can use the ip address)
lemur template already has the port, its 6100.
(its just its defaulted to organelle as a hostname)
@Taubaland , odd , my push2 was ok a couple of days ago when I tried… (I’ll check it again)
@Makrotulpa, yes hostname needs changing in the msg box , where indicated.
(patchbox. works for me)
… make sure you have mec running
single click of button, and the leds will flash once to show its activated.
1 Like
2 Likes
Woohoo!
Thanks for all the good work, @thetechnobear! Nice rollout too!
Sorry for all my nagging over the past couple of years. I never meant to be a burden and I didn’t necessarily feel entitled to get answers. But I’ve been waiting for pretty much this.
The RasPi video gets me pretty excited. Wasn’t really clear on how easy it’d be to install and run. Also wasn’t so clear what kind of functionalities ORAC itself had. The softsynth sounds pretty good! Will be quite useful with my wind controller. And maybe even with MPE? That’d be just plain great!
So, the version of MEC included should work with my Eigenharp Pico? If so, that’d be just plain awesome.
What’s funny is that I’m on vacation, away from my main musicking setup. Thought about bringing one of my Pisound-HATted Pis, but ended up not doing so, for a variety of reasons. They say absence makes the heart grow fonder. I’ll be quite fond of my Patchbox Pisound by next Wednesday! 
Again, Mark, thanks for all the good work!
2 Likes
nothing wrong…
this is why i’m going to do a getting started video - as I realised Ive not really explained how to setup a rack 
and by default its completely empty
(ok,not quite empty, if you go thru the modules (top arrows), you’ll see that actually the router module, and clock module are present…)
anyway, super quick
whilst on module a1, in the bottom panel, where its say a1:empty ,
select it (big arrow pointing right) - then the module list will come up…
you’ll want a synth, so go to the top, to get out of the ‘utility’ category, and then go to synth category, and grab a synth.
then if you plug in a midi controller, and press some keys, it should make a noise 
loopop did a good overview video of this for orac 1.0 on the organelle, but the principles of module slots is the same - so perhaps worth checking that out.
(he explains, modules, module slots and chains - and you’ll see the lemur interface looks quite similar to the organelle really)
after that my overview of 2.0 will probably make a bit more sense.
but as I say, probably at the weekend, I’ll film a getting started video, which’ll focus on how to build a rack on the remote interface.
3 Likes
Oh thanks! I’ve figured it out! It works, and it’s awesome 
2 Likes
@Giedrius @thetechnobear
Still not connecting. This is what I get checking the status of MEC. Any further suggestions?
what are you running the PD client on? windows/macos/Linux?
can you ping patchbox. ? (again note the dot after patchbox)
or ip from that client box?
is this all on one network? your not on a different subnet?
whats the ip of the patchbox reported as? and what is your local machines ip address?
could your router be blocking port 6101?
can you confirm on the patchbox that the IP address it has. check its the same as what your router says it is.
(i think much of this is covered in the post @Giedrius pointed too)
it sounds like you have a more general network issue, as all the PD client does it try to connect to port 6100 on patchbox , which mec has opened (you can see that on the mec logs you posted)
Was running on Windows 10 but tried on the MacMini/Sierra machine and it connected to the IP address - not “patchbox.”
Also pinging “patchbox.” gets an Unknown Host error.
I think one issue may be with my PD install on Windows as i’m getting a bunch of errors in the console. I’ve installed Mr Peach.
OK so some initial thoughts and suggestions based on using PD remote client on OSX.
- the module selector reverts too quickly - seems it reverts after about 1 second of no movement - this makes it a little stressful having to quickly choose a module.
- if I have a synth in a1 and FX in a2 - then go to FX to edit parameters the MIDI notes stop going to the synth. This doesn’t seem like it how it should ideally work.
- I wonder if there is an easier way to reset Modulation - I seem to be constantly accidentally modulating the modulation - nice feature but then it is difficult to unmodulate a parameter
- I’m using a KMI K-Mix connected to the rPi. At the moment it is running the audio out the Master - I presume I will need to edit the patch on the rPi to have it run out different channels. Ideally there would be a module that allows you to select which output you are routing to - not sure how this works on the PD interface.
There’s a world of fun here though - I hope you like lots of feedback!
routeOSC is part of mrpeach, so looks like it’s not installed properly on your windows box.
( that’s all I installed on my Windows 10 box to get it working)
1 Like
-
Yeah it’s a trade off , as you need it to return if you decide to not select a new module.
Once you know the modules it’s doesn’t seem so quick any more
Btw if your moving it’s timer is being reset -
You can change this in the router options under main control see my 2.0 overview video
-
Remove the module being modulated and it will reset, but the targets are not.
Agreed it’s takes a while to get used to remembering to turn mod learn off ; -
You mean you just want to target a different pair of outputs?
I’d so this is easy, just edit mother.pd
I’d you mean you want > 2 outputs then this is a matter of creating a specific router which is very easy to do - the trick here is you will probably want different chains to go to different outputs.
I think one of the strengths of Orac is because all the modules are PD it’s easy for users to create new modules to extend it , and hopefully share with community to help others.
1 Like
-
I’m not sure how this works without the Organelle.
-
So the K-Mix has 4 outputs: Master / Aux1 / Aux2 / Aux3
As you say ideally chain A would go out Aux1, Chain B out Aux 2 etc…
Something like [dac~ 3 4 5 6 7 8]
I’d already have started fiddling with this but I’m not familiar with the Linux filesystem and am not sure where mother.pd or the router modules are located?
look in PD’s Preferences -> Path… if the path library is listed… sometimes, even if you installed the library via deken is possible that you have to add it to list manually
Good call @SYS2064 - it was a subdirectory of the externals path but adding it as a new path got it going!
Cheers!
2 Likes
the same as organelle, now you have it going, you should see that the organelle screen basically is the same as what your seeing.
(except PD shows both the parameters and menu at the same time)
so as detailed in the overview video
you need to go to Router module (s1)
(just click thru modules at top, or use left/right arrow)
then click thru pages to get to Main Ctrl (or use page up/down)
then you will find Dest, change it to 1 , if you want input to to a1 , rather than active module
as with many things in orac, there are many times when the current behaviour is more desirable,
and also different ways to achieve what you want.
e.g. what I tend to do is:
I use midi channel 16 for the ‘active module’ (also on main ctl page on router)
then I turn on midi input on the particular chains.
e.g. I have midi ch1 = chain 1, ch2 = chain 2
so now, from my midi controller I can target the active module from ch16, and chain 1 and 2 with channel 1 and 2 respectively.
Note: the router settings are saved in the preset, so you can change the behaviour depending upon ‘the patch’.
ok, if thats what you want Id not change mother.pd!
you can create your own specialised router.
everything is located in /usr/local/orac
so what you would do is
mkdir -p ~/media/orac/usermodules/router
cp -R /usr/local/orac/modules/router/parallel ~/media/orac/usermodules/router/kmixrouter(warning: I did not actually type this on a pi, so might be a typo, but looks ok 
)
you now have a new router module called kmixrouter, which is identical to the parallel router.
but you can edit it.
~/media/orac/usermodules/router/kmixrouter now contains a module definition and pd file which does all the routing - open module.pd, you’ll see its pretty straightforward, just a bunch of modules, connected - then sending to a final output. (you’ll want to replace the final output with a [dac~])
using this technique you can not only change where the outputs go, but also change the topology eg. create 3 or 4 chains with different outputs.
I spent quite a bit of time for Orac 2.0 simplifying this process, as its a really powerful way for users to tailor it to their environments… whats the beauty of PD, its easy to modify - so in Orac I try to leverage that as much as possible.
3 Likes
ok, next release this will be user configurable, by changing /usr/local/MEC/osckontrol.json
and adding the ‘menu timeout’ option, as shown below
(default will remain the same)
{
"mec" : {
"oscdisplay" : {
"listen port" : 6100,
"menu timeout" : 350
},
"kontrol" : {
"listen port" : 6000
}
},
"mec-app" : {
"outputs" : {
"midi" : {
"virtual" : 0,
"voices" : 15,
"mpe":false,
"pitchbend range" : 48.0,
"device" : "Pure Data:0"
},
"_console" : {
"throttle" : 0
}
}
}
}
3 Likes
Awesome! I’ll have a go at it tomorrow. I presume I could feasibly create a selector for multiple inputs as well?
1 Like
Mark, I’m enjoying orac a lot; some observations/questions:
-
What is the better way to emulate the aux button of the organelle with a normal MIDI controller? I tried with my edirol keyboard by assigning controller 69 to the slider and it sort of works but I feel is not optimal…
-
Tried your suggestion of enabling a different midi channel per chain and it works beautifully for notes but the aux button is not “forwarded” so to say, I suppose it’s a global setting that works only in the selected module?
-
Would it be possible to have the remote control on the pisound app? Or alternatively, how can I use android to remote control orac?
-
Would it make sense to make the remote functions like selecting modules, chains, pages and so on midi controllable? From what I see on the videos on the organelle you have easy navigation with the wooden keyboard and the encoder but on pisound the navigation requires remote control (or I’m missing something?)
I’m looking forward to your getting started video, which I’m sure will be great like the last ones
Thanks for all this and keep up the great work!
4 Likes