Does the issue happen with local library music, streaming service music, or both?
· *Only streaming* music is affected.
Please select the streaming service(s) with which you're encountering playback problems.
· TIDAL
Have you tried logging out and back in again to your streaming service in Roon Settings?
· Logging out and back in had no impact, the issue remains
Do you have an approximate timestamp of when the issue last occurred?
· 12/20 20:35:25 Trace: [TSVEGA] [Lossless, 24/192 TIDAL FLAC => 24/192] [PLAYING @ 0:00] XYZ - Hiromi 12/20 20:35:25 Debug: [prebuffer] sleeping in read -- this isn't good 12/20 20:35:26 Warn: FTMSI-B-OE ti/0BCFEFDB: poor connection kbps:426.0 (min:3968.0) 12/20 20:35:27 Debug: [prebuffer] sleeping in read -- this isn't good
What are the make and model of the affected audio device(s) and the connection type?
· AURALIC VEGA G2.2
Describe the issue
Recent days I bought a new pc and connect it to my local family network. So I decide to transfer roon server to this new pc, and old pc as remote app. But I found after I started to use new pc as ROON SERVER, playing tidle music always have problem. The music will be buffered a bit, but each track only play 5 to 6 seconds and will be skipped. And also, before each track playing, it will wait at "00:00" for a long time.
Also in the log, you always seeing: 12/20 20:35:25 Debug: [prebuffer] sleeping in read -- this isn't good 12/20 20:35:26 Warn: FTMSI-B-OE ti/0BCFEFDB: poor connection kbps:426.0 (min:3968.0) 12/20 20:35:27 Debug: [prebuffer] sleeping in read -- this isn't good
If I switched back to my old pc, everything going well. And both pc area linked by the same router and in the same local network.
Describe your network setup
Normal local network but pluging all my two pc into ASUS RT-AC88U, not wifi.
Thank you for the detailed report and for including the relevant log excerpts — they’re very helpful.
The messages below indicate that the Roon Server on the new PC is unable to maintain sufficient throughput to TIDAL’s streaming servers:
Debug: [prebuffer] sleeping in read -- this isn't good
Warn: FTMSI-B-OE ti/0BCFEFDB: poor connection kbps:426.0 (min:3968.0)
Since playback works correctly when you switch back to the old PC while using the same router and wired network, this points to a difference in how the new PC is resolving or reaching TIDAL’s CDN endpoints.
In practice, this is often related to DNS resolution, where different machines may be directed to different CDN nodes with very different performance characteristics.
Could you please confirm:
Is there any VPN, proxy, firewall, traffic-shaping, or security software installed or running on the new PC that was not present on the old one?
Are you using any custom DNS settings (system-wide or per-adapter) on the new PC, such as DNS from a VPN, Pi-hole, AdGuard, or a manual DNS override?
Does disabling any third-party security or network-filtering software on the new PC change the behavior?
These types of services can significantly reduce effective streaming throughput and would match the FTMSI-B warnings seen in your logs.
Once we confirm whether any of these differences exist, we can try to understand where the problem is.
Actually I’m using a VPN to be able to listen to TIDAL music through ROON. (Currently I’m living in China, and by default can’t stream the Tidal music, but I use VPN with JAPAN IP to be able to listen all the great music)
I tried your solution tonight, and transfer to new PC by set as ROON SERVER, before that, I changed my local DNS to 1.1.1.1 and 8.8.8.8, and connect my VPN. For now it’s working !!!
Great thanks and I’ll observe it for the coming several days and let you know the result. Hope it’s stable, and I don’t need to switch to my old pc for ROON SERVER. Also if you have other good suggestions, please also teach me.
Really really thanks for you help, and can’t live with out ROON and MUSIC. !!!
We’re glad to hear changing the DNS service has resolved the problem for now. I recommend creating a post in Tinkering to see what other users with the same VPN have configured long-term. Posts in the Support section eventually close once a solution has been posted.