Anyone who wants Tidal should bug Tidal about it. We've spent a lot of time working on it, even had some help from Tidal, but it appears that their interface doesn't work in the U.S. They seem puzzled by this.
I have one of those 30 day trial going (from France) -- their desktop app wasn't working; wrote a ticket and they debugged/updated it today. The web browser worked right away. What is different about US internet from european internet?! seems weird; maybe a different interface or client app? just for the US? Otherwise try again with the modified desktop client -- with the time lag it, if it is not different, you should have it today in the US.
Here's a screen shot ...
(very spartan the Tidal config UI, but JRiver driver shows up --- Qobuz has much more fine tuning capabilities like buffer and latency
I'm wondering if it has something to do with device configuration. Try WASAPI generic out from the realtek (or other mobo out) bit-depth on automatic - avoiding ASIO or special bit-depth configurations; no convolution filters etc. just to rule somethings out empirically?
euh not meaning to patronize guys but just in case for new users, remember that the JRiver UI or at least the media server has to be running, otherwise there will be no sound as the default device set in WIndows is the JRiver 20 driver
I'm far from an expert on these things, but I have set up separate audio zones in over 10 peoples computers here for Qobuz and Tidal and no issues once the output was WASPI (a special driver using ASIO for PSAudio DAC didn't work, but the realtek using WASAPI on automatic did for the same DAC). Seems pretty strange that they would have different set-ups in geographically.
Only one person I know had problems that I couldn' sort, but he has a home-made digital preamp, 4-way monoblocks, lots of cross over filters etc. Take with a grain of salt, but