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

Wheaten · June 2, 2025, 7:31pm

HW:

Raspberry Pi 4 Model B Rev 1.4, Version: d03114
HiFiBerry DAC Plus
Innomaker DAC Mini
iFi Zen DAC V2
Pro-ject Pre Box S2 Digital
Waveshare 4.3 inch DSI

Tested:

Updated from V4.005 to V4.010 => OK
NAS Mount via CIFS, Options blank => OK
Rotary encoder => OK
IR Controller => OK
System Info => OK
Touch display => OK
Radio Paradise => OK
80s80s Radio => OK
Spotify => OK
FusionDSP => OK
PeppyMeterBasic => OK
PeppySpectrum => OK

Sound:

DSD 64, 128, 256, 512 => OK
MP3 => OK
MP4 => OK
Flac 44.1kHz (16, 24, 32 Bit) => OK
Flac 48kHz (16, 24, 32 Bit) => OK
Flac 96kHz (16, 24, 32 Bit) => OK
Flac 192kHz (16, 24, 32 Bit) => OK
Flac 384kHz (16, 24, 32 Bit) => OK
WAV 44kHz-16bit, 48kHz-16bit, 88kHz-24bit, 96kHz-32bit, 176kHz-32bit, 192kHz-32bit => OK

Fail:

Qobuz => Playlist => Search => Volumio crashes. Same behaviour as webradio.
Tidal => Genre/moods => Search => Volumio crashes. Same behaviour as webradio.

nerd · June 3, 2025, 7:15am

Dear Volumionauts,

I’ve received a few reports regarding problems connecting Bluetooth remotes (e.g. media controllers, button pads, etc.). While our main focus remains bit-perfect audio, I’m willing to investigate further to see if we can add support for remote control devices.

To do that, I need your help with more detailed reports.

If you’re experiencing issues with a Bluetooth remote, please reply with the following:

Device model (e.g. 8BitDo Remote, FiiO controller, etc.)
Hardware platform (e.g. Raspberry Pi 3B+, x86, etc.)
Bluetooth dongle or internal chip model (run lsusb or hciconfig -a)
Hardware class of the remote (e.g. HID, HID over GATT, AVRCP, custom)
Steps to reproduce the issue (pairing, reconnecting, button press behavior, etc.)
What works / what fails (e.g. pairs successfully but no media keys detected)
Log URL from http://<volumio_IP>/dev after attempting the connection

The more precise your report, the better we can replicate, observe, and possibly fix.

Thanks in advance for your help.

Kind Regards,

nerd · June 3, 2025, 7:50am

A post was merged into an existing topic: Public Beta Test: Audio Without Compromise - Plugin Compatibility for Volumio on Bookworm

nerd · June 3, 2025, 8:03am

Dear Volumionauts,

Problems with Plugins

To keep the Bookworm Public Beta organized, please report all plugin-related issues, feedback, or migration status updates in this post:

Public Beta Test: Audio Without Compromise - Plugin Compatibility for Volumio on Bookworm

This helps us separate plugin concerns from core system functions and ensures your input reaches the right maintainers.

Kind Regards,

SimonE · June 3, 2025, 10:55am

Hi @nerd,
Maybe I’m confusing two issues. But in my case the Bluetooth issue concerned playing music from a Windows 11 laptop through Volumio on a Pi4 (with Bluetooth input playback switched on in Sources). So no remote, dongle, etc.

This worked on Alpha, but not Beta (unable to connect). My Android phone however was able to connect via BT and play music via Volumio. The laptop is old, from 2016, the phone is new.

I’ll try again this evening after forgetting all BT connections and rebooting.
Thanks, Simon

Robert.Hecht · June 3, 2025, 11:09am

same here.

nerd · June 3, 2025, 12:35pm

Hey @balbuze, @Robert.Hecht,

Confirmed here - update from v4.005 to v4.010 fails with the boundary array error.

The UI message recommends a clean flash:

Updating to the latest version on this system is unfortunately not possible. Please download the latest Volumio and flash your SD Card from scratch.

Details:

Affected: amd64 v4.010
Failure point: malformed boundary size array check
Status: will be fixed in the next Beta release

Until then, safest route is to reflash with the latest image once available.

Kind Regards,

nerd · June 3, 2025, 12:41pm

Hey @SimonE,

Windows remembers (caches) previously trusted Bluetooth devices, and that can cause pairing issues - especially if the stack on the Volumio side has changed between Alpha and Beta. Since your Android phone connects fine but the Windows 11 laptop (2016 model) fails only on Beta, it’s likely due to cached trust.

Here are some things to try:

Forget the Volumio Bluetooth device on the Windows side:
Settings → Bluetooth & Devices → Devices → Click on Volumio → Remove Device.
Reboot both devices (Volumio Pi and Windows laptop).
Initiate pairing from Windows, not Volumio. On some older adapters, initiating from the Windows side is more reliable.
If it still fails:
- Check if the laptop supports A2DP Sink role - some older BT chipsets or Windows builds struggle with media roles.
- Make sure Volumio is not still paired with the laptop from a previous session or profile.

If it still doesn’t connect, please:

Post a log link from Volumio Beta after attempting the Windows connection failure:
Go to http://<volumio-ip>/dev, click Submit Log, and paste the URL here.

Kind Regards,

rkorell · June 3, 2025, 1:41pm

Dear @nerd,

today I was able to connect the BT remote to the 4.010 beta release of volumio.
Have done exactly same as yesterday, but today it worked.

Unfortunately despite successful pairing, keystrokes are not recognized.

Device model Bluetooth Media Button
Hardware platform Raspberry Pi 5
Bluetooth dongle or internal chip model
Internal Chip :

volumio@korellmusik:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 1997:2433 Shenzhen Riitek Technology Co., Ltd wireless mini keyboard with touchpad
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
volumio@korellmusik:~$ hciconfig -a
hci0:   Type: Primary  Bus: UART
        BD Address: 2C:CF:67:60:4C:23  ACL MTU: 1021:8  SCO MTU: 64:1
        UP RUNNING PSCAN
        RX bytes:9620 acl:373 sco:0 events:434 errors:0
        TX bytes:68483 acl:10 sco:0 commands:408 errors:0
        Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH SNIFF
        Link mode: PERIPHERAL ACCEPT
        Name: 'korellmusik'
        Class: 0x0c041c
        Service Classes: Rendering, Capturing
        Device Class: Audio/Video, Portable Audio
        HCI Version: 5.0 (0x9)  Revision: 0x17e
        LMP Version: 5.0 (0x9)  Subversion: 0x6119
        Manufacturer: Cypress Semiconductor (305)

Hardware class of the remote HID, I believe .

For your records - what I have done :

volumio@korellmusik:~$ bluetoothctl
Agent registeredct to bluetoothd...
AdvertisementMonitor path registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
SetDiscoveryFilter success
Discovery started
[CHG] Controller 2C:CF:67:60:4C:23 Discovering: yes
[NEW] Device 30:4A:3F:23:57:0B 30-4A-3F-23-57-0B
[NEW] Device 3D:28:DA:58:D5:E6 3D-28-DA-58-D5-E6
[NEW] Device 01:41:D1:7F:8A:0E 01-41-D1-7F-8A-0E
[NEW] Device 2F:EF:09:E0:60:9E 2F-EF-09-E0-60-9E
[NEW] Device 2D:6A:12:4C:EE:11 2D-6A-12-4C-EE-11
[DEL] Device 30:4A:3F:23:57:0B 30-4A-3F-23-57-0B
[DEL] Device 3D:28:DA:58:D5:E6 3D-28-DA-58-D5-E6
[DEL] Device 01:41:D1:7F:8A:0E 01-41-D1-7F-8A-0E
[NEW] Device 0C:FC:83:8B:91:C5 BT005   <--THIS is the BT remote

[bluetooth]# pair 0C:FC:83:8B:91:C5
Attempting to pair with 0C:FC:83:8B:91:C5
[CHG] Device 0C:FC:83:8B:91:C5 Connected: yes
[CHG] Device 0C:FC:83:8B:91:C5 Bonded: yes
[CHG] Device 0C:FC:83:8B:91:C5 WakeAllowed: yes
[CHG] Device 0C:FC:83:8B:91:C5 Modalias: usb:v0000p0000d0000
[CHG] Device 0C:FC:83:8B:91:C5 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 0C:FC:83:8B:91:C5 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 0C:FC:83:8B:91:C5 ServicesResolved: yes
[CHG] Device 0C:FC:83:8B:91:C5 Paired: yes
Pairing successful
[CHG] Device 0C:FC:83:8B:91:C5 ServicesResolved: no
[CHG] Device 0C:FC:83:8B:91:C5 Connected: no
[bluetooth]# trust 0C:FC:83:8B:91:C5
[CHG] Device 0C:FC:83:8B:91:C5 Trusted: yes
Changing 0C:FC:83:8B:91:C5 trust succeeded
[bluetooth]# connect 0C:FC:83:8B:91:C5
Attempting to connect to 0C:FC:83:8B:91:C5
[CHG] Device 0C:FC:83:8B:91:C5 Connected: yes
Connection successful
[CHG] Device 0C:FC:83:8B:91:C5 ServicesResolved: yes
[BT005]# exit

What the volumio system “thinks” about this is logged in:

logfile

In all other earlier installationt the BT device broadcasts on channel 0 so I have modified triggerhappy config file:

sudo nano /etc/triggerhappy/triggers.d/audio.conf
(i commented out default config and added below)
KEY_PLAYPAUSE 0 /usr/local/bin/volumio toggle
KEY_NEXTSONG 0 /usr/local/bin/volumio next
KEY_PREVIOUSSONG 0 /usr/local/bin/volumio previous
sudo /etc/init.d/triggerhappy reload
rm /lib/systemd/system/triggerhappy.socket

sudo reboot

As stated above unfortunately keystrokes are not recognized

For this reason I’ve tried to catch keystrokes with thd :

volumio@korellmusik:~$ sudo thd --dump /dev/input/event0
^Z
[1]+  Stopped                 sudo thd --dump /dev/input/event0
volumio@korellmusik:~$ sudo thd --dump /dev/input/event1
^Z
[2]+  Stopped                 sudo thd --dump /dev/input/event1
volumio@korellmusik:~$ sudo thd --dump /dev/input/event2
^Z
[3]+  Stopped                 sudo thd --dump /dev/input/event2

So no success there.
To double-check BT connection tried bluetoothctl again:

volumio@korellmusik:~$ bluetoothctl
Agent registered
AdvertisementMonitor path registered
[BT005]# exit
volumio@korellmusik:~$

BT005 is written as prompt which I interpret as connected.

So far my findings.
regards,
Ralf

Josh2000 · June 3, 2025, 3:19pm

i did OTA from a fresh installed 4.005 to 4.008 in alpha mode, then switched to test and OTA to 4010 worked fine

RPI3
Allo Kali + Piano2.1

Dual Mono still working perfect here

sorry for the short report - had an exam today for BCM (other thing….)

Wheaten · June 3, 2025, 3:46pm

BCM, euh:

Bouncing Crazy Marshmallows
Big Cheesy Muffin
Bewildered Clumsy Monkeys
Blazing Comet Madness
Bearded Cabbage Magician

Gelo5 · June 3, 2025, 3:52pm

*Business Continuity Management
*Body Control Module
*Bravo Company Manufacturing

nerd · June 3, 2025, 3:54pm

Hey @Wheaten, @Gelo5

Unable to find such process. Searching for modules…
Result: none found - perhaps all of them are still in pre-alpha or written in crayon.

If none of the above apply, then surely these must be webradio search results -
and I’m delighted that it works - at last!

Kind Regards,

RedEyeNinja · June 3, 2025, 4:40pm

@nerd

Pi4 8gb on 4.010, Hifiberry Digi did not initiate after reboot. There were some error messages about no device or device not found popped up on screen.

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

running:

aplay -D hw:2,0 --dump-hw-params /dev/zero

showed:

ALSA lib confmisc.c:165:(snd_config_get_card) Cannot get card index for 2
aplay: main:831: audio open error: No such file or directory

Unplugging it and leaving it off for a few minutes solved it as before. 44.1/16 playback was fine, 192/24 was silent thru i2s/HDMI. As noted prior, 192/24 plays fines on coax/spdif but not DSD…and thru i2s/HDMI, DSD and 96/24 and below plays fine except 192/24.

Here’s an entry for the Pi4 matrix you requested:

aplay -D hw:2,0 --dump-hw-params /dev/zero

Playing raw data '/dev/zero' : Unsigned 8 bit, Rate 8000 Hz, Mono
HW Params of device "hw:2,0":
--------------------
ACCESS:  MMAP_INTERLEAVED RW_INTERLEAVED
FORMAT:  S16_LE S24_LE
SUBFORMAT:  STD
SAMPLE_BITS: [16 32]
FRAME_BITS: [32 64]
CHANNELS: 2
RATE: [32000 192000]
PERIOD_TIME: (166 2048000]
PERIOD_SIZE: [32 65536]
PERIOD_BYTES: [256 524288]
PERIODS: [2 4096]
BUFFER_TIME: (333 4096000]
BUFFER_SIZE: [64 131072]
BUFFER_BYTES: [256 524288]
TICK_TIME: ALL
--------------------
aplay: set_params:1352: Sample format non available
Available formats:
- S16_LE
- S24_LE

aplay 192kHz WAV

This one I don’t understand. Do you want me to manually select the file to play via aplay? Let me know and I can update.

speaker-test -D hw:2,0 -c 2 -r 192000 -F S32_LE

speaker-test 1.2.8

Playback device is hw:2,0
Stream parameters are 192000Hz, S32_LE, 2 channels
Using 16 octaves of pink noise
Sample format not available for playback: Invalid argument
Setting of hwparams failed: Invalid argument

Playback via Volumio

44.1/16 played fine, 192/24 was silent, no error msg on screen
Only using Touch Display and Now Playing plugin’s.
DAC shows 192kHz, but no sound

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

I’ll update on the testing on the Pi5 and the matrix you requested.

Josh2000 · June 3, 2025, 4:46pm

You got it, it’s business continuity management

Robert.Hecht · June 3, 2025, 5:39pm

Hi,

after a fresh flash of the 4.010 on AMD64 I saw an interrupted scan of the local music library. An attached USB drive has been scanned until track 6450 and then the scan stopped. I startet it manually again. Here’s the log:

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

Cheers,
Robert

SimonE · June 3, 2025, 6:18pm

Hi @nerd,
No joy connecting via Bluetooth on my laptop. Again, no problem using my Android phone.

Tried:

Restart Volumio and laptop
Remove all learned Bluetooth devices from the laptop
Pairing attempt from the laptop

I don’t know how to check if the laptop supports A2DP Sink

Log after failure to connect
http://logs.volumio.org/volumio/pIHN8Nq.html

Simon

seanvan · June 3, 2025, 7:22pm

Issue Flashing Raspberry Pi Image – Archive Extraction Error

Hi everyone,

I’ve been following the progress of Volumio on Bookworm and was excited to see the shift to an open beta! However, I’ve encountered an issue when trying to download and flash the Raspberry Pi image.

Problem:

After downloading the image multiple times to rule out corruption, I consistently receive an error when trying to flash it.
The error message states: “Error extracting archive: File size could not be restored.”
I’ve attempted flashing with both Raspberry Pi Imager and BalenaEtcher, but neither has worked.

Troubleshooting Steps Taken:

Downloaded the image several times.
Tried multiple microSD cards.
Used different flashing tools (Raspberry Pi Imager & BalenaEtcher).
Ensured my system was correctly detecting the microSD cards.

Possible Causes & Questions:

Is the image file currently being served possibly corrupt?
Has anyone else experienced this issue with the latest beta?
Are there known workarounds or alternative flashing methods that might resolve this?

Would appreciate any insights or advice from the community! Thanks in advance for the help.

SimonE · June 3, 2025, 7:34pm

Just checking - you did unzip it?

Robert.Hecht · June 3, 2025, 7:38pm

Hi @seanvan ,

as the pi image has been downloaded more than 20 times I don’t believe there is e problem with the image itself. Please doublecheck he following:

did you extract the image from the zip file before flashing it?
did you select the correct target to flash it on?
does the medium match the minimum size requirements of now 8GB?
sometimes tools get dazzled. I’ve good experience with the rufus flashing tool (assuming you’re working on a M$ Windows platform).

Hope it helps.

Cheers,
Robert