Public Alpha Test: Audio Without Compromise - Volumio on Bookworm Begins

Hey @Celona,

Thank you for taking the time to test and share your detailed feedback.

First of all, we appreciate your positive comments about version 0.060 and the constructive spirit in highlighting areas for improvement. Your engagement really helps drive the quality forward.

Regarding the Webradio time counter:

  • We are aware the counter stops after a few seconds on Webradio streams.
  • It is a known minor UI limitation related to unsynchronized streams and not a playback defect.
  • We will review whether to improve its behavior or minimize its visibility when streaming webradios, without disrupting the general UI flow.

About the Raspberry Pi Zero W and memory concerns:

  • You are right that 512MB RAM is becoming a tight fit for Bookworm-based systems. Bookworm brings heavier kernel and userland overhead compared to Buster.
  • However, looking carefully at the memory usage screenshots you posted, they come from different hardware:
    • One shows a 512MB RAM device (likely a real Pi Zero W).
    • The other shows a 2GB RAM system (likely a Pi 4 or similar board).
  • Therefore, it is not a direct footprint comparison between the same device before and after Bookworm migration.

I agree that Pi Zero W is increasingly hardware-limited for future Volumio versions. Newer hardware like the anticipated Pi Zero 3W, if it indeed brings 1GB RAM, will greatly improve the situation.

Regarding your suggestion about moving directly to Debian Trixie and 64-bit migration:

  • It is a valid long-term strategic view.
  • However, completing the Bookworm migration first is essential, both to stabilize the current user base and to avoid skipping an entire Debian generation without proper validation.
  • Once Bookworm is fully stabilized and released, we will reassess platform roadmaps, including Trixie and 64-bit expansion, based on hardware and community evolution.

Finally, to make sure we have precise data, we will schedule controlled memory footprint comparisons across multiple reference SBCs in our internal lab. This will ensure we have a clear and fair baseline for performance discussions.

Thank you again for your thoughtful feedback and your continued contributions to the project.

Kind Regards,