Sure. The UltraRendu and Sonic Transporter are both hardwired to an Asus GigE wifi/Ethernet router over Cat 6e (Blue Jeans Cables) with a crossover cable to a Spectrum-provided cable modem. No other network devices are in the network chain.
Tidal did work initially, I subscribed in December and it worked for a couple of months, then suddenly stopped in February. I had thought it was a billing issue with Tidal, but have since confirmed my account with them is in good standing. Tidal has always played just fine through the local audio outputs on the Samsung Galaxy Note A 10" I use as my remote Roon controller.
NB. Problem is solved. I needed to log out of Tidal and back on with a different account ID, as an evaluation account I had was mistakenly used, causing this problem. However, I had difficulty accomplishing this, as after logging out of Tidal, the login interface failed to launch the browser on the first several tries. Then when it did work and handed back off to Roon, the login button stubbornly refused to go away. The problem persisted through several Roon restarts, tablet reboots and power cycles. I finally turned the tablet off and left it for a week and went back to listening to my analog source. A week later, I fired it up and was able to login to Tidal successfully.
So… 3 takeaways:
- Not every issue reported has to do with hardware or topology and I wish you would consider this during your analysis and
- Please research the issue I had with the Services interface to logging into Tidal. Perhaps a stuck cache somewhere?
- If a streaming service subscription account is unable to play files, it would be helpful to improve the error handling to not attempt to play all of the files in an album, fail on each one and then, after the last file, just say, “too many errors,stopping”. A more meaningful error would be useful - I have seen others report similar issues.
FYI, I am an IT QA / Quality Engineering specialist and would be willing to assist with these - and any other - defect resolutions or beta testing.