Hello all,
I just discovered Pisound and Modep last night and am EXTREMELY excited to get into it. I was just about to order a Pi 4 when I saw they just released news of the Pi 5. Curious to see if the Pisound hat will be compatible with Pi 5 and if not, what peoples plans are for a work around. Cheers!
2 Likes
Welcome to the Blokas community!
Just my $.02. Get a Pi4 with 8 GB of memory. It may be challenging to get a Pi5 at the moment and the Pi4 will handle Modep just fine.
Chances are, Pisound will work with Raspberry Pi 5 as well, it should be backwards compatible with existing hardware, we’ve ordered some RPi 5 boards and we’ll verify compatibility once received. 
4 Likes
Can’t wait to hear the results. Thankyou!
I tried it, and i got this message (maybe some Problem with 64bit?!):
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1271 100 1271 0 0 5940 0 --:–:-- --:–:-- --:–:-- 5967
Importing Blokas GPG public key…
Adding Blokas apt repository…
Updating package list…
…
Reading package lists… Done
N: Skipping acquire of configured file ‘main/binary-arm64/Packages’ as repository ‘apt.blokas.io rpi InRelease’ doesn’t support architecture ‘arm64’
Installing Pisound software…
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
pisound : Depends: pisound-btn (>= 1.13-1) but it is not installable
Depends: pisound-ctl (>= 1.03-1) but it is not installable
Depends: blokas-telemetry (>= 1.0.0-1) but it is not installable
E: Unable to correct problems, you have held broken packages.
Yes, there’s no arm64 deb packages yet.
Fortunately, they are not strictly necessary for audio and MIDI input & output, it’s for The Button and Pisound App.
Please check and provide the output of the commands listed here: https://blokas.io/pisound/docs/software/#verifying-it-works
Have you received your Pi 5 and tested it yet? I just received my Pisound w/case and am very excited about putting it to use!
1 Like
We haven’t received our Pi 5s yet. If anyone already has a Pi 5, it would be great if you could post the results of the commands listed at https://blokas.io/pisound/docs/software/#verifying-it-works.
The full command line output for
curl https://blokas.io/pisound/install.sh | sh on the Pi5 on Raspberry Pi OS Bookworm (it doesn’t run on Bullseye) is:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1271 100 1271 0 0 9377 0 --:--:-- --:--:-- --:--:-- 9414
Importing Blokas GPG public key...
Adding Blokas apt repository...
Updating package list...
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
Get:3 http://archive.raspberrypi.com/debian bookworm InRelease [23.6 kB]
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
Get:5 http://apt.blokas.io rpi InRelease [3921 B]
Get:6 http://archive.raspberrypi.com/debian bookworm/main armhf Packages [346 kB]
Get:7 http://apt.blokas.io rpi/main armhf Packages [56.6 kB]
Get:8 http://archive.raspberrypi.com/debian bookworm/main arm64 Packages [338 kB]
Fetched 769 kB in 1s (1057 kB/s)
Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'http://blokas.io/apt rpi InRelease' doesn't support architecture 'arm64'
Installing Pisound software...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
pisound : Depends: pisound-btn (>= 1.13-1) but it is not installable
Depends: pisound-ctl (>= 1.03-1) but it is not installable
Depends: blokas-telemetry (>= 1.0.0-1) but it is not installable
E: Unable to correct problems, you have held broken packages.
Updating /usr/local/pisound...
sh: 1: cd: can't cd to /usr/local/pisound
Now you may run 'sudo pisound-config' to customize your installation!
It’s expected, see my reply above: Pisound for Raspberry Pi 5? - #6 by Giedrius
I see, thanks. It installs on with bookworm 32-bit here, but I can’t see the pisound interface. I tried to run RNBO with the pisound, and I can’t say if it’s related to that or not. But I noticed that the button doesn’t work either…
output of the mentioned commands:
amidi -l
Dir Device Name
arecord -l
**** List of CAPTURE Hardware Devices ****
card 2: Dummy [Dummy], device 0: Dummy PCM [Dummy PCM]
Subdevices: 7/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Dummy [Dummy], device 0: Dummy PCM [Dummy PCM]
Subdevices: 7/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
Finally we received our Pi 5 shipment.
There’s an issue in the kernel that prevents Pisound from working right away on Pi 5, but we’ll work with RPi Foundation to sort the situation out. Sometimes new releases are just shaky at the beginning, no worries.
1 Like
Ok, here’s a proper temporary workaround, add exactly this at the top of your /boot/config.txt:
dtoverlay=
dtoverlay=pisound
1 Like
Thanks a lot. I Shows up now. Next step will be to get it to play nicely with RNBO. But that’s for the other forum
There’s a fix in the Raspberry Pi’s kernel tree that will make Pisound work on Raspberry Pi 5 right away, we now have to wait until the next stable update of the kernel gets released.
Great news. Thanks A lot!
Hey!
This makes pisound show up when I use aplay -l, but I’m still having trouble with jack…
I keep getting the following error:
JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
I’ve already tried updating the kernel as suggested earlier, using the new hat_map.dtb overlay, and updating both JACK (to version 1.9.21) and ALSA, but no luck 
edit: Thought it might help to know, JACK works as expected with a USB Audio Interface, so I don’t suspect the problem is JACK…
edit 2: I’m able to get pisound to work with jackd when I use either the -P or -C flags with jackd but NOT BOTH… Have tested functionality, it seems to work as expected when set on either settings, still struggling to figure out why duplex is failing
1 Like
Thank you for the information, I can reproduce the problem, we’ll investigate.
2 Likes
There’s a fix for this in RPi kernel, until it’s officially released, temporarily you may use this command to get it:
sudo rpi-update pulls/5757
3 Likes
Pisound should work fine now with Raspberry Pi kernel versions 6.1.64 and greater. Until a new version of raspberrypi-kernel package gets released (which is not done often), you may use this command to get the kernel updated:
sudo rpi-update
2 Likes