Would you please give me an estimated date , when qobuz connect will be included in this version .! I am asking because I mainly use qobuz connect.
Thanks .
I’ve uploaded 2 logs after diabling fusiondsp and peppymeter. to test 192/24…any feddback? Since disabling both plugins did not allow for 192/24 to play, I did not re-enable them. I’ll be updating to the latest now.
These are not the same device. Test conditions are not comparable due to differing DACs, overlays, and platform.
DAC/HAT Capability Check
I-Sabre Q2M (Pi5)
aplay -D hw:0,0 --dump-hw-params /dev/zero
Expected:
RATES: 44100, 48000, 96000, 192000
FORMAT: S16_LE, S24_LE, S32_LE
→ Hardware supports 192/24 via I2S
HiFiBerry Digi (Pi4)
aplay -D hw:2,0 --dump-hw-params /dev/zero
Expected:
RATES: up to 192000 reported by driver
Output path: S/PDIF (optical or coaxial)
→ 192kHz playback may fail silently if receiver does not accept it
Sine-Wave Playback Test
I-Sabre Q2M
speaker-test -D hw:0,0 -c 2 -r 192000 -F S32_LE
Expected:
Clear tone if ALSA path functional
DMA/buffer underrun if not
HiFiBerry Digi
speaker-test -D hw:2,0 -c 2 -r 192000 -F S32_LE
Expected:
Optical/coax output to external receiver
Failure may result in silence or underrun
Request: Detailed Test Result Matrix
To properly evaluate system-layer vs plugin/userland issues, please provide the following for each device (Pi5 and Pi4) and output (I-Sabre and HiFiBerry):
If you’re not seeing any web radio stations in Volumio, while others (like myself) are seeing them just fine, this usually indicates a local issue rather than a global outage. The web radios are still available and fully functional on the current Volumio ALPHA builds.
Here are some quick steps you can try to resolve this:
1. Network Check
Ensure your device has a working internet connection. Web radios require active internet to load and stream.
2. DNS Resolution
Sometimes DNS issues can cause failure in loading station lists. Try setting DNS to a public resolver like:
1.1.1.1 (Cloudflare)
8.8.8.8 (Google)
3. Clear Web Radio Cache
If the list was partially fetched or corrupted:
Go to /data/ directory on your Volumio device via SSH
Remove the following folder:
rm -rf /data/favorites
Then reboot Volumio.
4. Try Re-Login to MyVolumio
If you’re using MyVolumio, a corrupted session can sometimes affect service access:
Log out from MyVolumio
Reboot
Log in again
5. Test with Fresh User
Try creating a new MyVolumio user account (for testing) and log in to see if the stations appear. This can help determine if the issue is account-specific.
If these steps don’t help, please provide a log link via: http://<your_volumio_ip>/dev → click Submit Log → share the URL here.
That will allow us to inspect the backend behavior and pinpoint the cause.
The Pi version (v4.x) link has already been posted - no need to use the x86 version.
I’ll share the direct link again once the build server finishes processing and the image is ready to download.
Just to manage expectations: I’m a community member like you, and while I’m committed to helping move things forward, my day job comes first. So please bear with me - your patience is genuinely appreciated.
Thanks for the gentle nudge - definitely not missed.
I actually picked up the same screen myself (out of pocket) because I was genuinely intrigued and curious about why it misbehaves. It just arrived yesterday, and while I won’t be able to dive into testing before the weekend, it’s queued up and ready to go.
Once I’ve put it through its paces, I’ll follow up with confirmed results and any refinements we might need.
On Bookworm-based Volumio builds for Raspberry Pi 5, the CPU governor is set to “conservative” by default. This means the system favors lower frequencies at idle and only ramps up CPU speed gradually when there’s sustained demand.
Is CPU Speed Set to 1.5 GHz?
No, Volumio does not lock the CPU to 1.5 GHz.
Unless explicitly capped in /boot/userconfig.txt using arm_freq=1500, the Pi 5 is free to scale up to 2.4 GHz, which is the SoC’s maximum.
What you may see is the CPU idling at lower frequencies (e.g. 600–800 MHz), which can give the impression it’s limited.
This command updates the current CPU frequency every 0.5 seconds. Here’s what to expect:
At idle: You’ll typically see values like 600000 or 800000 (i.e., 600 MHz or 800 MHz).
Under load: Try running yes > /dev/null & in another terminal to stress the CPU; you should see the frequency ramp up toward 2400000 (2.4 GHz), depending on thermal and power conditions.
You can also check the configured governor and max frequency:
This will confirm that the scaling policy is active and the real max frequency is set properly.
In summary: Volumio does not cap the Pi 5 to 1.5 GHz, but the default conservative governor means the CPU spends most of its time well below max speed unless needed.
Thank-you Nerd! I just remembered I could OTA and didn’t need the link!
Playing with several wifi dongle with this new version, but no joy. BTW do you think if i got my hands on this would it work out of the box or possibly with the Userconfig.txt tweak.
Really appreciate all you do!
Jim
I wanted to check in for some clarification regarding the Pi version running 4.003. Should we expect an OTA update to 4.004, or will it require a fresh install?
I ask because, despite trying all available channels—stable, test, and alpha—I haven’t been able to complete an OTA update. Volumio reports I am on the latest version.
Thanks again for your incredible work. Volumio has been flawless for my use so far!
We are currently investigating reported issues with DSD playback and 32-bit float. Based on feedback and initial testing, I can confirm the issue with BW and we will continue analyzing its impact.
We will share further findings as they become available. If you have any additional insights or experiences regarding this, please feel free to share.
BW => V4.001
Plugins => Touch Display
HW => rPi4
DAC => Pro-ject Per Box S2 Digital
DSD
Bookworm
Buster
0101 - Morgan Wade - Total Control DSD64.dsf
Fail
Pass
0106 - Morgan Wade - 2AM in London DSD128.dsf
Fail
Pass
0107 - Morgan Wade - Hansel and Gretel DSD256.dsf
Fail
Pass
0110 - Morgan Wade - Walked on Water DSD512.dsf
Fail
Pass
44.1kHz
0101 - Bon Jovi - Limitless 44-16.flac
Pass
Pass
0201 - Bon Jovi - Do What You Can 44-24.flac
Pass
Pass
0301 - Bon Jovi - American Reckoning 44-32.flac
Fail
Pass
48kHz
0101 - Alice Cooper - Paranorma 48-16.flac
Pass
Pass
0201 - Alice Cooper - Dead Flies 48-24.flac
Pass
Pass
0301 - Alice Cooper - Fireball 48-32.flac
Fail
Pass
96kHz
0101 - Bruce Springsteen - Born to Run 96-16.flac
Pass
Pass
0201 - Bruce Springsteen - Thunder Road 96-24.flac
Pass
Pass
0301 - Bruce Springsteen - Badlands 96-32.flac
Fail
Pass
192kHz
0101 - Eric Clapton - Cocaine 192-16.flac
Pass
Pass
0102 - Eric Clapton - Wonderful Tonight 192-24.flac
Based on matching failures on a Pi5dev test system, we believe the root cause of both DSD and 32-bit float playback issues on Bookworm is the use of plug in the final ALSA output stage. This forces format conversions that can silently reject DSD-native streams and truncate or fail 32-bit float input.
WAV files succeed because they bypass the FLAC decoder and possibly avoid format negotiation issues. Once plug is removed and output is directed to the DAC via hw, both DSD and float playback succeed in our tests.
hello Nerd
Here are the log files as requested of 0.69 on the 1B. config.txt (746 Bytes) dmesg.txt (31.5 KB) lsusb.txt (16.8 KB)
I had to rename the .log files to .txt as this wouldn’t allow .log files to be pasted.
I had to crank up an old netbook with Debian (32bit) in order to read the SD card, as Windows couldn’t see these files.
Regards
