I have found that you can add a short header extender that makes up the added distance that the cooler takes away. This allows the pisound to fit on the Pi5 perfectly. I had to add some custom standoffs for shoring it up. I don’t use a case so I can’t speak to cases.
I was able to use my Pi4 to update the OS per the post In this thread and then put it back into the Pi5 so it would boot. I was able to run the rest of the OS updates everything seems to work but I can’t seem to get a desktop to show up and I am not sure how to get it to work.
Any help here would be nice.
I have a feeling I will need to wait for the next OS/Kernel update.
Mod works sooo well now and I can’t wait to try and get my other projects working.
So I wanted to give an update on my Pi5 experance thus far. Since upgrading broke things, I put a fresh 64bit PiOS image on the fastest SD card I have and the pisound is showing up and working perfectly out of the box. Amazingly so. This should hold me over till we see a new release of Patchbox.
As always your mileage may very.
Has anyone else tried the little 8.5mm header yet?
The .deb packages that Pisound and most of Patchbox OS rely on have been ported for arm64 architecture, available for bookworm OS release.
The install-pisound.sh and apt-setup.sh scripts have been adjusted accordingly, and will automatically fall back to the previous .deb packages if the OS release is unsupported.
To install the basic Pisound software, run this command:
curl https://blokas.io/pisound/install.sh | sh
To only update the APT packages without installing anything, run this command:
Hi,
Thnx for all the info about pi5 and modep. I have installed it (Pisound - modep) and it works great. Because it is not a full Patchbox OS, there is no config for the Pisound to set sample rate and buffer size. I have found out thee jack settings can be changed in the file jackdrc. But when I set a sample rate of 96000 or 192000 (-r option) and restart the system I have no sound on the Pisound output. So the line in jackrdc is like this:
exec /usr/bin/jackd -t 2000 -R -P 95 -d alsa -d hw:pisound -r 96000 -p 128 -n 2 -X seq -s -S
When I restart jack the server is displaying this error:
Feb 23 10:31:24 raspberrypi5 jackdrc[6663]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
It seems like it is impossible to change the sample rate. I can change the buffer size to 64 to reduce latency. I still would like the discover how the sample rate influences the latency and how far I can take it. On the other hand, I read an article about sample rate, harmonics and distortion/overdrive. and how a high sample rate can influence the sound (higher harmonics generating audible distortion).
Hi Giedrius,
Thnx, tried -r 96000, -p 256 and -n 3 and that worked until modep starts up. So, checked jack settings and jack.service runs even with -r 192000 -p 128 -n 2
But as soon as I start modep-mod-host and modep-mod-ui jack gives
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Looks like a sync issue with modep. Do I need to change some settings for modep somewhere?
Processing triggers for mailcap (3.70+nmu1) ...
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!
patch@patchbox:~ $ sudo pisound-config
/usr/bin/pisound-config: 2: exec: /usr/local/pisound/pisound-config/main.py: not found
When looking I don’t see that directory per say but I do see pisound-config in /bin
However when you run it you are left with the following :
./pisound-config: 2: exec: /usr/local/pisound/pisound-config/main.py: not found
Looks as if things are working kind of?I am not sure why things are not pointing to the correct location as I currently mirror the patch@patchbox user/directory. I was hoping that it would have resolved the issue but it did not. Maybe a script edit?
patchbox@patchbox:~ $ curl https://blokas.io/pisound/install.sh | sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1656 100 1656 0 0 4089 0 --:--:-- --:--:-- --:--:-- 4099
Checking if the kernel version is 6.1.74 or newer... It's not.
Your Linux kernel version (6.1.0-rpi7-rpi-2712) is below the recommended kernel version (6.1.74)!
Please upgrade it first by running the below command and following on screen instructions, and run Pisound install again!
sudo rpi-update
patchbox@patchbox:~ $
sudo rpi-update
patchbox@patchbox:~ $ sudo rpi-update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Performing self-update
*** Relaunching after update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
FW_REV:a31776f0abb4bee5b79a3334bf748c99a813c084
BOOTLOADER_REV:11c64e3721d104319d8b0f18b675d9beb4eb7f30
*** We're running for the first time
*** Backing up files (this will take a few minutes)
*** Backing up firmware
*** Backing up modules 6.1.0-rpi7-rpi-2712
WANT_32BIT:0 WANT_64BIT:1 WANT_PI4:1 WANT_PI5:1
##############################################################
WARNING: This update bumps to rpi-6.6.y linux tree
See: https://forums.raspberrypi.com/viewtopic.php?p=2191175
'rpi-update' should only be used if there is a specific
reason to do so - for example, a request by a Raspberry Pi
engineer or if you want to help the testing effort
and are comfortable with restoring if there are regressions.
DO NOT use 'rpi-update' as part of a regular update process.
##############################################################
Would you like to proceed? (y/N)
Downloading bootloader tools
Downloading bootloader images
*** Downloading specific firmware revision (this will take a few minutes)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 142M 100 142M 0 0 2750k 0 0:00:52 0:00:52 --:--:-- 3019k
BOOTLOADER: up to date
CURRENT: Fri 16 Feb 15:28:41 UTC 2024 (1708097321)
LATEST: Fri 16 Feb 15:28:41 UTC 2024 (1708097321)
RELEASE: latest (/lib/firmware/raspberrypi/bootloader-2712/latest)
Use raspi-config to change the release.
*** Updating firmware
*** Updating kernel modules
*** depmod 6.6.18-v8+
*** depmod 6.6.18-v8-16k+
*** Updating VideoCore libraries
*** Running ldconfig
*** Storing current firmware revision
*** Deleting downloaded files
*** Syncing changes to disk
*** If no errors appeared, your firmware was successfully updated to a31776f0abb4bee5b79a3334bf748c99a813c084
*** A reboot is needed to activate the new firmware
Figured it out. The OS image I have automatically sets up the default user settings (ex. Wifi) so at the point in the script it does its hotspot stuff it drops any wifi connection. Any connections at that point are refused. Causing the errors we see above. I just plugged it in via network cable and disabled wifi and have had no issues with this thus far.