Closed fmarzocca closed 6 months ago
Hires lossless playback should not be possible if oauth is used. I believe this is related to the bug I talked about in the other issue. You can check what is_pkce is set to in your session json file.
Try to delete your oauth session and sign in again and see if it helps.
Hires lossless playback should not be possible if oauth is used.
I know. That's why I opened the ticket.
This is in tidal-oauth.json
:
"is_pkce": {"data": true}
Try to delete your oauth session and sign in again and see if it helps.
Again?.... :-( Can't I just edit the json and put false
? Why it has true
? I have regenerated it a week ago.
I have deleted oauth session and signed in again. Now the track is correctly reported as HI-RES/MQA, but in the session json there is always: is_pkce": {"data": true}
Yep, I believe I have found the cause of this bug. A fix will be added in the next release of mopidy-tidal / tidalapi.
@tehkillerbee Johannes, I am experiencing this problem every day. As I don't currently have the budget to buy a new DAC, but my converter works great with MQA, I would like to continue using my mopidy's playlists.
If you don't have planned to publish the new release soon, can I have the patch to apply locally?
This is already fixed on the latest master.
You could always install that until the next release of tidalapi/ mopidy-tidal is ready.
Otherwise I'll try to get the next release ready ASAP
Ah, ok. Does it extends to tidalapi too?
The issue is caused by tidalapi but probably the best idea to update both mopidy-tidal and tidalapi.
Otherwise I'll try to get the next release ready ASAP
Thanks!
I am afraid it is still there...
With OAUTH and HI_RES, the track tidal:track:2579:77622430:77622437
plays at:
{"quality": "HI_RES_LOSSLESS", "codec": "flac"}
Should I have (again) to delete the session json file?
I have deleted the session file and now it looks OK. I will report any future issue.
Now the session oauth file correctly contains:
"is_pkce": {"data": false}
I have set HI_RES and OAUTH, as confirmed by the log:
but it still plays HI_RES_LOSSLESS/FLAC for tracks that also have HI_RES/MQA available:
The track uri
tidal:track:15796:77661290:77661291
has MQA capability, but it plays HI_RES_LOSSLESS/FLAC:Shouldn't
TidalPlaybackProvider
take care of this?