Hello Roon Support, what do I need to do to get the Tidal streaming again after over a week?
Where is the team? What is the contribution of all the others, QA team, developer, and senior staff?
To be clear, our whole team does spend time here on Community, but support issue responses are typically handled by one of our specialists. The rest of our team does contribute ideas for troubleshooting and weighs in on possible solutions. Having our discussion here allows for this to work. Weâve had a number of members of the team monitoring and discussing your issue here.
In most cases like what youâre seeing here there is a networking issue at play that is causing the behavior youâre seeing. This type of issue isnât something that is widespread and affecting all customers, so we need to understand what about your environment is causing this to occur.
A good test might be to connect your Core machine vis hotspot or USB tethering to a mobile network â when you do this, is there any change? These types of networks arenât good for long-term use, but itâs a quick way to test a completely different network.
Very busy this week. Any thing else I can try on the weekend, when I have time?
Also: The core runs on a work station without WiFi in a different part of the building than the Devialet. Can you suggest a way to do your test in such a setup?
Hello @Robert_Sonderegger,
What youâre experiencing is consistent with networking issues weâve seen in the past, simplifying the network helps rule out a good number of other possible issues. So letâs connect the devialet and the core directly to the router via Ethernet and see if the issue persists. Once we do that, we can expand to your other devices until we start seeing the issue again.
Great news: After two updates to Roon wiithin 72 hours (!) that both addressed problems with Tidal (Build 536: âTIDAL login is more reliable, even when weâre unable to communicate with TIDALâ and 537 âImprovements to TIDAL login expirationâ) I have been streaming from Tidal again without any problems.
And just for the record and future issues:
The network was NOT the problem. All the hard- and software components of the wired Ethernet network were unchanged before, during and after the resolution through the Roon software update. All the above mentioned components work perfectly with Roon.
What the software engineers see as a problem
in reality looks to be a typical software problem consistent with constantly changing software at Roon communicating with an equally changing software at Tidal. Both of which are probably based on a software stack that is nowhere near as tried and tested as Ethernet technology.
On another positive note, the Auto Sleep feature is very cool and works well - nicely done!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.