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

Volumio Development Volumio Beta Testing
, ,
449

[Poll 1] Do You Actually Read the Beta Intro, Changelog, or Bug Report Guide?

We’re curious - before diving into a Beta update or reporting a bug, do you:

  • Read the full Beta intro thread, changelog, and how to report bugs
  • Skim the post and jump straight to the download link
  • Assume it’s like the last Beta and just update
  • Never knew there was a guide or changelog
  • What’s a Beta?
0 voters

This poll helps us understand if the time spent writing those posts is time well spent - or if we should start tattooing them onto the UI.

Kind Regards,

450

[Poll 2] Do You Understand That Buster and Bookworm Share the Same Backend?

Here’s a technical reality check: the Volumio backend is shared across Buster and Bookworm. That means bugs in one… often follow you like a loyal pet to the other.

Do you:

  • Fully understand the backend is shared
  • Suspected it, but never sure
  • Thought Bookworm magically fixed everything
  • Wait, what’s a backend?
0 voters

This helps us separate real Bookworm issues from the classic “it was broken before but I never mentioned it” surprises.

Kind Regards,

451

[Poll 3] Do You Know That OS Beta and Plugins Beta Have Separate Threads?

Yes, we know it’s a lot of threads. But to keep things organized, OS Beta and Plugins Beta each have their own dedicated community threads.

Do you:

  • Follow both threads and know which one to post in
  • Know they’re separate, but forget which is which
  • Just post in whichever one is open in a tab
  • Didn’t realize there were two threads
  • I report bugs by shouting at my speakers
0 voters

We’re trying to keep chaos at bay with threads like these - help us out by answering honestly.

Kind Regards,

452

[Poll 4] What Do You Expect from Community Beta Contributors?

The Volumio Beta - both OS and Plugins - is kept alive by volunteers with support from staff. Not full-time developers. Just community members spending their own time to test, fix, document, and occasionally repeat “please post logs” for the 400th time.

And yet… some users still expect white-glove service with a 24-hour SLA.

So tell us honestly - what do you expect from community Beta contributors?

  • Casual testing and bug triage - anything more is a bonus
  • Help with showstopper issues, not your personal wishlist
  • Occasional updates and guidance - no pressure
  • Daily fixes, polished features, and concierge-level support
  • Wait… this isn’t a paid team?
0 voters

This poll helps us understand if expectations match reality - or if we need to pin this to every thread from now on.

Kind Regards,

453

Freshly installed 4.020 on a Fujitsu Futro S920 AMD ThinClient w/ 8GB RAM on a mSATA SSD 8GB via USB stick. The audio interface is a Meridian Explorer 2.
For testing I created a new MyVolumio Account w/ Premium plan and a new Qobuz account w/ Studio plan. Right now I am on Tidal and an old Virtuoso plan. Testing Qobuz connect was since release on my whichlist.
For the account registation, etc. I got beamed in a browser world and was not able to get out of it. I shurely made a mistake, but still it was impossible for me. After regulary push button poweroff and on every thing was fine.
One small thing I found for Qobuz connect: it pauses in volumio UI but does not start. I have to go for the app to start again.

Tidal connect reports a Server error in the Windows App, while I get this popup in UI:

grafik

Volumio3 does work at the same time.

454

Tidal connect:
Please read this topic, before replying that something doesn’t work, please.

Qobuz Connect
Are you running the latest version of the Qobuz app (phone or your PC)?

455

With Debian Bookworm, will DisplayLink drivers be available for an extra option for display?

456

Hey @RedEyeNinja,

Good question. As of Debian Bookworm (which Volumio 4.x is based on), DisplayLink support is possible, but it depends on a few factors.

Current status of DisplayLink on Debian Bookworm

  1. Open Source option: evdi + displaylink-driver

    • DisplayLink devices (USB to HDMI/DVI adapters) require the EVDI kernel module.
    • As of Bookworm (kernel 6.1+ or in our case 6.12.x), EVDI must be recompiled for the exact kernel version in use.
    • The proprietary DisplayLink Manager from Synaptics requires EVDI, which is not included in Debian by default.

  2. Driver availability

  3. Compatibility with Volumio

    • Volumio does not include EVDI or DisplayLink stack by default.

    • DisplayLink support is not tested in the standard image.

    • Manual integration is required, including:

      • Installing headers
      • Patching and compiling EVDI
      • Inserting udev and X11 (or Chromium kiosk) rules

Conclusion

Yes, DisplayLink can work under Debian Bookworm, but:

  • It is not plug-and-play in Volumio.
  • It will require custom kernel module builds for EVDI matched to Volumio’s 6.12.x kernel.
  • Official support in Volumio is not guaranteed at this time.

Kind Regards,

1 Like
457

Hard to say if JS 8.0.0-b009 is the latest version. At least it’s not offering an update, as it usually does.

458

image
image906×193 7.21 KB

image
image837×177 6.73 KB

Tested Both Qobuz as Qobuz Beta, but I am unable to reproduce this error. Only thing I can think of if that you have a Qobuz Solo subscription and trying to play on 2 devices?
Also very unclear what happened here as the process is pretty stable and straight forward.

Please post a full log, when this happens.

459

I guess it is when done from the local UI screen. If you are redirected to a connexion page, no way to return to Volumio.

460

Good afternoon!

Installed 4.020 via OTA - went without problems.

Capability of reboot from GUI is still missing.
This is still unfortunately true for reboot commands from terminal as well- so reboot is currently not possible - hard reset (power off) is neccessary.

BT remote is connected and initially doesn’t work correctly.
Have now installed BluetoothRemotePlugin and rescanned. GUI was for some reason tricky - it was not easily possible to get the found device selected but after several approaches some may strange combination kept the device selected in the drop-down and so a saving could be performed.
BT remote still doesn’t work properly, Volume up/down and skip back were missing as before.
The triggerhappy config file was moved or reflected to the externally visible INTERNAL storage Portion - nice idea.
Doesn’t work either initially - file belongs to root. Changing this it was possible to add the missing entries
KEY_VOLUMEUP 1 volumio volume plus
KEY_VOLUMEDOWN 1 volumio volume minus
KEY_PREVIOUSSONG 1 volumio previous
Restarting triggerhappy (possible from plugin-settings - great idea, as well!) and voilà: BT remote now works fine.
Thanks to @balbuze!

The poblem with one of the rotary encoders disappeared, both Rotary Encoders are doing their respective work.

(HW) Config:

Pi5,
Raspi 2 Display (DSI),
Two rotary encoders on several GPIOs - both working fine.

Working BT remote :slight_smile:

Testing:

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

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

Many, many thanks for your effort. The result is awesome!
Warmest regards,
Ralf

1 Like
461

Here you get a log for pause on volumio, try to resume and finally resume with Qobuz app.

ad219ac1e672cae19d27ba3d0e706be0

Yes, I have a Qobuz Solo subscription, but no I only run it on a single device. Actually on a different Windows 11 system and which was update from 7… to 8.0.0-b009.

462

Thanks for clearification. Yes, cable connection to a monitor and keyboard/mouse connected. I understand, but still it’s not nice.

463

@DED

Hi Davide, can you take a look at the log, I don’t see any reason for the reported issue

464

Turns out the TIDAL issue was an incompatibility between libcurl and OpenSSL 1.1.1. Now we statically link a compatible version of libcurl. Next build should fix this. :wink:

6 Likes
465

Well done and great find.

466

Found an issue with Media servers.
For testing I’ve added 3 uPnP servers:
image

With 2 (NAS1 and Twonky) I receive errors when trying to browse the uPnP. It restarts and nag with regards to the rotary encoders???
image

LMS doesn’t crash, but I can’t play any track. But I can browse like crazy :slight_smile:

log:

467

Hi @hifiswede,

thanks for the workaround. Made it running, but: UPnP is not started and media server’s are not detected. Probably beacuse of delayed network startup. Thus waiting for a system solution.

468

Hello nerd
I just did a clean install of 4.020 and it works great.
The good news is that it created a hotspot , well two ? One with Volumio and the other with the expected Volumio-FBAF9 . The bad news I couldn’t log into either, so I reverted to wired ethernet.
Hardware is Pi2B with WiPi USB as before.
Best Regards

Here’s the log file reference http://logs.volumio.org/volumio/j267ELY.html