David, it only affects earlier products using that particular streaming engine. Current platform products are unaffected.
It appears that Tidal seem to have changed something with the log-in that stops the earlier platform from working properly. Steve H said he was trying to contact Tidal engineering last night to let let them know.
Hi there, Just to top up what @Richard.Dane has said, It would appear that a recent and unannounced Tidal API update has created connection issues for certain older Naim products. I appreciate how frustrating this is but currently a fix is out of our hands I’m afraid. We’re pursuing Tidal to get them to take some remedial action as soon as possible.
Are there legal agreements in that Tidal and such cannot make modifications rendering a Naim product feature unusable when you made Tidal part of a product when selling it? I mean, can we potentially lose Tidal if they don’t want to fix this and Naim cannot release an update solving it on their side?
A point I have made on the 272 thread (though I love my 272) only to get a couple of zingy replies. Not relating to 272 only, but directed at all streaming tech. Redundant and unusable software is a great way to get you to replace hardware…
A few weeks ago a message popped up on my Squeezebox Touch, advising in the near future the SBT Tidal authenification (???) would no longer work. When it stopped working I was advised to log out of Tidal in the Logitech server and log back in again using the Logitech server.
Sorted in a few minutes.
Maybe a similar thing has happened to Naim equipment.