Roon Core Machine
Windows 10, latest updates
Networking Gear & Setup Details
Standard Ethernet, mainboard
Connected Audio Devices
DAC, USB from mainboard MSI
Number of Tracks in Library
Description of Issue
Any music played with Tidal is causing leaps and glitches in the replay. No single album can be played without this challlenge. Detail: For example a song with 4:00 playtime, is interrupted after 20 seconds, jumps to 25 seconds and continues to play, then after 1:20 the song is interrupted again, jumps to 1:27 and continues to play. This is very annoying since the same song played via Tidal directly is not experiencing this problem. Can you pls. investigate and get a fix for Roon release asap. This behavious started with release 918 is is still there. Thx.
Thanks for taking the time to write in and allow us the chance to help! My apologies for the delayed response and for your wait. We’ve made some recent changes to the support team structure and some reports have experienced a longer response time than usual. I’m sorry to hear you’re running into such frustrating playback issues with Tidal through your Roon account.
Since some time has passed I wanted to touch base to get your current status. If you’re still experiencing this problem, are you able to provide more specific details about your network setup and how your devices are connected to both the internet, as well as each other? Is your Roon Core hardwired?
Also, if you are able to update your Roon to the latest build 952, that might help clear up your playback issues!
We’ll be watching for your reply and get back in touch as quickly as we can. Thanks!
thanks for coming back to the reported issue - even if 1 month later. I did have a hard time with Roon and Tidal early this month. The release 943 later in May helped and since then the music is acting and playing as used to. This ticket can be closed for now.
I understand the reorg of your support team, nonetheless a short note to the user and sharing some information would have been good. 30 days response time, hmmm. Anyway thanks for coming back to the issue.
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.