05-14-2020, 01:04 PM
I may be restating the obvious, but I'm not certain we're all on the same wavelength here. There are two different ways to play Tidal tracks with moOde.
I'm talking specifically about one way, which is to have upmpdcli hold the Tidal credentials, authenticate with Tidal, and subsequently act as a proxy for the Tidal streaming servers. In this case, moOde is both a UPnP renderer and UPnP media server. It is the apparently broken authentication process in upmpdcli which I'm focused on.
The other way is to have a native Tidal app or some Tidal-aware app like BubbleUPnP hold the Tidal credentials and authenticate with Tidal. In this case, moOde need be only a UPnP renderer, Bluetooth renderer, or Airplay renderer. These apps may have authentication problems of their own but that's not a moOde issue.
Regards,
Kent
I'm talking specifically about one way, which is to have upmpdcli hold the Tidal credentials, authenticate with Tidal, and subsequently act as a proxy for the Tidal streaming servers. In this case, moOde is both a UPnP renderer and UPnP media server. It is the apparently broken authentication process in upmpdcli which I'm focused on.
The other way is to have a native Tidal app or some Tidal-aware app like BubbleUPnP hold the Tidal credentials and authenticate with Tidal. In this case, moOde need be only a UPnP renderer, Bluetooth renderer, or Airplay renderer. These apps may have authentication problems of their own but that's not a moOde issue.
Regards,
Kent
