one thought, perhaps if you have PD 32 bit installed, then the OscRemoteDisplay externals are some how conflicting with the deken version…
(those externals were for PD48 32bit)
this would explain why the help file worked, as this would be in same directory as the deken version ….
so yeah, deleting the external folder is the best direction
OscRemoteDisplay/pd/externals
I suspect that will fix it.
(if it does, I’ll delete them for next release of OscRemoteDisplay … I did it to help windows users… but looks like it will help some, but hinder others!)
Do you have a link for that? Can’t kind anything like “OscRemoteDisplay” either on Patchstorage or google. Or do you mean Orac Remote Control patches?
I installed the latest Pd 64 bit just to use with Orac when I was installing it on Nebulae.
32 bit or 64 bit “problem” on Windows is long gone, everything is 64 bit now.
I unintalled it, reinstalled again, installed mpreach via deken - and no luck, unfortunately.
I think for the future you might consider making a Max app, just to use a more professional and robust platform, at least for the editor. I can give you my 3 month long license serial from Roli if you want)
sorry im mean Orac Remote Control… (ive a different name for it in my projects)
did you remove the externals folder? I think that is your issue.
Ive got a perpetual Max licence
the reason I did it in PD was so that people could use it as a learning tool if they wanted to implement it on (e.g) TouchOSC… PD is free, so they could easily play with the patch
also PD runs on mac, windows, linux
If I did as a Max app, then id have to produce a binary for mac and windows, and Linux users would be out of luck
i’ll admit ive miscalculated the community a bit, id hope some others would pick up this and run a bit with it… but seems only one or two so far have done that, most just want something that works ‘out of the box’
Well I deleted that externals folder, then copied the files from mrpeach folder to OracRemoteClients \pd, where main.pd and others live, and at least I don’t have “couldn’t create” errors now, only LISTEN:: listen 6101
connecting to port 6100
SEND:: connect 192.168.1.70 6100
Seems like Pd controller issue is solved - I vaguely recall it was always an issue with Pd, that externals have to be in the same folder with the Pd patch.
I also can see alarmpi connected to my wi-fi router.
Clicking on any prev / next or cursor buttons still doesn’t do anything, so I guess there’s still no connection.
You said that MEC is what’s required for communication. Unfortunately I forgot the slot number I gave to the mec file. 1 starts wi-fi, so its either 2 or 3. So I don’t know if I’m starting mec or package installer.
But what I’ve noticed is that loading slot 3 lights up the freeze led, and loading slot 2 - doesn’t.
Is there a way to re-install everything on Nebulae’s side?
Also - what [declare -path externals] supposed to do?
a) if you followed my video, then its likely (?) you numbered the same way as i did…
so it will be in slot 1 (aka a)
here is where I go thru it
a) just reinstall in the same way as you previously did - that will work find
in fact all you actually need to do is to copy
mec.instr onto usbstick and rename to a-mec.instr to ensure its in slot #1
(you dont need to do pkg inst, as thats already done… in fact you can delete it now)
c) log into your nebulae with
ssh alarmpi@alarmpi
password alarm
in the home directory you will find a directory called instr
in there you will find mec/pkg instr, the slot depends on the alphabetic order
hence if you did as per the video and rename to a-mec.instr it will be in the first slot.
I know this is all a bit of a faff (remembering slot numbers etc)
but unfortunately thats all that the nebulae provides, and even then Ive gone beyond what it does by default.
perhaps I’ll create a web front end for the package management for nebulae,
but frankly I found the community at muffwiggle a bit ‘off putting’ to development.
the MW thread is dreadful for supply support, as you get abused by people who ‘dont care about 3rd party stuff’, and also its so long … interested users cannot find relevant posts, so I end up say the same things repeatedly …
(oh and there is a huge amount of mis-information on the MW thread!)
so, Ive been waiting for QuBit to provide their promised forum before I step up development on the Nebulae - as then i can provide much better support.
then I could have done a dedicated thread to things like troubleshooting installations, and more details about you can check things on the Nebulae…
Its a pity as personally Ive ‘unlocked’ so many things on the Nebulae, including things like Wifi, usb midi support… and found quite a few opportunities - but I can/will not share these on the ‘toxic’ MW thread, I need a place where we can have focused, creative and positive discussions - like we have on say axoloti and the organelle.
anyway… fingers crossed QuBit sort this out - as I know Andrew is quite keen to get more community involvement.
issues with externals
you should not have needed to copy the externals, just delete them
this is not true.
this adds an additional folder to the search path
(search order is : current directory, paths declared in patch, system paths e.g. which deken updates)
so the issue you had was…
in the last update of the pd client, I supplied a 32bit pd 48 version of routeOSC /packOSC etc, because users were “forgetting” (not reading instructions ) to install my peach via deken.
but some how for you (not for me!) , this was conflicting with the mrpeach version…
what Im going to do is remove these, as obviously this is going to lead to more trouble than its solving!
as mentioned my ‘long term’ plan is to put a web interface on MEC/Orac so that there is nothing to install on the client side!
mec does not start wifi,
wifi is only till next power cycle
I believe the readme explains you how you can make it ‘once and for all’
the reason for this, is by default I don’t want to be leaving anything running on the nebulae for the next boot… because its not necessary, so is a potential overhead.
but if you want to have with mec or wifi started every boot - that’s easy to do .
my view of orac is:
once you have setup Orac as you like, you can just switch to it, and play with it ‘standalone’ , using the knobs on the nebulae, and a usb midi keyboard if you like (you can also switch ‘rack presets’ from the nebulae)
you only need wifi/mec when your editing new rack presets.
so when you want to create or edit and existing rack , then you
start wifi
start mec
start orac
fire up Orac remote client on your desktop/phone…
then do the editing etc, and then save the rack to use ‘standalone’
for sure I know some like to use the edit constantly live,
but personally… I prefer to have orac presets which I then switch between and use standalone
(of course, you have to get over the first step which is to use the editor to setup those presets!)
btw: one word of warning… not sure which version of nebulae firmware your using,
but the last release (not the one on GitHub) had a bug, which means the module will not start after a power cycle IF you last had a user patch running.
I believe this is fixed on their version on GitHub
(not 100% sure, as I fixed it myself on my version of the firmware, so not download this one yet)
Okay, so a little update. I flashed my nebulae’s sd card to the factory state (latest firmware), just to start fresh and repeat every step in the installation instructions video to a tee.
Just like the last time, I’ve noticed that in my case the package installer run almost instantly, few times faster than in your video, @thetechnobear. It didn’t looked like it did anything at all.
And now I have no drum beat and no synth sound from a keyboard)
did you leave the USB stick in whilst running the package installer?
if it cannot mount the usb stick when you run it, it will exit immediately
does orac appear in the user pd section?
also make sure you are using a high quality USB stick,
one thing we see repeatedly on the Organelle, are usb sticks can be really unreliable at times, and you only noticing when you start using it for larger files.
I’m a bit confused… not only have I run it multiple times without issue,
but you also ran it the first time and it installed orac fine, so don’t understand how the results can be different this time?!
I’ll be honest, I’m not really happy with this install process on the Nebulae, even though, its simple - and theoretically should work every time (since Nebulae/OS/install is the same) , it seems users are having difficulties, and when they do its nigh impossible for me to support properly
so, I think, I’m going to develop a different method for package installation,
one that has more feedback for the user, and so also is easier to support.
it will take a different but complimentary approach to the Qubit install mechanism,
and might make some Nebulae users throw their usb sticks away
(sorry, no details yet - as still a few ideas, tests, experiment to do)
unfortunately, I’m busy on another project for the next few weeks… and starting to build up a backlog for after that, but I’ll take a look at it during September.
Wow, looks like a great day for all the eurorackists out there
Could this be used to build a polyphonic synth?
Having played with the ContinuuMini quite some time in the last weeks. My personal takeaway: The step from 1 to 2 voices is probably the most rewarding one, really prefer the duophonic patches most of the time. A lot can be done with just two voices. After playing mono and duophonic for some time it’s sooo nice though to get all the remaining fingers and chords back
Different instruments, different techniques, I (should) know… My curse seems to be that I want to use everything like a piano perhaps
polyphony for sure, terminal tedium is a raspberry PI 3, so quite powerful (cpu/memory)
it’s an interesting area for eurorack, since polyphony with individual voice modules is expensive… but you could generate with this quite easily…
i guess at some point it becomes paraphonic, as you might start putting the output of the TT thru an analog filter module, so the voices then are sharing this.
one area where salt/pepper is better is the TT only has 2 digital and 2 audio outputs, no cv outputs - where as bela has 8 cv outputs. (but TT rPI is more powerful)
but its got a good number of CV input, so still a lot of fun to be had.
