Bluesound Node 2 With Tidal, Sound Delay
Answered
Hi!
I have a Node 2 that is connected to a Denon AV receiver via RCA.
When Im using the Bluos app, it all works without any problems, but if I use the Tidal app on my phone, or the Tidal software on my computer....there is a 2 second delay.
If I start a new song, it's all silence for the first 2-3 seconds, and it's the same if I skip forward in a song. And the same thing if I adjust the volume....it doesn't change right away....it takes 2-3 seconds.
I don't know if the fault lies in the Node or with the Tidal software.....but If anybody knows how to fix this, I would love to know!
Thank You!
/Niklas
-
Official comment
The lag you are seeing is not unusual if you are using a third-party app on a phone or tablet with Bluetooth and is not uncommon. Note you will not get MQA output when using Bluetooth as you are limited to 16/44 (CD Quality). Use the integrated TIDAL solution in the BluOS App for not only 0 delay but also the best audio quality.
-
Hi Tony!
Im not using Bluetooth, Im using ethernet cable direct into the Node.
The only wireless connection is of course wifi from the phone to the router.
But from the computer it's all wired, and it still delays.
I also tried Roon, and there is no delay there either.....so It has to have something to do with Tidal.
Maybe I should try contacting them......but I don't there is anything to do about it...
1 -
i realize this is a complete shot in the dark, but in case you care... I had a 10 sec delay before each Tidal song when using Tidal on my PC. i watched the network traffic (imma geek) and found that my ISP DNS server was the source of my delays. I changed my DNS server to 1.1.1.1 (cloudflare, trustworthy and very fast DNS resolutions) and now i have no more delays when playing from Tidal. [shrug] i don't know exactly why, but it worked.
1 -
Hi RodgerK
This is, in fact, one of our Support Crew's tricks as well - that or Google at 8.8.8.8 works well too.
1 -
I had the same issue. Completely DNS related. This was my recap;
I would love to provide you with a step-by-step solution, but there isn’t one available. What I do can tell you is how I determined the real issue and how I resolved it. I guess that you will conclude that my problem was very specific to my infrastructure...So the problem was that my node2 was terribly slow with Tidal. It took up to 30 seconds to start playing. The odd thing was, that every other device (whether wired or wireless) in my network did not have any issues. I concluded that it had to be a misconfiguration or some hardware fault of my node2. With diagnostic info I determined that there was some packet loss. So I bought a new gigabit switch (a cisco) to replace my netgear one. Packet loss resolved. But nothing happened with Tidal performance: still awfully slow.I actually gave up on Tidal at that point: when it eventually played, it played beautifully.A week ago, a new firmware was available for my router. I decided to update it (an Asus RT-N66U), and did a quick scan of my settings. And then I saw that the primary DNS of my DHCP pool was manually set to my internet router (which was actually set to be a bridge). My internet router had been replaced a couple of months ago to accommodate the new subscription (300/30mbit). And I don’t know why, but then I started thinking: perhaps my new internet router isn’t relaying the DNS requests any more, or in a way that my node2 could not comprehend.So: I just replaced the primary DNS (192.168.178.1, the internal IP of my internet router) to the DNS address of my provider. I restarted the node2… and hey presto, it worked! Tidal performance was absolutely fine (<1 sec for each query) and blazing fast compared to before.TL;DR: replaced the primary DNS setting in my router’s DHCP server settings from an unresponsive internal DNS to an external DNS address. The node2 DNS timeout grace is too long.0
Please sign in to leave a comment.
Comments
5 comments