Wow, the more I look into Orac, the less I can imagine how much work that must have been…
Here an overview over the currently available modules, parameters and value ranges:
4 Likes
a little something that might interest those wanting to run Orac on a rPI, but ‘unconvinced’ about remote configuration 
https://blokas.io/midiboy/ (hint: look half way down page!)
other news, someone has also coded up a web editor, more info on blokas forum.
3 Likes
Oh boy… might be a fun “assembly” project.
Useful one 
1 Like
Thanks for this, I wonder if I could make a combo of rings and clouds run on Nebulae)
How do I connect Seaboard Block or Linnstrument to Nebulae?
sure , this already works in Orac … you can even run multiple of each. (up to cpu load)
so once you have Orac installed, when you run Orac I connect the first usb midi device to orac, so it should ‘just work’ … if you have multiple midi devices connected at once, then you need to alter pdsettings.
1 Like
I mean where physically on the Nebulae do I plug the usb-cable. I’ve seen you performance video with Madrona Soundplane with Eurorack, but you’ve used bela as converter to CV there.
EDIT: I should probably educate myself and learn everything about setting up Orac, since you kindly posted all of that online, and then come back here with questions)
EDIT 2: So I see I can just plug into the front usb port where the usb-stick with samples usually lives, question answered)
exactly … the usb storage stick is only used to copy samples/new instruments initially, it doesn’t need to be plugged in unless your doing that - I generally don’t have it in the slot.
(the soundplane is different since its not midi, and I also wanted direct CV outputs… though I could get it to work with an ‘internal sound source like orac’ on the nebulae directly if I wanted too )
What’s better than a virtual modular? a hybrid modular
Ive been working on a new set of modules for Orac, called (un-imaginatively) cvtools
more details here:
basically what you’d expect, support for cv clock in/out, note in/out, modulation
its a lot of fun linking up the Organelle to the modular… lots of possibilities.
oh, this also works on the rPI too
its kind of a work in progress… but Im already having a lot of fun with it !
and yup, it supports MPE -> CV
3 Likes
Hi @thetechnobear, I deeply appreciate you willingness to help!
I asked my older questions in this thread prior to installing Orac 2 on my Nebulae, and I tried to install it just a week or so ago.
At this point I’m not looking into MPE yet, just making a simple Rings into Clouds patch would make me happy)
I think the installation itself went okay, since I hear a little drum beat each time I load the Pd patch on the Nebulae. However, installation was almost instant in my case, yet it took some time in your video. Maybe this means something.
But the controller patch on my PC gives me this:
Pd console
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /module
… couldn’t create
routeOSC /page
… couldn’t create
unpackOSC
… couldn’t create
packOSC
… couldn’t create
routeOSC /clearText
… couldn’t create
routeOSC /text
… couldn’t create
routeOSC /selectText
… couldn’t create
LISTEN:: listen 6101
bad host?
SEND:: connect organelle 6100
Other than that I don’t have much info or understanding what’s wrong. I can eject the SD card from Nebulae if there’s something I need there.
Many thanks, Mark!
if you hear a drum beat, sounds like orac is working fine.
looks like you have not installed mr preach
in pure data -> help ->find externals -> mrpeach
you’ll then need to restart PD.
that should clear those errors.
after that, as shown in the video , you need to make sure of a couple of things
a. installed wifi correctly
b. start wifi on nebulae (custom instr as per video)
try to ping it from your desktop to make sure you can contact it - watch out, windows can sometimes be a bit funny with hostname resolution.
so if you’re positive your wifi network name/password is correct… see if you can find the ip address.
c. start MEC (custom instr as per video)
this is the app that’s used to talk to PD on your desktop
(the above are only needed when your setting up orac, when you don’t need the editor … you don’t need wifi/mec etc, hence why its a separate setp)
d. start orac on nebulae
e. start PD app on your desktop
down at the bottom of the patch you will need to edit the hostname (if you found hostname was not working, you can alternatively use ip address) , then press save to save patch…then click connect (or restart patch)
(fyi : in PD ctrl-e takes you in and out of edit mode)
that’s it… really the only step that’s sometimes tricky is wifi, as peoples computer and network setups are different.
I found out both hostname and ip, installed mrpeach, and the log changed a bit:
New log
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /$1Desc
… couldn’t create
routeOSC /$1Value
… couldn’t create
routeOSC /$1Ctrl
… couldn’t create
routeOSC /module
… couldn’t create
routeOSC /page
… couldn’t create
unpackOSC
… couldn’t create
packOSC
… couldn’t create
routeOSC /clearText
… couldn’t create
routeOSC /text
… couldn’t create
routeOSC /selectText
… couldn’t create
LISTEN:: listen 6101
connecting to port 6100
SEND:: connect 192.168.1.70 6100
I guess Orac and Controller Pd patch established a two way connection, but the patch can’t send OSC data?
routeOSC /selectText
… couldn’t createthis means the routeOSC external cannot be found.
routerOSC is part of mrpeach, so id guess for some reasons its not on your PD path
… did you install via deken? (which version of pd are you using?)
Pd version 0.49.0
Yes, I installed mrpeach via deken, and the files are actually in PD externals folder.
yeah, so the you should see listed in
pd->file->paths…
and in that directory is routeOSC.dll
that’s about all there is too it… it picks up externals listed there.
only other thing I could think might be wrong is if you have the wrong architecture, e.g. 32 bit pd , 64 bit mr-peach?
I think ive got 32 bit pd 49.0 on windows 10 installed, but im pretty sure deken (by default) only shows the correct architectures.
Yes, routeOSC.dll is here C:\Users\Fedor\AppData\Roaming\Pd\mrpeach
Funny that running routeOSC-help.pd file clears route osc error messages.
I mean that if I run in first,
then Main.pd, then the log is just:
slipdec: maximum packet length is 65536
import mrpeach
… couldn’t create
LISTEN:: listen 6101
connecting to port 6100
SEND:: connect 192.168.1.70 6100
But again, nothing useful happens)
its probably the wrong architecture then…
ok, so I realised I was using pd 48… so decide to reinstall from scratch on my windows 10 laptop
what id did was …
remove PD 48
remove all folders in AppData\Roaming\Pd\mrpeach
(as I was changing to 64bit from 32bit)
download PD 49-1 64 bit installer
installed PD
ran PD
help->find externals -> mrpeach - install
exit PD
clicked on main.pd in the PD OscDisplay folder
then no errors in console (except bad host?.. as id not edited it to alarmpi. yet, so couldn’t connect)
(I was previously using PD 48.0 32bit)
try deleting the externals folder in the OscDisplay/pd directory… perhaps that has 32bit externals?
mrpeach is described in Deken as Windows-amd64-32
Maybe there is a web editor and touch osc template?
So my solution might be using PD 48.0 32 bit?
I cannot see why its not working for you…
I’m now running pd49-1 64 bit, and its also working fine…
yup that’s what I installed, without issue.
Ive also just redownload the OscRemoteDisplay from patchstorage, to just check its ok,
and its fine BUT I did include the 32bit mrpeach dlls used, which are not appropriate for 64 bit, but PD just said, it could not load them, and then seemed to proceed to use the ones id downloaded via deken. (you can delete the externals folder to get rid of the warning)
you seem to be having an issue with the mrpeach externals but its unclear why,
when it works for me from a fresh install here?!
perhaps redownload from OscRemoteDisplay from patchstorage, if you didn’t download it in last few days.
and delete the deken folder and try again…
(perhaps you had an old install with a different architecture, or another package than includes routeOSC?)
…. this is why I don’t like windows much, its full of these little potholes
theres Lemur and Pd for now…
someone has put together a web editor for the rPI for orac, but currently that involves installing a stack of stuff, which is not easy on the nebulae - my hope is to simplify this, but ive no time for this in next month or two.
1 Like