Tidal suggests changing my network settings to use Google Public DNS

Is the NAC272 on wifi or wired? I used to have the same issue while my streamer was on wifi, now it is rock solid after I hard wired my streamer to a switch.

However, I think it is no harm to try Google public DNS, it is much better than some DNS servers provided by some ISPs anyway.

Btw, I think it does not matter if some of your devices using the Google public DNS and some not.

Thanks for that. The NAC is connected via LAN running around 70mps download and 40mps upload. Thus my original complaint to Tidal; "why is this happening?"

Recently tried Spotify and realised a huge difference (for the better) in the user experience. Barely perceptible drop in audio quality at half the monthly fee. No dropouts. Instant response.

Decision time.

Not audio related, but I stream NHL coverage to my TV via an Apple TV. I'd been having trouble with this when all other streaming services (iPlayer) worked fine. The NHL support team also suggested this change to the Google DNS. I did it, and it did seem to improve things. I can't rule out any improvements they may have made to their own servers etc.  Anyway, it should be a simple thing to try, and easy to reset if it has no impact.

(This was a setting edit on my router.)

I had to change my Sony Blue-Ray player from my ISP's DNS to the Google Public DNS to get that to connect to it's update server.  Strange things happen sometimes.

Thanks for this. I guess there's no harm giving it a try despite the futility some suggest. Not really sure what numbers to change as the Google DNS numbers do not look the same format as the ones on my DAC272. Hmmm. 

Use the Google IPv4 number i.e. 8.8.8.8

The only way I can see that this is going to make a difference I suggest is if Tidal are changing the resolving address of the internal servers cloud servers due to load managaement, and they feel the Google DNS is going to be on average updated quicker than your ISP or alternate DNS... this really feels clutching at straws and any gain is only going to be transient at best.. as I have said before most of the issue is the interaction of network / TCP latency with the Naim streamer... and the Classic series streamers appear rather sensitive to latency.

Silverguy, if you want to try this you should set up the Google DNS address in your router for best performance, and also allows the correct use of DHCP given values on your home network... and it allows your router to act as as a DNS cache which is what it should be doing. BTW I don't think it will provide much benefit at all, but if not done correctly could provide performance reduction on your home network, streamer experience. 

Thanks Simon. Without the benefit of the technical know-how you obviously have, my sense has always been that this has more to do with Tidal allocating resources to priority markets. I'm in Thailand and I suspect one of a few Tidal subscribers. Loathe to make changes to the router without someone more competent here to guide me (and I'm Mac-based whereas most of the router interfaces seem to be Windows only).

Possibly the simplest solution is to move to Spotify which only just launched in Thailand a few weeks back. I've been conducting A/B comparisons and unless I'm sitting front, centre and concentrating on the fidelity, it's hard to discern the difference.

Also, much better user experience and zero dropouts with Spotify so far.

Thanks again.

Personally, I think there is no harm in trying the Google DNS solution as it may pick out the most optimal Tidal server with the shortest path to your home, thus mitigating the issue of network latency and restransmission.

Silverguy posted:

I suffer frequent buffering issues when streaming Tidal on my NAC272 streamer.

I contacted the Tidal folks and they recommended; "Based on the information you provided, this issue may be resolved by making some adjustments to your device in question.
Please change the DNS settings on your device by following this guide:
https://developers.google.com/...dns/docs/using?hl=en

Does anyone have experience with this? Is it indeed a solution and will it affect the ability for me to control the streamer using the app - which will presumably remain connected via the  normal ISP DNS settings via my WiFi.

Thoughts appreciated.

 

 

I switched to google DNS last year without any problems. Change the setting on your router.