Well, praise the Lord; my ND5SX and Tidal live to play together again another day. All good news. I agree, it would be good to know where the problem lay and how it was resolved.
I received this response from Tidal earlier today: “Since you are using TIDAL through the Naim app, unfortunately we are unable to access Third Party Interfaces and we are unable to assist, so please contact Naim Support so they can help you with this. Please note that we can offer support when it comes to the TIDAL application directly.”
So while audio Armageddon may have been averted temporarily, there is a feeling that we are living on borrowed time as with each revision (or upgrade as they like to call it) we get a step closer to our kit being rendered obsolete. If only because those helpful people at Naim suddenly find that there isn’t a quick fix to be done.
I think, for a service like Tidal, there are way to many customers on hardware that need FLAC 44.1 Khz and that wont change soon. They would simply remove themselves as such a large contender if they just drop this segment. IMO Audio Armageddon won’t be happening soon in terms of serving a consumable audio stream for older devices.
And as reported by @jmtennapel (I think, if I have misremembered the user my apologies to jm) above he found other manufacturers suffering, so it was hitting a larger number of users than we saw here. Most of whom would unsubscribe from Tidal if the service kept stuttering.
My update from Naim support: “ can confirm that Tidal is actively addressing the issue based on the latest update they provided. If you’re noticing a reduction in the problem, it a good indication of progress on Tidal’s part. However, I must emphasize that we haven’t received an official all-clear from them at this time. I will provide further updates once we receive confirmation that the bug has been resolved.”
I still have this problem, or have had for three to four months. I know my network connections are fine. It has never been stable. Nac 272, happy to listen to advice if it exists.
You get this if you have the app open on say a macbook and at the same time try to open it on a smartphone or vice versa. Are you sure you don’t have the app active on more than one device? That means closed and not minimised (the dot under the app in MacOS means it is just minimised, not closed)
Hi Blackbird… thanks for your reply. I only have my Naim app on one device, exactly where my screenshot originates from, i.e. my iPad. I don’t have the app installed on other devices. I also find it strange that I always get the message that there is another app open. There isn’t…
A former work colleague who despite working in digital for all his career is a complete luddite and despises the whole idea of streaming to the point of paranoia, what if Spotify or whoever switch it off? Well what if they don’t?!
But there is a point. Thankfully it seems Tidal have fixed this latest glitch but is it going to be the case that having spent day £20k on a Naim or whatever streamer suddenly Qobuz update their system such that it no longer works?
Not happened to me with Qobuz🤞🏽……one of the reasons i moved from Tidal, they have a track record of doing poor changes……the likes of Naim are the last to know.
As of 30 minutes ago, I’m still having this problem on my Uniti Star - I’ve no idea if it is classed as a ‘1st Gen’ or not :). I’ve done all the checks - including factory reset, wireless + hard wired, re loaded apps, new passwords, etc.etc. Still feeling pretty frustrated. Tidal works fine through bluetooth, of course.
I was also trying to listen the the new Chris Stapleton album on Friday evening (so a week ago) and had exactly the same issue with my NDX.
My guess is Tidal has done something that doesn’t agree with the Naim integration of the service. This has happened before, so hopefully Naim and Tidal are able to resolve the issue.
