· Subject: Regression: Playback fails on Eversolo T8 after switching outputs (v2.58)
Roon Core Machine: Roon Optimized Core Kit (ROCK) running as Virtual Machine on Proxmox
Description of Issue: Since updating to version 2.58, I am experiencing a regression regarding the playback on my Eversolo T8.
Whenever I switch the output on the Eversolo T8, Roon is no longer able to start playback. This used to work perfectly fine in version 2.57.
The only way to restore functionality is a full reboot of either the Roon Server (ROCK) or the Eversolo T8 itself. Once rebooted, playback works until the next time the output is changed, at which point it breaks again.
Steps to Reproduce: - Start playback on Eversolo T8 (works initially after boot). - Change the output on the Eversolo T8. - Attempt to play a track in Roon. - Result: Playback fails to start
Thank you for the detailed report and for clearly outlining the steps to reproduce — that’s very helpful.
One important point to clarify first: running ROCK inside a virtual machine (Proxmox) is not a supported configuration. Because of this, we can’t reliably determine whether the behavior you’re seeing is caused by Roon itself or by the virtualization layer interacting with audio/network services.
To help us move forward, could you please do the following:
Temporarily run Roon Server on a supported setup (for example, ROCK installed directly on compatible hardware, or Roon Server on macOS / Windows / Linux).
Reproduce the same steps with the Eversolo T8:
Start playback
Switch the output on the T8
Attempt playback again
If the issue still occurs, please note the exact date and time (with timezone) when playback fails and let us know.
That timestamp will allow us to check the diagnostics and see what’s happening at the moment playback breaks.
Once we can confirm the behavior on a supported configuration, we’ll be in a much better position to investigate whether this is indeed a regression in 2.58.
Hi,
thank you for the clarification and the troubleshooting steps. I have some additional findings to share:
I have tested the Roon Server installation on Windows, and the problem does not occur there. Everything works as expected.
Unfortunately, I do not have access to any other Roon-compatible hardware to test a “bare metal” ROCK installation at this time.
I performed a rollback of my current ROCK installation to version 2.57, and the issue disappeared. The playback and output switching with the Eversolo T8 work perfectly on 2.57, which suggests the behavior is specific to the 2.58 update rather than the virtualization layer itself.
Given that it works on 2.57 but breaks on 2.58 within the same environment, I hope this helps narrow down the cause of the regression.
Thanks for letting us know your observations. Do you by any chance still have the old RoonServer logs from when the issue was happening? If you do, please upload them to the link below and let us know once uploaded.
I have the same problem on the eversolo dmp a6, it started since a recent update on the eversolo side. I think it is a firmware bug on their side. I also have to restart the eversolo after changing the input to internal player to get roon to play. Before the update it worked fine. When the input is already internal player when i turn on the dmp it works fine.
Hi,
in the meantime, I was able to test a Roon Server installation on a Debian VM running on the exact same Proxmox host.
Interestingly, I encountered the exact same issue as I did with the ROCK 2.58 installation.
I have uploaded the corresponding log file for this test as well, file name: RoonServer_log_Debian.txt
I hope these logs provide more insight into what changed in the 2.58 update.
Issue starting at 03:49 p.m. CET.
I wanted to inform you that the issue has been identified and is currently under investigation by our R&D team.
You can follow the progress and updates in this thread.
Usually, we merge similar topics; however, since this specific thread contains diagnostic details that might be confusing to others, we’ve decided to keep it separate. Please feel free to post in the main thread mentioned above or simply follow it for the final resolution.
We apologize for the inconvenience caused and appreciate your patience.
Hello,
thank you for your efforts and for looking into this.
I have one final question to clarify: Is running Roon Server within a Debian VM on a Proxmox host officially supported? I initially chose the ROCK installation primarily for convenience, but I would like to know if the Debian VM setup is considered a supported configuration by Roon.
To clarify the support status: while Roon Server can certainly run within a virtualized environment like a Debian VM on Proxmox, it is not an officially supported configuration. Our technical support team is generally unable to troubleshoot issues specific to the virtualization layer; however, in this particular case, we have confirmed that the behavior is a known regression affecting multiple users across various platforms.
Since this has been identified as a specific bug that our R&D team is currently working on, we are going to close this thread to consolidate our tracking.
We recommend that both of you visit the main tracking thread linked below and post a quick message there (or simply “Watch” the topic) to ensure you receive automatic notifications as soon as a fix or workaround is released: