I have spit your post into it’s own thread since you mention that these issues are occurring not only on Qobuz content. While it’s originally formatted for streaming services, can you please take a look at the relevant questions here (Issues w Qobuz + TIDAL streaming in Roon 1.7) and let me know your feedback?
What are the specs of your Core machine
What endpoints are affected? If you’re on Windows or Mac does this happen with the system output?
What is the topology of your network? How is your Core connected? How are your affected endpoints connected? Is everything WiFi or ethernet?
What is the speed of your internet connection?
Does this happen with all content, only high res, etc?
What exactly happens when playback fails? Does Roon fail to complete the song? Does the next song always work?
Does logging in and out of Qobuz/TIDAL have any effect?
The affected endpoint is connected via ethernet (same switch as roon core)
ADSL 80/20 (down/up)
The last couple of weeks I am working through my library because I’m currently filling various playslists. That’s the reason why I’m experiencing the behaviour below quite often recently. I know it differs from normal listening behaviour but it happens so often that I thought it would be good to point it out.
I listen to an album. I am listening to the first few tracks and I’m intentionally skipping (with the “next” button) one or two tracks. Sometimes I am moving to two or three positions within the track using the waveform before pressing the “next” button).
Then it happens that the next song is starting but after a few seconds it stops suddenly (important: the song is not the last song of the album).
After that there is a random new song played. The new song is either from my local library or hosted by Qobuz. It looks like the Roon Radio routine starts at this point although neither the previous song nor the previous album has come to an end.
Apologies for the delay in getting back to you here due to the holiday period. I appreciate all the information you have provided above, you mentioned that this only occurs on the Windows 10 PC with the Traktor Kontrol? Have you had a chance to test our “System Output”, does this behave in the same way as the Traktor zone?
Have you given this a try yet? Has this changed anything with regard to the Qobuz behavior?
the problem didn’t reappear so far. I am was running on System Output (without DSP effects) for some time and then switched back to the Traktor ASIO drivers (without DSP effects). The skipping issues didn’t come back… thanks for your help anyway.
Glad to hear the skipping behavior has subsided. Do feel free to send me a message or open another thread and reference this one if it returns, will mark this thread as [solved] in the meantime. Thanks!