#72

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

#73

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

#74

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
#76

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

#77

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

#78

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?).

#79

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

#80

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:

#81

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

2 Likes
#82

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?

#83

‘best’ probably depends on context/application
systemd service?
login script?
pd launch script?

#84

context would be eventually getting pd running as a norns engine (and thus being sure grid/arc were properly interfacing with pd).

So systemd service perhaps in that case?

#85

deb package worked fine and serialosc is started on boot per default i think

#87

I’m trying to work with a grid and a node.js script on Rasbian Buster but something is not working and it’s difficult to troubleshoot…

I’m on ARMv6, RPI Zero W, Raspbian Buster

Just to be clear, do I need to install libmonome-dev AND serialosc or libmonome-dev is sufficient ?

First, I followed these instructions https://monome.org/docs/serialosc/raspbian/
But I’m getting nothing from my node script, it’s supposed to print the grid keys pressed but… I assume there’s an issue with my serialosc install…

journalctl -u serialosc returns a blank log, that’s weird (same for serialoscd, I never know which one is correct).

When I try to start serialoscd manually (after a systemctl stop serialosc, just to be sure) it returns a “Segmentation fault”.

So I decided to remove the libmonome-dev and serialosc packages and tried to compile from source but I’m getting an error with serialosc this time, the build fails :

heres the output of ./waf -v

Capture d’écran 2020-08-29 à 20.51.39
Capture d’écran 2020-08-29 à 20.51.391576×1356 952 KB

Am I missing something here ? Is this an issue with ARMv6 ?

Thanks :wink:

#88

maybe a gcc version problem?

but wow that error’s not really giving much useful info, is it?

#89

Ha yeah I know :slight_smile: The other part of the script is not throwing any error, this is all I have. I remember using a monome with pd on a rpi3 a few years ago without problem. The only difference here is RPI buster instead of Jessie (?) and the RPI model… I suspect armv6 is the cause… unless someone has successfully used a monome and a pi zero…

#90

You could try doing a test install with Jessie on the PiZero and see if that works? Not ideal, but would narrow down causes.

I would suspect gcc being a much newer (more restrictive) version rather than armv6 off the top of my head.

I have 4.19.66+ armv6l on my pihole pizero I could test here if you like

1 Like
#91

Yes, good idea. I can try that on a new SD card.

Just to be sure, the regular procedure for connecting and working with a grid on a RPI is to install the libmonome-dev package and that’s it ?
Because this package is not mentioned on the Monome docs (“install serialosc on raspbian”). That’s confusing. If so, you then add a script to start serialosc(d?) as a service ?

or
Is it libmonome-dev then the serialosc package ?

Oh and, when serialosc is working , is it supposed to log the ID of the grid in the console when you connect a grid ? At the moment, it’s not obviously but I’m looking for ways to troubleshoot the install… lsusb shows the device connected to the pi but that’s it.

Will try with Jessie tomorrow as you’ve suggested :wink:

#92

noting here for others…

serialosc compile solution is to change the compile flags to not treat warnings as errors…

not sure how to do that with flags in waf so I changed the serialosc/wscript line 257 to conf.env.append_unique("CFLAGS", ["-std=c99", "-Wall", "-Wno-error"])

1 Like
#93

The solution suggested by @okyeron seems to work.

Serialosc will compile after changing line 257 of wscript to not treat warnings as errors.

After a reboot, serialoscd will load without throwing a “segmentation fault” and detects my grid.

I’ve posted an issue with the details here https://github.com/monome/serialosc/issues/53