search

ebb-earl-co / tidal-wave

Waving at the TIDAL music service
Apache License 2.0
38 stars 2 forks source link

Dolby Atmos Does Not Downloads #132

Closed Rajeshsahoo12 closed 6 months ago

Rajeshsahoo12 commented 6 months ago

Hi Dev,

I am using tidal-wave latest release & tried downloading this track in DOLBY ATMOS format. But unfortunately, it does not gets downloaded. Here is the url of track https://tidal.com/browse/track/295322685?u

Command I have used to download is tidal-wave https://tidal.com/browse/track/295322685?u --audio-format atmos

Error log :-

2024-04-02:04:02:12,099 INFO [models.py:668] TIDAL track ID parsed from input: 295322685 2024-04-02:04:02:12,729 INFO [requesting.py:95] Requesting from TIDAL API: tracks/295322685 2024-04-02:04:02:13,773 INFO [requesting.py:95] Requesting from TIDAL API: albums/295322684 2024-04-02:04:02:14,794 INFO [requesting.py:95] Requesting from TIDAL API: tracks/295322685/credits 2024-04-02:04:02:15,817 INFO [requesting.py:95] Requesting from TIDAL API: tracks/295322685/playbackinfopostpaywall 2024-04-02:04:02:16,177 WARNING [requesting.py:107] 401 Client Error: Unauthorized for TIDAL API endpoint tracks/295322685/playbackinfopostpaywall

To make sure this track is in DOLBY ATMOS, I tried same track with HIRES audio format & here below have attached the terminal output. It means track is in `DOLBY ATMOS format.

2024-04-02:04:01:59,933 INFO [models.py:668] TIDAL track ID parsed from input: 295322685 2024-04-02:04:01:59,934 INFO [login.py:151] Loading TIDAL access token from 'C:\Users\Rajesh Sahoo\AppData\Local\tidal-wave\android-tidal.token' 2024-04-02:04:02:00,812 INFO [login.py:175] Access token is valid: saving to 'C:\Users\Rajesh Sahoo\AppData\Local\tidal-wave\android-tidal.token' 2024-04-02:04:02:00,814 INFO [requesting.py:95] Requesting from TIDAL API: tracks/295322685 2024-04-02:04:02:01,688 WARNING [track.py:681] Track 295322685 is only available in Dolby Atmos format. Downloading of track will not continue.

ebb-earl-co commented 6 months ago

@Rajeshsahoo12 can you tell me

  1. What OS you're using to execute this (it looks like Windows)
  2. Whether other Dolby Atmos tracks are able to be downloaded successfully

Then, can you retry to get this track and add --loglevel debug at the end?

Rajeshsahoo12 commented 6 months ago

@Rajeshsahoo12 can you tell me

  1. What OS you're using to execute this (it looks like Windows)
  2. Whether other Dolby Atmos tracks are able to be downloaded successfully

Then, can you retry to get this track and add --loglevel debug at the end?

Yeah I am using windows 10. No I have tried many DOLBY ATMOS tracks but the results are same.

Rajeshsahoo12 commented 6 months ago

--loglevel debug

I have ran the below command with --loglevel debug flag. And the results are shared.

https://justpaste.it/f5zq9 = This is for binary release tidal-wave-2024.3.6

https://justpaste.it/e6qgu = This is for binary release tidal-wave-2024.3.5.2

ebb-earl-co commented 6 months ago

@Rajeshsahoo12 I have downloaded the track you originally mentioned with no problem, and in the logs you’re getting a 401: Unauthorized response…

Is it just Dolby Atmos for which you are getting these responses? My first thought is that your account lapsed and you haven’t paid for TIDAL HiFi. That might cause this 🤷

Rajeshsahoo12 commented 6 months ago

I have downloaded the track you originally mentioned with no problem

Ohhhh okay. But I am able to download hi-res files with same account access token. I am having HIFI PLUS FAMILY account.

image

Rajeshsahoo12 commented 6 months ago

@Rajeshsahoo12 I have downloaded the track you originally mentioned with no problem, and in the logs you’re getting a 401: Unauthorized response…

Is it just Dolby Atmos for which you are getting these responses? My first thought is that your account lapsed and you haven’t paid for TIDAL HiFi. That might cause this 🤷

Hi-Res files are not having any issue with same account access token. Here is the mediainfo of the same tracks which was downloading in terminal.

https://mediaarea.net/MediaBin/yKZaN3RC

image

Rajeshsahoo12 commented 6 months ago

@Rajeshsahoo12 I have downloaded the track you originally mentioned with no problem, and in the logs you’re getting a 401: Unauthorized response…

Is it just Dolby Atmos for which you are getting these responses? My first thought is that your account lapsed and you haven’t paid for TIDAL HiFi. That might cause this 🤷

I have tried using this repo script https://github.com/Dniel97/orpheusdl-tidal for downloading DOLBY ATMOS track. I have used the same account for the login in program. And it is able to download the DOLBY ATMOS track.

Command used to download python orpheus.py https://tidal.com/browse/track/295322685 . And here I have attached the mediainfo for the downloaded file. https://mediaarea.net/MediaBin/bZqcINHP

image

ebb-earl-co commented 6 months ago

How strange… I was about to retrieve this track (and the rest of the album) without issue, and it seems that you were able to retrieve the track from the TIDAL API with another project…

I really do not know to what to attribute the error you are experiencing, especially because it’s a 401 unauthorized response.

Rajeshsahoo12 commented 6 months ago

https://github.com/Dniel97/orpheusdl-tidal

Ohhh. Okay. Yeah it is strange behavior. I thought may be this is issue with my ISP, so I have tried with same account access token & tidal-wave latest binary release on vps too. But the error is same. So, definately it is not issue with machine.

And one more thing is for login process it is not asking for any access token. In 1st start of the module it generates with device linking link & awaits for the login process to be finished. It is same as the fire-tv access token login happens on ur project./

And that's it. And it generates config. json which can also be modified as per ur needs.

Rajeshsahoo12 commented 6 months ago

How strange… I was about to retrieve this track (and the rest of the album) without issue, and it seems that you were able to retrieve the track from the TIDAL API with another project…

I really do not know to what to attribute the error you are experiencing, especially because it’s a 401 unauthorized response.

As I remember well & it was mentioned here in readme that to extract HiRes FLAC, Dolby Atmos, and Sony 360 Reality Audio tracks we need to have access token extracted from android device / windows device.

image

So, I use android device access token to rip HIRES & DOLBY ATMOS.

But now I have deleted all of my existing token inside config folder. And when I tried to rip DOLBY ATMOS track with fresh access token from android device inside config folder.

It says below msg in terminal now it is asking for fire-tv access token. Which is I think there has been some changes with code.

image

And voilla after successfull login to my account with provided device link url. Program got the fire-tv access token & it successfully downloaded the track which were trying. Here is the success msg.

image

Thanks dev for being patient about it.

ebb-earl-co commented 6 months ago

How strange… I was about to retrieve this track (and the rest of the album) without issue, and it seems that you were able to retrieve the track from the TIDAL API with another project… I really do not know to what to attribute the error you are experiencing, especially because it’s a 401 unauthorized response.

As I remember well & it was mentioned here in readme that to extract HiRes FLAC, Dolby Atmos, and Sony 360 Reality Audio tracks we need to have access token extracted fro android device / windows device. So, I use android device access token to rip HIRES & DOLBY ATMOS

But now I have deleted all of my existing token inside config folder. And when I tried to rip DOLBY ATMOS track with fresh access token from android device. It says below msg in terminal now it is asking for fire-tv access token. Which is I think there has been some changes with code.

image

image

If you’re talking about the code for tidal-wave, then it has always been the case that Dolby Atmos tracks are retrieved with the spoofed Fire TV parameters.

The TIDAL website does list Android as a Dolby Atmos-capable client, but there must be some other code inside the TIDAL for Android app that I don’t have a way to replicate. Thus, Atmos is retrieved with the spoofed Fire TV credentials.

ebb-earl-co commented 6 months ago

https://github.com/Dniel97/orpheusdl-tidal

Ohhh. Okay. Yeah it is strange behavior. I thought may be this is issue with my ISP, so I have tried with same account access token & tidal-wave latest binary release on vps too. But the error is same. So, definately it is not issue with machine.

And one more thing is for login process it is not asking for any access token. In 1st start of the module it generates with device linking link & awaits for the login process to be finished. It is same as the fire-tv access token login happens on ur project./

And that's it. And it generates config. json which can also be modified as per ur needs.

Is this project capable of retrieving HiRes or Sony 360 tracks?

Rajeshsahoo12 commented 6 months ago

How strange… I was about to retrieve this track (and the rest of the album) without issue, and it seems that you were able to retrieve the track from the TIDAL API with another project… I really do not know to what to attribute the error you are experiencing, especially because it’s a 401 unauthorized response.

As I remember well & it was mentioned here in readme that to extract HiRes FLAC, Dolby Atmos, and Sony 360 Reality Audio tracks we need to have access token extracted fro android device / windows device. So, I use android device access token to rip HIRES & DOLBY ATMOS But now I have deleted all of my existing token inside config folder. And when I tried to rip DOLBY ATMOS track with fresh access token from android device. It says below msg in terminal now it is asking for fire-tv access token. Which is I think there has been some changes with code. image image

If you’re talking about the code for tidal-wave, then it has always been the case that Dolby Atmos tracks are retrieved with the spoofed Fire TV parameters.

The TIDAL website does list Android as a Dolby Atmos-capable client, but there must be some other code inside the TIDAL for Android app that I don’t have a way to replicate. Thus, Atmos is retrieved with the spoofed Fire TV credentials.

Ohhhhh okay. I got it.

Rajeshsahoo12 commented 6 months ago

https://github.com/Dniel97/orpheusdl-tidal

Ohhh. Okay. Yeah it is strange behavior. I thought may be this is issue with my ISP, so I have tried with same account access token & tidal-wave latest binary release on vps too. But the error is same. So, definately it is not issue with machine. And one more thing is for login process it is not asking for any access token. In 1st start of the module it generates with device linking link & awaits for the login process to be finished. It is same as the fire-tv access token login happens on ur project./ And that's it. And it generates config. json which can also be modified as per ur needs.

Is this project capable of retrieving HiRes or Sony 360 tracks?

Yes it does HIRES , DOLBY ATMOS , MQA & 360 RA

For HIRES I have downloaded the same tracks using both projects https://tidal.com/browse/track/294592079. Here below is the mediainfo for the both files :-

image

https://mediaarea.net/MediaBin/NWRtTinl = Using tidal-wave

https://mediaarea.net/MediaBin/Xs07WeN2 = Using orpheusdl-tidal

For DOLBY ATMOS I have downloaded the same tracks using both projects https://tidal.com/browse/track/295322685. Here below is the mediainfo for the both files :-

image

https://mediaarea.net/MediaBin/CcAOnmyu = Using tidal-wave

https://mediaarea.net/MediaBin/TMFSXGJ7 = Using orpheusdl-tidal

For 360RA I have downloaded the same tracks using both projects https://tidal.com/browse/track/354739558. Here below is the mediainfo for the both files :-

image

https://mediaarea.net/MediaBin/lXhTbjMp = Using tidal-wave

https://mediaarea.net/MediaBin/bXqMDAJG = Using orpheusdl-tidal

Thanks

ebb-earl-co commented 6 months ago

Excellent. Well, if you continue to hit problems with this project, you have a backup!

Rajeshsahoo12 commented 6 months ago

Excellent. Well, if you continue to hit problems with this project, you have a backup!

I can think why I was getting error. May be fire-tv access token old in the tidal-wave config folder. Yesterday I have deleted it & reconnected the device with tidal. So, fresh access token got generated for fire-tv login mode. And it worked.

Thanks