All — I saw the request for some feedback on the various error messages users might see with TIDAL after the latest update (i.ebuild 310) and wanted to offer some insight.
As you may be aware, we have had mixed results reproducing this behavior in house, and some of the diagnostics and feedback we’ve gathered point to more than one underlying causes. Obviously, this complicates things, since we may in fact be looking at multiple causes which are all triggering the same symptoms.
We’ve been discussing how to proceed, and decided to release an update this week that takes into account some of these distinctions, triggering different error messages accordingly. So after updating to Build 310 the following messages will be displayed when there is an issue streaming TIDAL content:
-
“TIDAL media is loading slowly. This may indicate a networking or connectivity problem.”
-
“This track is not currently available from TIDAL.”
Going forward, everyone should confirm that their Core and all Remotes are running Build 310, and the next time you experience this issue, be sure to let us know exactly which error you are seeing.
We have collected a lot of information here, so knowing which error you are seeing will help us start to address underlying causes with more specificity.
Looking forward to the feedback everyone. Thanks for your help, and for your patience.
Many thanks!
-Eric