Done! Very thorough explanation, thanks!
Now I’m stuck here. I’ll have to watch and rewatch all other videos I guess 
3 Likes
Hey Mark thanks so much for doing this.
I’ve gone through your setup video - everything should be kosher but i’m guessing the hostname needs to be changed in the PD patch.
I’ve tried “patch” and “patchbox” and that isn’t working so what could it be?
cheers
Lloyd
1 Like
You can use the IP address of the Raspberry Pi. See: Raspberry Pi: Find Raspberry Pi's IP Address
1 Like
Thanks Giedrius.
I found the IP address via my router however it’s still not connecting.
Might try again in the morning 
Yup I think I’m stuck at the same point. I’ve put the raspi’s IP in the Lemur client but nothing happens. Maybe I have to enter a port number? It currently says 0. No idea. Sorry for being a complete newbie. 
To be able to connect, MEC has to be running. It’s off on startup.
If using Pisound, click the button once.
If not using Pisound, run sudo systemctl start mec
To check the currrent status, run:
sudo systemctl status mec
1 Like
Mark, thank you for this! I’m playing a bit with it and it’s fantastic.
Really a milestone of open source audio software.
2 Likes
Hi @thetechnobear, I followed the video but I get an error when I try to connect my Push 2 to pisound/orac.
sudo systemctl status mec
mec-app[2835]: MecApi_Impl::init
Apr 11 16:57:23 patchbox mec-app[2835]: oscdisplay initialise
Apr 11 16:57:23 patchbox mec-app[2835]: listening for clients on 6100
Apr 11 16:57:23 patchbox mec-app[2835]: KontrolDevice initialise
Apr 11 16:57:23 patchbox mec-app[2835]: KontrolDevice::init
Apr 11 16:57:23 patchbox mec-app[2835]: kontrol device : listening on 6000
Apr 11 16:57:23 patchbox mec-app[2835]: KontrolDevice::init - complete
Apr 11 16:57:23 patchbox mec-app[2835]: KontrolDevice::new client 127.0.0.1 : 6001 KA = 5
Apr 11 17:07:03 patchbox pulseaudio[1471]: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
Apr 11 17:07:03 patchbox pulseaudio[1471]: [pulseaudio] module.c: Failed to load module “module-alsa-card” (argument: "device_id=“2” name=“usb-Ableton_AG_Ableton_Push_2-01” card_name=“alsa_card.usb-Ableton_AG_Ableton_Push_2-01” namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties=“module-udev-detect.discovered=1"”): initialization failed.
I’ve tried hotplugging it and stopping the service and restarting it.
Any tips?
It seems the Pulse Audio backend may be interferring with Push. Try disabling pulseaudio backend:
echo "autospawn=no" >> ~/.config/pulse/client.conf
pulseaudio -k
and retry starting MEC. Show us the new output of the systemctl status.
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!