Hello List,
1- Doing Pd 0.54-1 compilation under RPi OS 11 Bullseye 32-bit on an RPi 400 was okay: pd 0.54.1 is now configured Platform: Linux Float size: default Debug build: no Universal build: no Localizations: yes Source directory: . Installation prefix: /usr/local
Compiler: gcc CPPFLAGS: -DNDEBUG CFLAGS: -ffast-math -fno-finite-math-only -funroll-loops -fomit-frame-pointer -O3 -g -O2 LDFLAGS: INCLUDES: LIBS: -lpthread -ldl
External extension: pd_linux External CFLAGS: -fPIC External LDFLAGS: -Wl,--export-dynamic -fPIC Deken identifier: linux-arm64
fftw: no wish(tcl/tk): wish watchdog: yes audio APIs: PortAudio JACK ALSA OSS midi APIs: ALSA OSS libpd: no
2- I installed yesterday the new Raspberry Pi OS 12 Bookworm 64-bit, with PipeWire set by default, on my Rapsberry Pi 400. Trying to compile Pd 0.54-1 is not okay with ALSA gone for both AUDIO & MIDI: pd 0.54.1 is now configured Platform: Linux Float size: default Debug build: no Universal build: no Localizations: no Source directory: . Installation prefix: /usr/local
Compiler: gcc CPPFLAGS: -DNDEBUG CFLAGS: -ffast-math -fno-finite-math-only -funroll-loops -fomit-frame-pointer -O3 -g -O2 LDFLAGS: INCLUDES: LIBS:
External extension: pd_linux External CFLAGS: -fPIC External LDFLAGS: -Wl,--export-dynamic -fPIC Deken identifier: linux-arm64
fftw: no wish(tcl/tk): wish watchdog: yes audio APIs: PortAudio JACK OSS midi APIs: OSS libpd: no
And at the 'make' step of the compilation I get: portaudio/src/hostapi/alsa/pa_linux_alsa.c:52:10: fatal error: alsa/asoundlib.h: Aucun fichier ou dossier de ce type 52 | #include <alsa/asoundlib.h> | ^~~~~~~~~~~~~~~~~~ compilation terminated. make[2]: *** [Makefile:746 : portaudio/src/hostapi/alsa/pa_linux_alsa.o] Erreur 1 make[2] : on quitte le répertoire « /home/joe/Desktop/Pd/pd-0.54-1/portaudio » make[1]: *** [Makefile:539 : all-recursive] Erreur 1 make[1] : on quitte le répertoire « /home/joe/Desktop/Pd/pd-0.54-1 » make: *** [Makefile:442 : all] Erreur 2
Q: How can we fix that for using Pd with PipeWire (an upcoming standard) under the latest RPi OS? Note1: I know we can step back from PipeWire to PulseAudio in Raspi-Config => 6 Advanced Options => A7 Audio Config (choice between PulseAudio and PipeWire-default). Note2: Pd 0.53-1 (puredata-0.53.1+ds-2) from the RPi OS 12 64-bit repos doesn't have these ALSA issues (true for both Audio & Midi) even with PipeWire active.
Thanks, Joseph Gastelais
Am 7. Dezember 2023 02:17:28 MEZ schrieb Linux Rouen Normandie linux.rouen@free.fr:
Hello List,
2- I installed yesterday the new Raspberry Pi OS 12 Bookworm 64-bit, with PipeWire set by default, on my Rapsberry Pi 400. Trying to compile Pd 0.54-1 is not okay with ALSA gone for both AUDIO & MIDI:
You must install the libasound-dev package. In theory you can compile Pd without ALSA altogether, but I don't think anyone ever does that, so it's bound to fail every now and again (in your case, you would also have to disable (local) portaudio)
Q: How can we fix that for using Pd with PipeWire (an upcoming standard) under the latest RPi OS?
There's nothing that needs to be fixing. PipeWire has front-end for ALSA and JACK, so Pd can connect to PW right away (you probably need to install some glue package first, cannot check as I'm currently afk). As a matter of fact, on my desktop machines I practically always run both Debian packaged Pd and self compiled Pds on PipeWire-enabled machines (not RPis though) without any problems.
IIRC, PipeWire actively discourages people from writing "native" support for it, and instead tells people to keep using whatever audio backends they already have.
Note1: I know we can step back from PipeWire to PulseAudio in Raspi-Config => 6 Advanced Options => A7 Audio Config (choice between PulseAudio and PipeWire-default). Note2: Pd 0.53-1 (puredata-0.53.1+ds-2) from the RPi OS 12 64-bit repos doesn't have these ALSA issues (true for both Audio & Midi) even with PipeWire active.
Thanks, Joseph Gastelais
mfg.sfg.jfd IOhannes
Thank you IOhannes,
I have missed this libasound2-dev-1.2.8-1 package among some others which were also missing like autotools-dev-20220109.11, libjack-jackd2-dev-1.9.21 and few others. Now Pd 0.54-1 is well compiling with ALSA and the installation went smoothly. 😎
I can move forward and try building the Cyclone 0.8-0 et Else 1.0-0 rc-10 externals for RPi OS 12 64-bits and few others which are not available at all thru Deken.
Q: With Pd 0.53-1 from the RPi repo I got in Deken, Default architecture: Linux-arm64-32. Now after installing 0.54-1 over it I'm getting in Deken, Default architecture: Linux-armv8-32. I'm a little bit confused. Is Linux-armv8-32 = Linux-arm64-32? In Pd Deken 0.9.14 which is the correct architecture for RPi OS 12 Bookworm in 64-bit (running on an RPi 400)?
Joseph
Le 07/12/2023 à 07:45, IOhannes m zmölnig a écrit :
Am 7. Dezember 2023 02:17:28 MEZ schrieb Linux Rouen Normandie linux.rouen@free.fr:
Hello List,
2- I installed yesterday the new Raspberry Pi OS 12 Bookworm 64-bit, with PipeWire set by default, on my Rapsberry Pi 400. Trying to compile Pd 0.54-1 is not okay with ALSA gone for both AUDIO & MIDI:
You must install the libasound-dev package. In theory you can compile Pd without ALSA altogether, but I don't think anyone ever does that, so it's bound to fail every now and again (in your case, you would also have to disable (local) portaudio)
Q: How can we fix that for using Pd with PipeWire (an upcoming standard) under the latest RPi OS?
There's nothing that needs to be fixing. PipeWire has front-end for ALSA and JACK, so Pd can connect to PW right away (you probably need to install some glue package first, cannot check as I'm currently afk). As a matter of fact, on my desktop machines I practically always run both Debian packaged Pd and self compiled Pds on PipeWire-enabled machines (not RPis though) without any problems.
IIRC, PipeWire actively discourages people from writing "native" support for it, and instead tells people to keep using whatever audio backends they already have.
Note1: I know we can step back from PipeWire to PulseAudio in Raspi-Config => 6 Advanced Options => A7 Audio Config (choice between PulseAudio and PipeWire-default). Note2: Pd 0.53-1 (puredata-0.53.1+ds-2) from the RPi OS 12 64-bit repos doesn't have these ALSA issues (true for both Audio & Midi) even with PipeWire active.
Thanks, Joseph Gastelais
mfg.sfg.jfd IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Am 8. Dezember 2023 18:25:31 MEZ schrieb Linux Rouen Normandie linux.rouen@free.fr:
Q: With Pd 0.53-1 from the RPi repo I got in Deken, Default architecture: Linux-arm64-32. Now after installing 0.54-1 over it I'm getting in Deken, Default architecture: Linux-armv8-32. I'm a little bit confused. Is Linux-armv8-32 = Linux-arm64-32? In Pd Deken 0.9.14 which is the correct architecture for RPi OS 12 Bookworm in 64-bit (running on an RPi 400)?
The correct one is "Linux-arm64-32".
armv8 is *not* the same as arm64 (technically, the armv8 can run on both 32bit and 64bit mode, so the "arm64" specifier is used for 64bit).
There is a "--with-deken-cpu" configure flag (or somesuch... I'm currently afk) that allows you to override the specifier (and which is used by the Debian packages).
mfg.sfg.jfd IOhannes
Am 8. Dezember 2023 20:02:53 MEZ schrieb "IOhannes m zmölnig" zmoelnig@iem.at:
The correct one is "Linux-arm64-32".
So obviously there is an issue with the autodetection. Could you please open a bug report on https://bugs.puredata.info ?
There is a "--with-deken-cpu" configure flag (or somesuch... I'm currently afk) that allows you to override the specifier (and which is used by the Debian packages).
Sidenote: Debian sets the CPU specifier explicitly because it also supports weird CPUs (like s390x), which are of no practical importance to the Pd universe, but we want them to have consistent extensions nevertheless). That is too say, the Debian packages do not do anything fancy just to get the amd64 extensions correct (but they get it right as a side effect of something else).
mfg.sfg.jfd IOhannes
Am 8. Dezember 2023 20:08:29 MEZ schrieb "IOhannes m zmölnig" zmoelnig@iem.at:
Am 8. Dezember 2023 20:02:53 MEZ schrieb "IOhannes m zmölnig" zmoelnig@iem.at:
The correct one is "Linux-arm64-32".
So obviously there is an issue with the autodetection. Could you please open a bug report on https://bugs.puredata.info ?
There is a "--with-deken-cpu" configure flag (or somesuch... I'm currently afk) that allows you to override the specifier (and which is used by the Debian packages).
Sidenote: Debian sets the CPU specifier explicitly because it also supports weird CPUs (like s390x), which are of no practical importance to the Pd universe, but we want them to have consistent extensions nevertheless). That is too say, the Debian packages do not do anything fancy just to get the amd64 extensions
that should of course read "*arm64* extensions".
mfg.sfg.jfd IOhannes
-
IOhannes m zmölnig -
Linux Rouen Normandie