Tidal account

Rosuken

e

Now im receiving cant determine type of stream

FenixFeniks

@ruben2rl i have not been able to use this method to get my toke from the 25 some odd files in that location. Has this method changed at all to your knowledge?

kamilos_x

@fenixfeniks Same. Worked for me last time I tried it a few months back. This time I get no output after running the grep command

hogthow

@kamilos_x I ran into the same problem with the latest version of the Tidal Android app. I had to uninstall the Tidal android app and load an older version (I used 2.3.7) and it worked fine.

superfluous

@hogthow said in Tidal account:

@kamilos_x I ran into the same problem with the latest version of the Tidal Android app. I had to uninstall the Tidal android app and load an older version (I used 2.3.7) and it worked fine.

Yes, it looks like something has changed.

In 2.3.7 (from APKMirror) the format is like this:

[REDACTED].0:X-Tidal-Token: [REDACTED/this is the part you need]

While in later versions it is:

[REDACTED].0:vary: x-tidal-sessionid,x-tidal-token,authorization

Anyway, finally got it to work.

kjetilk

I just reopened a Tidal subscription, since my daughter also wanted Tidal, and the hope it would work with Strawberry again.

I can't find a X-Tidal-Token in the cache files now on my Android Fairphone 3+. There is some JSON:

{"authenticationToken":"redacted"}

I tried to use that, but that didn't work. I suppose that's not actually the client ID.

Are there any changes that people have encountered recently?

superfluous

@kjetilk Tidal app version...?

Already back in 2022 the correct token was only available from an older Tidal app version. -> https://forum.strawberrymusicplayer.org/post/1530

If the old-version-app still allows successful log-in - I haven't needed to this again so I don't know.

kjetilk

@nonsequitur Uh-oh. Everything is uptodate as of today here.

I used Tidal with Strawberry some years ago, but stopped as it broke for some reason that I didn't figure out. Decided to give it another try today.

I'll try and see if I manage to install the old version.

MorenoAL

Para los que lleguen por aquí para estas fechas, les comento que el método que propone @ruben2rl funciona con versiones anteriores de la app de Tidal en Android, específicamente yo usé la version 2.32.1, sugerida en otro foro por un usuario que le funcióno también con esa versión instalada en su android.

Esta faceta del internet me facina, donde nos podemos ayudar mútuamente.

Gracias a todos por su colaboración a cada momento.

kjetilk

I've had Tidal working again for a while now, but just had an error that said something around an expired token. I didn't record the actual error message, but I was afraid the API token had expired, so I checked that, but it eventually turned out that it was most probably the OAuth bearer token, so all I needed to do was to log in again.

I did notice 401 in the error message though, so I suppose the client might have gotten an HTTP 401 from the Tidal API, which would make it clear that logging in again was required.

So, perhaps this would be an enhancement, that if the client receives a 401, Strawberry prompts the user to log in?

cdhacker

Managed to get Hi-Res working using this script:

https://gist.github.com/nsyntych/eb867b06dd4350e22785223b1af7696c

Obviously you need to never touch your tidal settings from the GUI otherwise it will break.

I am working on porting the functionality of tidalapi lib into Strawberry itself. Until I find the time the workaround works great and it is a nice POC.

blondu

It works very well and you can save Strawberry.conf for installation on another system

jonas

@cdhacker
This seem to have to do with the client ID which the tidalapi script uses, and quality set to "HI_RES_LOSSLESS" and stream URL method set to "playbackinfopostpaywall".

HI_RES_LOSSLESS was missing for quality, added now.

I'm able to stream with some albums with 96/24 and some with 192/24 without any other modifications to the authentication code.