Public Beta Test: Audio Without Compromise - Refining the Future of Volumio on Bookworm

RedEyeNinja · July 9, 2025, 3:49pm

Some interesting new observations, at least to me. After “Touch Display” crashed my Pi5, I reflashed. At setup, an option I had mentioned before came up again.

This is again for the R19 HAT, but this time I just went with it to see what will happen. No FusionDSP, no PeppyMeter Basic. It did the usual thing thru i2s/HDMI…loud clicks and pops at the start of the song, no sound for 192/24. DSD played as DOP for 1 song, and then it wouldn’t start another one but the clicks and pops when trying to start remained. For kicks, I changed Playback Option to DOP [selecting DOP manually] and then tried the same round of tests again. For whatever reason, again I had manually selected DOP on Playback Option, it started playing DSD native, albeit with loud clicks and pops at the start of the song…but it played multiple DSD natively like this thru i2s/HDMI. Here’s a log.

http://logs.volumio.org/volumio/hSCJafd.html

EDIT: I also have a Pi4 and mini PC running the latest 4.015 with no issues to report thru USB playback.

RedEyeNinja · July 10, 2025, 6:10pm

Pi5 and PC on 4.015 can not reach plugin server. Having looked at my firewall, this is what I see as being blocked. Can someone confirm this address and correct and appropriate before I let them thru? They were obviously connecting fine before, so this is new.

nerd · July 11, 2025, 4:42am

Hey @RedEyeNinja,

Thanks for confirming. You’re absolutely right - the log from hSCJafd.html still shows the same fundamental issues:

ASoC: DAI link failures
I2C errors when the i-sabre overlay attempts communication
Playback start/stop instability with loud clicks
No sound for 192/24 after stream change or DAC desync

No surprise there - the R19 remains non-compliant with the expected i-sabre-q2m overlay behavior.

The upcoming kernel 6.12.34 may indeed shift things. If upstream Raspberry Pi changes or internal Volumio overlay patches adjust DAI or codec probing order, the board could behave differently (for better or worse). We’ll re-test against it as soon as it lands in the weekly build.

In the meantime, your workaround testing is still valuable - especially the observation that manually selecting DoP seems to let DSD play multiple tracks in succession (albeit with clicks), suggesting the board may only partially implement DoP framing, and not at ALSA level.

Let’s revisit once 6.12.34 is in and revalidate core behavior again.

Kind Regards,

hifiswede · July 11, 2025, 8:08am

i made together with chatgpt this script.

!/bin/bash

# Log start
echo "$(date): Starting delayed Wi-Fi connection" >> /home/volumio/wifi-log.txt

# Wait 2 minutes
sleep 120

# Bring up wlan0
ip link set wlan0 up

# Kill any previous wpa_supplicant instances
killall wpa_supplicant 2>/dev/null

# WPA config
cat > /home/volumio/wpa.conf <<EOF
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
network={
    ssid="YourSSID"
    psk="YourPassword"
    key_mgmt=WPA-PSK
}
EOF

# Start wpa_supplicant
/sbin/wpa_supplicant -B -i wlan0 -c /home/volumio/wpa.conf

# Wait to associate
sleep 10

# Request IP using dhcpcd
/sbin/dhcpcd wlan0

# Log result
if ip addr show wlan0 | grep -q "inet "; then
  echo "$(date): Wi-Fi connected and IP assigned" >> /home/volumio/wifi-log.txt
else
  echo "$(date): Wi-Fi failed to connect" >> /home/volumio/wifi-log.txt
fi

made a service that runs it

[Unit]
Description=Delayed Wi-Fi Connection
After=network.target

[Service]
ExecStart=/home/volumio/wifi.sh
Type=oneshot
RemainAfterExit=true

[Install]
WantedBy=multi-user.target

and now it works without cable, until a real solution comes up.

thanks

Klasw · July 11, 2025, 2:06pm

Hi!

I installed Volumio 4 latest beta version, on PC. Every thing functions quite good, even youtube music, but not to HDMI.

I have two sound card, HDMI over my Marantz AVR surround receiver and Maverick Tubemagic DAC 2. For the record, I had turned of motherboard build in soundcard in bios settings.

Sound functions out from the Maverick, but not from HDMI. I got this message:

Volumio failed to open alsa (alsa). Failed to open ALSA device on “volumio”. No such file or directory.

I had tried to flip flop controls and al combinations of configuration. I have tested restart. Also tested adding;

options snd_hda_intel index=0
options snd-usb-audio index=5

in new file;
/etc/modprobe.d/sound.conf

(then a restart)

I have tested sound out from console, there is sound, tested by;

speaker-test -Dhw:0,3 -c 6

**This is my aplay -l;**

evi* List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [marantz-AVR]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
  Subdces: 1/1
  Subdevice #0: subdevice #0
card 5: TE7022 [Maverick Audio TE7022], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 5: TE7022 [Maverick Audio TE7022], device 1: USB Audio [USB Audio #1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

This is my aplay -L:

hw:CARD=NVidia,DEV=3
    HDA NVidia, marantz-AVR
    Direct hardware device without any conversions
hw:CARD=NVidia,DEV=7
    HDA NVidia, HDMI 1
    Direct hardware device without any conversions
hw:CARD=NVidia,DEV=8
    HDA NVidia, HDMI 2
    Direct hardware device without any conversions
hw:CARD=NVidia,DEV=9
    HDA NVidia, HDMI 3
    Direct hardware device without any conversions
plughw:CARD=NVidia,DEV=3
    HDA NVidia, marantz-AVR
    Hardware device with all software conversions
plughw:CARD=NVidia,DEV=7
    HDA NVidia, HDMI 1
    Hardware device with all software conversions
plughw:CARD=NVidia,DEV=8
    HDA NVidia, HDMI 2
    Hardware device with all software conversions
plughw:CARD=NVidia,DEV=9
    HDA NVidia, HDMI 3
    Hardware device with all software conversions
hdmi:CARD=NVidia,DEV=0
    HDA NVidia, marantz-AVR
    HDMI Audio Output
hdmi:CARD=NVidia,DEV=1
    HDA NVidia, HDMI 1
    HDMI Audio Output
hdmi:CARD=NVidia,DEV=2
    HDA NVidia, HDMI 2
    HDMI Audio Output
hdmi:CARD=NVidia,DEV=3
    HDA NVidia, HDMI 3
    HDMI Audio Output
dmix:CARD=NVidia,DEV=3
    HDA NVidia, marantz-AVR
    Direct sample mixing device
dmix:CARD=NVidia,DEV=7
    HDA NVidia, HDMI 1
    Direct sample mixing device
dmix:CARD=NVidia,DEV=8
    HDA NVidia, HDMI 2
    Direct sample mixing device
dmix:CARD=NVidia,DEV=9
    HDA NVidia, HDMI 3
    Direct sample mixing device
usbstream:CARD=NVidia
    HDA NVidia
    USB Stream Output
hw:CARD=TE7022,DEV=0
    Maverick Audio TE7022, USB Audio
    Direct hardware device without any conversions
hw:CARD=TE7022,DEV=1
    Maverick Audio TE7022, USB Audio #1
    Direct hardware device without any conversions
plughw:CARD=TE7022,DEV=0
    Maverick Audio TE7022, USB Audio
    Hardware device with all software conversions
plughw:CARD=TE7022,DEV=1
    Maverick Audio TE7022, USB Audio #1
    Hardware device with all software conversions
sysdefault:CARD=TE7022
    Maverick Audio TE7022, USB Audio
    Default Audio Device
front:CARD=TE7022,DEV=0
    Maverick Audio TE7022, USB Audio
    Front output / input
surround21:CARD=TE7022,DEV=0
    Maverick Audio TE7022, USB Audio
    2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=TE7022,DEV=0
    Maverick Audio TE7022, USB Audio
    4.0 Surround output to Front and Rear speakers
surround41:CARD=TE7022,DEV=0
    Maverick Audio TE7022, USB Audio
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=TE7022,DEV=0
    Maverick Audio TE7022, USB Audio
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=TE7022,DEV=0
    Maverick Audio TE7022, USB Audio
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=TE7022,DEV=0
    Maverick Audio TE7022, USB Audio
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=TE7022,DEV=0
    Maverick Audio TE7022, USB Audio
    IEC958 (S/PDIF) Digital Audio Output
iec958:CARD=TE7022,DEV=1
    Maverick Audio TE7022, USB Audio #1
    IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=TE7022,DEV=0
    Maverick Audio TE7022, USB Audio
    Direct sample mixing device
dmix:CARD=TE7022,DEV=1
    Maverick Audio TE7022, USB Audio #1
    Direct sample mixing device
usbstream:CARD=TE7022
    Maverick Audio TE7022
    USB Stream Output

any help appreciated.

benatreptar · July 12, 2025, 8:39am

4.016 fresh installed this morning with RPi 4 / SSD boot by USB 3.0 plug / Digione Signature (no need to reboot ! Great !!!) / Official RPi Touch Display v2 DSI port (plugin touch display installed). Everything works fine !!!
Great job guys !!!
Follow-up !!!

rkorell · July 12, 2025, 10:05am

Good morning!

Just installed 4.016 via OTA - went without problems.
Capability of reboot from installer/GUI is still missing - hard reset neccessary.

Have tried @gkkpch’s tip and issued

sudo journalctl -f > /data/INTERNAL/reboot-issue.log

here the (from my perspective) short logfile result.

Jul 12 11:50:31 korellmusik systemd[1]: Started user@1000.service - User Manager for UID 1000.
Jul 12 11:50:31 korellmusik systemd[1]: Started session-1.scope - Session 1 of User volumio.
Jul 12 11:50:31 korellmusik sshd[2491]: pam_env(sshd:session): deprecated reading of user environment enabled
Jul 12 11:50:51 korellmusik go-librespot[1815]: time="2025-07-12T11:50:51+02:00" level=trace msg="sent dealer ping"
Jul 12 11:50:52 korellmusik go-librespot[1815]: time="2025-07-12T11:50:52+02:00" level=trace msg="received dealer pong"
Jul 12 11:51:00 korellmusik systemd[1]: systemd-timedated.service: Deactivated successfully.
Jul 12 11:51:21 korellmusik go-librespot[1815]: time="2025-07-12T11:51:21+02:00" level=trace msg="sent dealer ping"
Jul 12 11:51:21 korellmusik go-librespot[1815]: time="2025-07-12T11:51:21+02:00" level=trace msg="received dealer pong"
Jul 12 11:51:35 korellmusik sudo[2636]:  volumio : TTY=pts/0 ; PWD=/home/volumio ; USER=root ; COMMAND=/usr/bin/journalctl -f
Jul 12 11:51:35 korellmusik sudo[2636]: pam_unix(sudo:session): session opened for user root(uid=0) by volumio(uid=1000)
Jul 12 11:51:35 korellmusik systemd[1]: Starting setdatetime-helper.timer.service - Volumio Time Sync Watchdog Service...
Jul 12 11:51:35 korellmusik dbus-daemon[1072]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.36' (uid=0 pid=2640 comm="timedatectl show --property=NTPSynchronized --valu")
Jul 12 11:51:35 korellmusik systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Jul 12 11:51:36 korellmusik dbus-daemon[1072]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jul 12 11:51:36 korellmusik systemd[1]: Started systemd-timedated.service - Time & Date Service.
Jul 12 11:51:36 korellmusik setdatetime-helper.sh[2639]: Time is not synchronized. Attempting to sync...
Jul 12 11:51:36 korellmusik sudo[2648]:     root : PWD=/ ; USER=root ; COMMAND=/usr/bin/date -s 'Sat, 12 Jul 2025 09:51:36 GMT#015'
Jul 12 11:51:36 korellmusik sudo[2648]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 12 11:51:36 korellmusik setdatetime-helper.sh[2649]: Sat Jul 12 11:51:36 CEST 2025
Jul 12 11:51:36 korellmusik sudo[2648]: pam_unix(sudo:session): session closed for user root
Jul 12 11:51:36 korellmusik setdatetime-helper.sh[2639]: Time synchronized successfully.
Jul 12 11:51:36 korellmusik systemd[1]: setdatetime-helper.timer.service: Deactivated successfully.
Jul 12 11:51:36 korellmusik systemd[1]: Finished setdatetime-helper.timer.service - Volumio Time Sync Watchdog Service.
Jul 12 11:51:36 korellmusik systemd-journald[443]: Time jumped backwards, rotating.
Jul 12 11:51:51 korellmusik go-librespot[1815]: time="2025-07-12T11:51:51+02:00" level=trace msg="received accesspoint ping"
Jul 12 11:51:51 korellmusik go-librespot[1815]: time="2025-07-12T11:51:51+02:00" level=trace msg="received accesspoint pong ack"
Jul 12 11:51:51 korellmusik go-librespot[1815]: time="2025-07-12T11:51:51+02:00" level=trace msg="sent dealer ping"
Jul 12 11:51:51 korellmusik go-librespot[1815]: time="2025-07-12T11:51:51+02:00" level=trace msg="received dealer pong"
Jul 12 11:52:05 korellmusik systemd[1]: systemd-timedated.service: Deactivated successfully.
Jul 12 11:52:21 korellmusik go-librespot[1815]: time="2025-07-12T11:52:21+02:00" level=trace msg="sent dealer ping"
Jul 12 11:52:21 korellmusik go-librespot[1815]: time="2025-07-12T11:52:21+02:00" level=trace msg="received dealer pong"

BT remote still is connected but doesn’t work.

(HW) Config:

Pi5,
Raspi 2 Display (DSI),
Two rotary encoders on several GPIOs

NO (working) BT remote

Testing:

Spotify plugin, works (my only use case).
Touch display (and corresponding plugin) works
“Now Playing” plugin works
Rotary encoders are both working
WiFi is working (can access from laptop / phone).
BT remote is NOT working (connected but no signals detected)

CORRD link still only leads to app-store, no intergrations as far as I can see.

Nice rest of the day to all of you,
Regards,

SimonE · July 12, 2025, 3:14pm

I had this problem with 4.015 and earlier, but is now working with 4.016.
By working, I mean I can pair from my Android phone and play music from my phone through Volumio.

OTA to 4.016
Pi4B SD boot, USB dac

SimonE · July 12, 2025, 3:17pm

OTA 4.015 to 4.016
Pi4B, SD boot, USB DAC

Everything works!
Log http://logs.volumio.org/volumio/4qSdpKf.html

SimonE · July 12, 2025, 4:29pm

nerd:

After analyzing the Pi5 + HDMI failure log (mdeRXQe), I can see something concerning:

The Spotify plugin crashes due to a segmentation fault in go-librespot:
Jul 05 12:54:53 volumio go-librespot[1864]: Segmentation fault (core dumped)
error: system crashed: player: callback from go-librespot threw: TypeError: Cannot read properties of null (reading 'mute')
This segfault leads to a player state exception and a restart. The crash appears to occur when using HDMI audio output on the Pi5. It does not happen when using a USB DAC, nor does it appear in Pi4 logs under any output path.

Same after OTA to 4.016 - only with my Pi5 using HDMI. Spotify fails, other media OK.
Logs http://logs.volumio.org/volumio/UgocNl2.html

rkorell · July 12, 2025, 6:17pm

Dear @SimonE , thanks for your hint.
My UseCase is a little bit different.
I CAN connect to Bluetooth.
But I‘ve paired a remote control button to adjust volume/skip songs and start/stop playing.
The function is (in earlier releases) realized via the „triggerhappy“ demon in the system which catches the Bluetoooth signals. But the signals of the connected remote are not recognized so triggerhappy cannot work.

Warm regards,
Ralf

SimonE · July 12, 2025, 8:14pm

Oh OK. I hope triggerhappy is working for you soon.
Simon

nerd · July 13, 2025, 7:16pm

Hey @rkorell,

Thanks for your continued patience.

Progress update:

Bluetooth Remote: The remote is successfully paired and triggering actions like volume control and play/pause toggles via triggerhappy.
Event Handling: From internal testing, the following event logs confirm that key presses are being captured and the corresponding actions are being executed correctly:

Jul 13 20:03:07 pi5dev thd[4257]: {"time":1752433386104,"response":"volume Success"}
Jul 13 20:03:07 pi5dev thd[3782]: Executing trigger action: /usr/local/bin/volumio volume plus
Jul 13 20:03:07 pi5dev thd[4262]:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Jul 13 20:03:07 pi5dev thd[4262]:                                  Dload  Upload   Total   Spent    Left  Speed
Jul 13 20:03:07 pi5dev thd[4262]: [158B blob data]
Jul 13 20:03:08 pi5dev thd[4262]: {"time":1752433387296,"response":"volume Success"}
Jul 13 20:03:08 pi5dev thd[3782]: Executing trigger action: /usr/local/bin/volumio volume plus
Jul 13 20:03:08 pi5dev thd[4267]:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Jul 13 20:03:08 pi5dev thd[4267]:                                  Dload  Upload   Total   Spent    Left  Speed
Jul 13 20:03:08 pi5dev thd[4267]: [158B blob data]
Jul 13 20:03:13 pi5dev thd[4267]: {"time":1752433388556,"response":"volume Success"}
Jul 13 20:03:13 pi5dev thd[3782]: Executing trigger action: /usr/local/bin/volumio toggle
Jul 13 20:03:13 pi5dev thd[4272]:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Jul 13 20:03:13 pi5dev thd[4272]:                                  Dload  Upload   Total   Spent    Left  Speed
Jul 13 20:03:13 pi5dev thd[4272]: [158B blob data]

Current status:

While progress has been made and some buttons are recognized, the issue is not fully resolved. I’m still seeing some inconsistencies with input recognition that need further debugging.

Next steps:

I will continue to troubleshoot and refine the event handling process to ensure all buttons are recognized and mapped correctly.
Any additional observations on key behavior would be helpful to zero in on specific issues.

Thanks again for your ongoing reports. I will keep you updated on the next steps once we make more progress.

Kind Regards,

rkorell · July 14, 2025, 6:27am

Dear @nerd, thanks a lot for your effort!
As soon as the changes are available on beta-channel (when ? ) I can try to assist you in figuring this out if you like.

Warmest regards,
Ralf

SEREGAFOX · July 14, 2025, 8:14pm

Hello ! I installed 4.016 completely from scratch on the Raspberry Pi3b +, the driver of the touchscreen in this assembly settled, at 4.015 it stopped by 70%, after installation I rebooted the system, a multi -colored square appeared for a couple of seconds and then just a black screen, Volumio did not start, turned off from the outlet for 5 minutes, 5 minutes. Included - there is no Volumio interface.
The screen 5 inches touch, not HDMI, the system is defined as A020D3
How to solve the problem?

Wheaten · July 14, 2025, 8:23pm

Please perform a factory reset first
Perform the initial setup
add to/boot/userconfig.txt

display_auto_detect=1
dtoverlay=vc4-kms-v3d

Reboot
Check if the boot logo is visible, if not your screen might need additional entries in /boot/userconfig.txt
Check if the date of the rPi3 is correct, if not correct it
Install the Touch Display plugin again

Newbiggen · July 14, 2025, 8:48pm

http://logs.volumio.org/volumio/V4UqMEX.html
Just testing v 4.016
Rpi 4 model B rev 1.4 2GB
IQAudio DAC+ Audio Hat
Openmediavault NAS
System Information Plugin - 2 screenshots

OTA update from v4.015 successful
I got a warning about ‘firmware detection failed’ before the Sytem Information was displayed
No problem playing audio from NAS and BBC Radio streaming

nerd · July 15, 2025, 6:07am

Hey @rkorell,

Thanks for following up and offering to help verify the changes.

The behavior with the Bluetooth remote input should be addressed by this PR:

https://github.com/volumio/volumio-os/pull/205

This change ensures that proper input permissions and udev propagation are applied for all HID-class Bluetooth devices like your remote. Once included, triggerhappy should consistently receive the expected events.

The fix will be included in the next beta weekly build, scheduled for this Saturday. If you’re able to test once it lands, your feedback would be helpful to confirm whether this resolves the issue fully.

Kind Regards,

nerd · July 15, 2025, 6:11am

Hey @SimonE,

Thanks for confirming that the issue persists after the OTA to 4.016, and that the segfault is still reproducible under the same Pi5 + HDMI conditions. I’ve reviewed the new log (UgocNl2), and it shows the same fatal pattern:

go-librespot segmentation fault
Followed by a null object error in the player callback
Audio playback otherwise OK for local, network, and other services

This continues to indicate a some targeted state incompatibility between go-librespot and the HDMI ALSA path on Pi5 hardware (unable to reproduce in lab).

Good to know that this is now being tracked at:
https://github.com/volumio/volumio-plugins-sources-bookworm/issues/64

We’ll monitor for further confirmations or reproductions from other users to determine if this is limited to certain Pi5 units or a broader HDMI backend issue.

Thanks again for your persistent testing and clear reporting.

Kind Regards,

nerd · July 15, 2025, 6:17am

Hey @Klasw,

Thanks for the detailed report. Just confirming this issue has now been taken over and resolved in the main Volumio x86 hardware thread here:

https://community.volumio.com/t/x86-hardware-issues-graphics-wifi-onboard-sound-external-dacs-disks-bios-uefi-boot-problems-etc/50280/1240

You successfully added the correct device profile for your NVIDIA HDMI output:

{"name": "HDA NVidia", "multidevice": true, "devices":[{"number":3, "prettyname": "HDMI-0 Marantz NR1509", "defaultmixer": ""}],"type":"integrated"},

@gkkpch confirmed that a generic version will be submitted for inclusion in the next weekly release. If possible, could you confirm here that the issue is closed?

This will help us avoid duplicate tracking.

Kind Regards,