What kind of performance/speed issue are you experiencing?
· The app takes a long time to respond to commands
Please try to reboot your Roon Server
· No, the issue is still the same even immediately after a reboot
Please try to reboot your networking gear (Router/Switches/etc.)
· No, the issue is still the same even after a reboot
Is there any change in behavior if you try to navigate to Roon Settings -> Library and set both Background and On-Demand Audio Analysis to Throttled or Off?
· No, the issue is still the same
Does the issue happen on multiple Roon Remotes (controllers) or just one?
· I only have one Roon remote to test with
Please try to restart your Roon Remote (controller) app
· No, the issue is still the same even after a restart
What is the operating system of your Roon Remote (controller)?
· Android
Reinstall Mobile Roon Remote App
· No, I am still having the issue even after reinstalling
Router Domain Name System (DNS) change
· I don't know how to do this
What is the operating system of your Roon Server host machine?
· Linux Server (Ubuntu, Fedora, ArchLinux...)
Timestamp of issue occurrences
· 10 april at 10.30 am
Describe the issue
Roon runs but only plays for two sek. When i start playback i can stop via the pause button, and there is no sound. dac is klickking (t+a dac 200) when skipping, but no sound
Describe your network setup
router connected to ubuntu/ linux and connected to ropieee roon endpiont.
We were able to review the diagnostics report from your machine and could have spotted that Roon unsuccessfully tries to connect to your Ropiee endpoint to port 0.
It usually means that initial handshake has failed.
please try to reboot the Ropiee, make sure that all updates are installed and Roon Bridge is running on Ropiee normally.
Also, please make sure that your Roon Installation is not Running in Docker and if your Ropiee has private IP address please reset it to DHCP.
This thread will shortly auto-close without any further responses. Please reach out if you’re still encountering this issue and we’ll investigate logs to pinpoint the event. If you can, share the name of a track that dropped out to help us identify the interruption in logs.
Whenever the issue occurs again, simply reply to this thread with the name of the track, the date, and the local time the dropout happened. Once we have those specific details, we can pull your diagnostics and pinpoint exactly where the stream is failing.
Take your time, and we will be standing by whenever you are ready!
Just checking in on this. Were you able to reproduce the issue? If so please reply with the track name, the date, and the local time when the dropout happened, so we can pull the right diagnostics and trace where the stream is breaking. If you have those details, send them over when you can, and we’ll take a look, thanks.