My Remote control is LE without usb dongle and just “connect” unfortunately, is not enough.
How to create a boot script (or what?) that will execute two commands: bluetoothctl and scan on? Thanx.
My Remote control is LE without usb dongle and just “connect” unfortunately, is not enough.
How to create a boot script (or what?) that will execute two commands: bluetoothctl and scan on? Thanx.
@nerd
Updated to 4.017 without issues on both my Volumio installs on RPi3B and Rpi4B.
One thing I do notice, however, is that the startup volume level setting is applied 30 secs or so after startup on both units. In other words, if I manually set the volume to, say, 90% and reboot, it takes a full 30 secs after startup before it applies the preset level of 60% (as shown by the volume level graphic - thank you for adding that ). Don’t think there was this much of a delay when you fixed the startup volume issue a few versions back.
Not a major issue, but in the above scenario, if you start playback immediately on reboot or have the Autostart plugin running with the delay set to less than 30 seconds you will get a blast of sound before it resets to the preset startup level.
Regards,
Thanks for the support and I have solved the problem related to the “Now Playing” screen display.
However, there is a problem related to some music file formats in my library - *.APE and DSD. I use DAC SMSL SU9 Pro (Output device: SMSL USB Audio), when listening to music with Volumio 3.xxx everything is normal, and I do not encounter the following problems:
Hi @DungLD
Have you tried to increase the buffer audio size in playback option ? Just rise it to 16 MB to see if there is any different behavior.
Regards
On what kind of hardware are you running V4?
My hardwares:
Memory card: SD 16GB
Computer: Pi5
Storage: SSD 512GB.
DAC: SMSL SU9 Pro (https://bitly.li/RxpL)
I have set the audio buffer size to 12MB as it was (haven’t tried 16MB yet).
I will try with the size you suggested.
@nerd
Any other suggestions on your sleeve?
I understand your comments.
However, the change between Ver. 3.xxx and Ver. 4.017 is simply that I installed 02 versions of Volumio on 02 different SD memory cards, and plugged/unplugged these cards. The whole system has no changes, including all connections.
This allows me to deduce that the above situation comes from the software.
Specifically, when inserting the SD card ver. 3.xxx, playing music from APE, WAV, FLAC, DSD formats is normal, for all modes Balanced, Unbalanced, All Line Out of the DAC (of course the sound is a little changed). Switching songs, browsing the music library is also smooth, responsive.
Listening to music from Bluetooth, optical (from TV) sources is also normal.
Regarding the issue log, I will find out how to get the log file because I really have no experience.
Sincerely.
Hey @DungLD,
1. Get Volumio log link (from UI):
http://<volumio-ip>/dev
<volumio-ip>
with your actual Volumio IP address, e.g., http://192.168.1.100/dev
)http://logs.volumio.org/...
)2. SSH diagnostics - basic command set:
SSH into the Pi 5:
ssh volumio@<volumio-ip>
Default password is: volumio
Once logged in, run the following and save output:
aplay -l
cat /etc/mpd.conf | grep -A15 "audio_output"
cat /var/log/mpd.log | tail -n 100
journalctl -u mpd --no-pager --no-hostname | tail -n 100
dmesg | tail -n 100
Optional: If available, post your asound.conf
or ~/.asoundrc
:
cat /etc/asound.conf
Post the output of each command or upload a pastebin/gist link if it’s long. Once this is done, I will help analyze what broke between Volumio 3 and 4 in the DSD/DoP handling.
Kind Regards,
Following your instructions, I have done the following:
Hey @DungLD,
Thanks for the detailed logs and SSH outputs - they were very helpful.
From the analysis so far, we’ve identified that FusionDsp is currently enabled, and this plugin rewrites the audio path in Volumio using ALSA routing logic incompatible with DSD Direct or DSD-over-PCM. Specifically, it cannot handle raw DSD_U32_BE
format, which leads to the MPD process crashing and your playback failing. This matches the error seen in your log:
ALSA lib pcm_volumioswitch.c:189: unable to set sample format to DSD_U32_BE
mpd: pcm.c:728: snd_pcm_name: Assertion `pcm' failed.
To continue diagnosing and confirm this is the root cause, please follow these exact steps:
Step-by-step instructions
Go to Volumio UI - Settings - Plugins.
Disable the following plugin:
Also disable (for safety during test):
Reboot Volumio.
After reboot:
Attempt to play a DSD file from your local library.
Then:
Visit:
http://<volumio-ip>/dev
This will confirm whether the core system (without audio-altering plugins) can properly handle DSD playback on Volumio 4.017 with your DAC.
Once we have that log, we’ll proceed step-by-step to confirm if plugin interference is the root cause, or if deeper changes are needed.
Kind Regards,
I have been having an issue where sound seems to stop. There’s no output sound and the UI timestamp is also stopped but if I refresh the page it will increase. So it seems like the song is playing just no output sound. If I hit the play button sound starts again.
If I go into /dev I can see the song changes as well once its done.
I pulled logs here. Let me know anything else I can get. I have had it happen a few times this time I woke up and found it had happened overnight so I’m not sure exactly when it started. I can try to get a log next time it happens so you have a clearer time frame.
https://logs.volumio.org/volumio/9cUyqNY.html
This is a Rasberry Pi 5 with a HiFiBerry DAC+ Pro and streaming from a NFS NAS.
Edit: It happened again just now
http://logs.volumio.org/volumio/Yx42LG6.html
I think it’s smart to clean/repair your mp3 files first.
Your log contains about 350+ errors. If Volumio tries to play one of these broken files, no clue what will happen.
Here are a few of the many:
[src/libmpg123/id3.c:INT123_parse_new_id3():1086] error: Whoa! ID3v2 frame claims to be larger than the whole rest of the tag.
[src/libmpg123/parse.c:skip_junk():1317] error: Giving up searching valid MPEG header after 65536 bytes of junk.
[src/libmpg123/id3.c:process_comment():584] error: No comment text / valid description?
Note: Illegal Audio-MPEG-Header 0x00000000 at offset 5103249.
[src/libmpg123/parse.c:wetwork():1406] error: Giving up resync after 1024 bytes - your stream is not nice... (maybe increasing resync limit could help).
2025-07-23T11:54:44 mpg123: mpg123_read() failed: A generic mpg123 error.
error: scanFolder - failure to stat '/mnt/NAS/proxmox-share/
Thanks @Wheaten I had this same setup on the previous volumio and didn’t have an issue.
How would I clean up or repair my MP3s?
error: scanFolder - failure to stat '/mnt/NAS/proxmox-share/
(78 errors)Dear Volumionauts,
We are officially entering pre-release phase for the Volumio Bookworm Beta. This marks a critical milestone in the evolution of Volumio 4 - the systems are in place, the architecture is stable, and we are stepping into the final stretch before full release.
What does this mean?
This is a major systems achievement. The migration from Debian Buster to Bookworm involved:
The result is a modern, future-proof foundation for Volumio moving forward.
Expect the changelog to reflect only core changes. This announcement is about the status: Volumio Bookworm Beta is no longer experimental. It is now pre-release quality and ready for your help in testing, validating, and refining every edge case.
Let’s make this the smoothest transition Volumio has ever seen.
Kind Regards,
The mouseover does not show the correct prompt. Here is the log http://logs.volumio.org/volumio/CE00y17.html
When clicking on a suggested album, I get an error message. The log is here http://logs.volumio.org/volumio/7jIa6L6.html