I was wondering whether this issue is in the queue.
5 posts were merged into an existing topic: Audio drop out on the Volumio App./SMSL N100
Iāll start with the silliest problems that havenāt been solved, such as the elapsed time indicator while listening to web radio. Iāve been told that it depends on the audio streams, obviously all of them. I insist that it would be simpler to start the timer every time you change stations, pause it, and reset it when stopped. Isnāt that simpler and more elegant than dragging around something that doesnāt work?
I suggest fixing Jazz24 which now transmits in AAC at 256 kbps:
https://knkx-live-a.edge.audiocdn.com/6285_256k
Finally I tried swapping for a long time and I think /bin/dynswap.sh might work fine like this too:
if [[ "${RAMSIZE}" -le 256422 ]] && [[ ${SWAPDEVS} -le 1 ]]; then
echo "256 MB or less RAM Detected, need to enable swap"
[[ -d ${SWAPDIR} ]] || mkdir -m 700 ${SWAPDIR}
mount -L volumio_data ${SWAPDIR}
if [ ! -e ${SWAPFILE} ]; then
echo "No Swapfile present, creating it..."
fallocate -l 256M ${SWAPFILE}
echo "Securing Swap permissions"
chown root:root ${SWAPFILE}
chmod 0600 ${SWAPFILE}
echo "Preparing SwapFile"
mkswap ${SWAPFILE}
fi
echo "Enabling Swap"
swapon ${SWAPFILE}
echo "Setting swappiness to 40"
sysctl vm.swappiness=40
fi
Hey @pjorgenunes,
Volumio 4 (Bookworm-based) currently covers Raspberry Pi and x86_64. Additional platforms are planned, and this includes the ASUS Tinker Board used in Primo V1. While it is not available yet in the Beta builds, the intention is to provide upgrade support once the porting work is complete.
Kind Regards,
1 Like
Hey @jacobacci,
Just to clarify your latest message - are you asking whether the DLNA playlist metadata issue (with *20 in filenames) is currently being tracked for resolution?
If so, yes, weāve reviewed your reference to the older thread, and the behavior youāre observing still holds: Volumio displays the encoded filename (e.g. *20 for spaces) when queuing tracks via DLNA/UPnP, and only updates to proper metadata after playback starts. This is a known limitation of how DLNA items are queued - metadata is not fully resolved at queue time.
To move this forward, weād need to switch over to Bookworm first, then evaluate how metadata is handled inside upnpcli and whether a change in queue injection logic could trigger early tag resolution. Itās not forgotten, but itās also not trivial to fix, as it sits in between DLNA behavior and MPDās current limitations.
Let us know if you were referring to something else.
Kind Regards,
1 Like
Hey @Celona,
On the elapsed time indicator for web radio: this is not a simple cosmetic fix. Most radio streams do not expose usable duration metadata, so MPD cannot advance time reliably. Forcing a local timer would create inconsistency between radio and all other sources, since the value would not match what MPD reports internally. This is why it has not been patched in the way you suggest.
Regarding your proposed change to dynswap.sh: the original threshold was deliberately set at 512 MB to cover the oldest and smallest memory boards Volumio ever supported, such as Raspberry Pi Model B (256 MB), early Pi Zero, Orange Pi Zero (256 MB), NanoPi Neo (256 MB), and some BananaPi variants. Those boards cannot survive heavier operations without swap. On devices with 512 MB or more, the system is expected to cope without swap being forced.
For Bookworm, development focuses on Pi 2 and newer. Armv6 devices like the early Pi and Pi Zero are no longer in the mainstream path. If Bookworm ever runs there, it will be a community backport. Any changes to dynswap thresholds would need to consider this historical context, device coverage, and impact across the full matrix of supported boards.
Kind Regards,
It seems to me that the conditions in the script correspond to what you say, we need the swap only for those Raspberry Pi models on which Volumio 4 will not run because they have no 64-bit SoC.
I apologize for the error, today I have Trixie in mind (Volumio 5), but the script I proposed creates the swap for models with 256 MB RAM.
Maybe there is not enough on demand or interest to make Orange Pi Zero work, I report it because I remember reading it in other sections of the forum.
Hey @Celona,
No worries. Your script clearly targets 256 MB RAM devices, which matches the handful of legacy SBCs you had in mind.
Current picture:
- Volumio 4 Bookworm targets Pi 2 and newer with 32-bit userspace. Those boards all have 1 GB or more, so the legacy dynswap guard effectively never triggers in mainstream builds.
- Interest in keeping 256 MB class boards alive, like Orange Pi Zero 256 MB or early Pi 1/Zero, is low and any Bookworm support there would be community-driven, not an official target.
About your proposal:
-
For a community backport on 256 MB boards, enabling a 256 MB swapfile and vm.swappiness=40 is reasonable.
-
Consider flash wear on SD; keep swap size minimal and avoid swappiness higher than 40.
Given the official scope, we will keep the historical 512 MB threshold in core for now, but it will not affect supported Pi boards. If there is concrete demand and test data for Orange Pi Zero or similar, we can revisit in a community backport context.
Kind Regards,
Thanks Nerd,
I have no interest in worrying about models with less than 512 MB of RAM, I modified the script only to not create the Swap file on the micro SD card.
Initially it seemed to me that it was necessary with 512 MB of RAM, today I am more inclined to think the opposite.
I am also convinced that the Raspberry Pi are the best choice for the user who want to try Volumio, they do not cost a fortune and you also pay for software support that has a higher value than the alternatives can save us economically.
For OEMs it may make more sense to scale costs to maintain profits, component prices are destined to rise, but a different strategy is needed, today connectors cost more than the DRAM that for this type of product will be integrated into the SoC.
And so if hobbyists can want a new RP3 chip with 1 GB of RAM (or rather a new Pi Zero 3 W) that could be the only new cheap Raspberry product by the end of the year, for those who know how to tinker with the welder it might be better not to change the low-obsolescence parts every time, which are now the outline of the chips.
Raspberry Piās industrial customers now dictate the companyās choices and the new CM0, which is only sold directly, in my opinion offers new opportunities to seize, starting from 512 MB of RAM (which will double with the new RP3).
Honestly you donāt have to deceive us that we can be fine with 256 kB of RAM, the new software must seize the opportunities that the hardware on the market can offer, and in this case the possibility of having for $ 18, practically at the same price as the Raspberry Pi Zero 2 W with welded GPIO, the same hardware with even an 8 GB eMMC, could interest some OEMs and would open a market aimed at a wider audience, the one in the SD would only need the songs, the one who just wants to know where is the play button or the stop.
In my opinion, a similar solution allows a greater product differentiation, e.g. also in the offer of different power supplies, linear or switching, of different converters, and combined with a commercial differentiation, between bundles with one or more premium options and different OEMs can offer everyone what they deem necessary and grow a flourishing ecosystem of solutions around Volumio, which will be able to integrate your existing offer in other segments, as SMSL has already tried to do, but with low investments for your partners.
And if Volumioās user base grows, spaces will open up for new services and also for the sale of songs that no one does anymore. This is what the new software should be for, and perhaps to give that prominence that the platforms are taking away from national broadcasters.
Appetite comes eating, and therefore to bring new users to the most value-added solutions, it may seem unintuitive, but you need a very economical product to enter the ecosystem and grow over time. Only we who enjoy putting the pieces together have this possibility, maybe there is space for cheap gadgets and therefore not in competition with the current offer.
To get back to where I started, do I serve you as a user who wants to stay with his 256 MB RAM SBC without a market? No and so you donāt have to want me like that, your customers all have a great passion, yes, bigger than the wallet and without this push they would never have arrived here, today we all have a cell phone that plays music, but we want more. For example?
I donāt want to be profiled and even more I donāt want to be interrupted by advertising, pop-ups and any other technique to get my attention, and I donāt want to pay YouTube for this, and not even others, but Iām willing to spend to keep my local music at the highest quality and enjoy it. At this point a large SD already costs more than a cheap SBC.
Hey @Celona,
You make a very good point. This is the Bookworm Beta release thread, and the focus here has to stay on ironing out issues that directly affect the path to stable. Broader strategy topics such as OEM hardware choices, long-term Pi roadmaps, and ecosystem opportunities are important, but probably deserve a dedicated discussion where they can be explored without distracting from the Beta testing feedback loop.
If you want, we can spin off a thread specifically on hardware direction and OEM integration, while keeping this one tightly focused on Beta validation and getting the upcoming stable release honed in.
Kind Regards,
1 Like
Hi everyone,
Even though weāve been a bit quiet lately, a lot has been happening behind the scenes. We know many of you have been waiting for updates on the Bookworm release, and while we would have loved to move faster, a combination of hard-to-reproduce regressions, personal matters, and other priorities slowed things down.
That said, weāre excited to announce that we are finally ready to share the first Release Candidate (RC) of Bookworm!
Weāve spent quite some time chasing a tricky bug that isnāt fully solved yet, but overall weāre very happy with the current state of Bookworm. This RC marks the last step before the official release.
Whatās new
One notable change is in the way networking is handled:
- Only one network can be active at a time.
- If you connect via Ethernet, Wi-Fi (including hotspot mode) will be disabled.
Let us know if you find this too inconvenient or youāre fine with it
Why a Release Candidate?
Before the official release, we want to be 100% sure there are no major regressions. Thatās why weāre going through an RC phase rather than jumping straight to full release.
We also need to carefully manage the transition:
- OTA updates will be available.
- In some cases, a factory reset may be required.
- In certain situations, a full SD card rewrite might be necessary.
Weāll be gradually testing these scenarios throughout the RC period.
Thank you
Huge thanks to everyone who has contributed feedback and testing so far, and to our amazing mods team with a special shoutout to @nerd, the real driving force behind this effort.
We canāt wait to hear your feedback on the RC and get Bookworm over the finish line together!
5 Likes
The link to download the RC for Raspberry Pi does not work.
https://updates2.volumio.org/pi/volumio/4.025/Volumio-4.025-2025-09-24-pi.zip
http://logs.volumio.org/volumio/aRIpZ1L.html
Rpi 4
IQAudio DAC Pro
Openmediavault NAS on Rpi 4
OTA update from 4.024 to 4.025 went smoothly - all looking good 
OTA from 4.023 to 4.025 release candidate
Pi4B, SD boot, Topping D10S USB DAC
Pi is connected via wifi
Tested and working:
Tidal and Tidal Connect playback
Playing local files on SD and USB SSD
Web Radio
Play here
Multiroom
Good wifi strength and stability
Looking good!
Logs: http://logs.volumio.org/volumio/zn8HPdr.html
My second system:
OTA from 4.023 to 4.025 release candidate
Pi4B, SD boot, HDMI
Pi is connected via ethernet
Tested and working:
Tidal and Tidal Connect playback
Playback via Samba drive
Web Radio
Play here
Multiroom
Thank you very much, it looks great overall!
The OTA update worked without a hitch.
RPI 2, 3, 4, Allo BOSS, Allo DigiOne (& Signature), USB to DAC.
Local FLAC on NAS
Internet radio (SwissPop, SwissJazz, ā¦)
Qobuz
Qobuz Connect
Log
http://logs.volumio.org/volumio/O3wiL1m.html
The bug also exists in RC 4.025ā¦
3-dot context in tile view partially not correct
Great - Yes fine with Wi-Fi being disabled with LAN wired connectivity. Donāt want superfluous wireless activity, including Bluetooth, if not needed or wanted. Thanks.
1 Like
Tested with:
HW: x86 devices, rPi4, rPi5;
DACS: Hifiberry DAC2, Innomaker DAC Pro, Topping E50, E30II, DX3Pro+, Project Pre-box S2 Digital, iFI Zen DAC.
Premium Features: Tidal, Qobuz,
Plugins: Randomizer, Rotary Encoder, IR receiver, FusionDSP, Spotify
Mixers: HW, SW and None
Nothing strange encountered, seems stable to me.
2 Likes