From Mosaic unable to open Tidal > My Music > Tracks. Mosaic just spins and not showing tracks. I am able to reproduce the issue on every device I had, tablet and mobile phone. I thought it could be isolated to a device, so, tried the following, still no luck
Logged out of Tidal and relogged in
Removed all the tracks in my collection and readded
Uninstalled Mosaic and reinstalled
Fresh installed and setup Mosaic on a new device
Don’t know what more to do, so, logging this request.
Tracks from my collection opens fine from Tidal and able to use Tidal Connect, however, that isn’t ideal knowing the issue with Tidal Connect. Using Tidal Connect is a pain unable to switch audio streaming sources, Mosaic not releasing the connection.
This issue started few months ago and has been in since last 2 version updates. My Vivaldi upsampler is updated and has Network board version 1.4.4 (527).
I am not a Tidal subscriber and therefore cannot see exactly what your issue is. However it sounds much like an issue that is known by dCS, is caused externally (streaming provider), and for which a fix has been devised ( news from 20 days ago). However this will involve the next Mosaic update whenever that may come.
Read this and the preceding thread which will give you the picture:
Interestingly two Mosaic releases came after this problem cropped, but neither included the fix and still waiting for the next release. Atleast the problem is known and is acknowledged that’s a good news.
dCS would invest time if there is money coming into their business from it, free items they care very little. If they had a contract with Airable to provide the proxy to Tidal API, it is a fix there or if dCS maintains it then their job.
Technically it didn’t sound as complex other than trying to pointing fingers who will do the fix, more of a management issue. Integrations may break, however, a software fix isn’t as complex as dCS explained it on the other thread. Worst part is dCS though may not accept they are a software company (selling software in a box) and cannot fix a simple integration issue.
I’m not sure if you have seen but I posted a reply a month ago on the other thread stating that the issue had been identified, that TIDAL / Airable have been made aware of it AND a workaround for the issue is being implemented into Mosaic that will be included in the next release, this was also referenced by Pete / @PAR above…