Our Tech Team has concluded their investigation into this matter and determined this is an issue through the device setup with Lenbrook and the way it's connecting back to your network. I was skeptical I'd use it much at all, but honestly it's a decent way to control the Node.Īt long last, i received an answer to my numerous emails to Tidal: I'm using that on the same exact laptop, and it sees the Node 100% of the time. According to the Tidal page of supported devices, this SHOULD work:įWIW the desktop workaround is to use the BluOS Controller desktop software.
TIDAL APP PC WINDOWS 10
Even when I take the Node out of the equation here, something's still not right - the Android implementation of Tidal does not see the Windows 10 version, and vice versa. My Android phone has always been reliable though - I can always send my session from my phone to my Node, or take it back to my phone. Then, suddenly, it just stopped seeing it. For a while there, the desktop Tidal would actually see my Node 2i streamer.
The weakest point seems to be the Windows desktop version of Tidal.
The Tidal implementation seems way more buggy/poorly implemented. The Spotify Connect functionality is pretty much flawless - I can send my session from any of those three devices, TO any of those three devices. I use Tidal and Spotify on my Android phone, my Windows 10 laptop, and my Node 2i streamer. This is not a major problem, I'm really just wondering if I'm the only one having it.
0 kommentar(er)
