hey thanks for your response! I was actually just trying to get your ppa going but theres no distribution template for raspbian/Jessie?

I suppose I should upgrade to Stretch?

“bionic” dist works great with stretch, but i haven’t tested it with jessie.

I have tried following the instructions very carefully and looked around the internet for help but I cannot get this done.

After I add the repository to my sources.list and run the keyserver command then when I try update I get:

The repository ‘http:/ppa.launchpad.net/artfwo/monome/ubuntu bionic release’ does not have a release file.
Updating from such a repository can’t be done securely and is therefore disabled by default.

I can see the signing key there on your page but I don’t know what to do with it!

That should be ‘http:/ppa.launchpad.net/artfwo/monome/ubuntu bionic main’, have you copied the command to add repository exactly as it’s typed in the docs?

Ah, it did say main but there was another typo (an extra ‘/’). Thanks for the tip!

from here

I run ./waf successfully in /libmonome, but when I run ./waf configure in /serialosc, it throws an error:

Checking for libmonome : not found
The configuration failed

there is a config.log file, but I am not sure which bits are relevant to this discussion.

this is on a RPi 2 with Raspbian Stretch Lite.

ideas?

edit: this issue could be related to gcc-multilib? when I try to apt-get install gcc-multilib, it tells me:

E: Package 'gcc-multilib' has no installation candidate

You could ls /usr/lib to check if libmonome is installed there properly. (that’s where it is on my pi 3)

1 Like

doesn’t look like libmonome is in /usr/lib. :confused:

try ./waf configure and re-compiling libmonome again?

Oh you could also try

sudo apt install libmonome-dev

Maybe this is a new package since that article was written

recompiles successfully, but doesn’t create a folder in /usr/lib :confused:

returns E: Unable to locate package libmonome-dev

edit:

… I think the waf compiler is looking for monome.h but I’m not sure where it is looking :mag_right:

i’m just manually copying it to random directories and recompiling at this point

edit edit:

ok I just found this page - gonna give this a go

So yeah - I realized the apt get libmonome is dependent on this first:

curl https://keybase.io/artfwo/pgp_keys.asc | sudo apt-key add -
echo "deb https://package.monome.org/ stretch main" | sudo tee /etc/apt/sources.list.d/norns.list

sudo apt install libmonome-dev

which is similar to that new link you posted

for the purpose of this topic i’d recommend to use the PPA linked from https://monome.org/docs/raspbian/ because the norns repository doesn’t have serialosc binaries.

2 Likes

hey there, been a while :slight_smile:

i wanted to hook up my monome to one of my rpis and realized that the only official version of serialosc that i could find is for the outdated pd extended. before i go thru the trouble of rebuilding serialosc for vanilla i wonder if anyone did that and care to share? im on buster / pd 0.50

<3

You want libmonome on rpi rather than serialosc I think… (darn can’t remember what’s involved here now)

pd vanilla now includes osc encoding and decoding out of the box, so you should be able to do this without any special externals (I assume the serialosc you refer to here is some kind of external?).

no, its just built around mrpeach externals, i guess its not such a big deal to change it tho, ill have a look into the libmonome

if i recall correctly, on Linux libmonome handles the OS level (USB) communication with a Grid or Arc. At which point you should be able to get the OSC messages inside pd.

I’ll have to double check this against some hardware later to make sure I’m not mis-remembering. :slight_smile:

this did the job (and can be updated to be confirmed working with buster btw)
https://monome.org/docs/raspbian/

2 Likes

Can you confirm - did the deb package work for you or did you compile from source (for Buster)?

@tehn - what’s the best way to autolaunch serialoscd for use with pd?