-
-
Notifications
You must be signed in to change notification settings - Fork 476
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: DL Track[*] failed.Can't get the streamUrl, type is application/dash+xml #931
Comments
Weird - was working literally half an hour ago for me - then seemed to have stop after midnight ( or just before ). There was a newer version when I tried updating, but that's also showing the issue - so I wonder if it's a tidal-side change (I'm still authed, tho I wonder if they've invalidated the keys again). |
Same issue on Termux. Tried:
Edit: I tried API Key 4 again and it seems to be working. |
Had the same issue, I changed it to API key 4, that seemed to fix it... for now. |
Was already using API key 4 - I suspect that keys been rolled over again and we need to extract a new one. |
Also seeing the same issue... |
same issue "[ERR] DL Track[Nubes] failed.Can't get the streamUrl, type is application/dash+xml" |
I´ve tried it and now works perfect! |
Same problem. Either: |
I did find a workaround, not really sure what changed to cause it to not work on the latest. But downgrading to an older version, authenticating and then upgrading to the latest does seem to make it work. You can review this to see how've I've scripted it: |
Wow, I can confirm this works for me too. How on earth did you figure this out? Such a nuanced issue/workaround... I'm thinking about this... It must have to do with how the auth is being done? It just doesn't seem to make sense because the actual error shown doesn't seem relevant to the auth. I'm pretty new to this codebase but I plan to learn more about how it works so hopefully I can be more useful debugging. I did a |
Someone on my support channels pointed out that it worked, so I just tested and pushed a workaround for my automation script... |
I have to switch to API Key 1 and then back to API Key 4, after reauthenticating it works for a while |
For some reason I been trying that out already back & forth api 1 & 4 & still can't get it to work I've done authentication at least 10 times |
Switching API key to 1 then back to 4 also fixed the issue for me just now. |
Switching API key to 1 then back to 4 also worked for me. |
Same! Switch to 1 and after to 4. |
Worked for me too. Thanks! |
|
Doesn't work anymore, when will there be an update? |
Having the issue now |
obtube un accestoken de tidal para descargar en la mejor calidad y sale este mensaje:
|
same problem here! |
Same problem! Then I decided to other Tidal downloaders. You can try the Tunelf Tidal Music Converter. I used it for a while. So far, so good. |
What other tidal downloader? |
Athame Tidal Downloader is also good. But I think it's not as easy to use as Tunelf. If you don't care about the sound quality, you can also try some recorders like Audacity and Apowersoft. |
Hello everyone, I encountered the same problem at first, but like others by changing the API Key between 1 and 4 I have been able to download files, but I find that even though the Tidal player says that the track is 24 Bit 44, 1 Khz, the download always remains at 16 Bit, any ideas? If I use the graphical environment, the album that says 24 Bit in the tidal web player is only shown as lossless Thank you. |
I've encountered this problem myself, in a long playlist many tracks are getting this error. I've tried changing the api key from 4 to 1 and back to 4, but it's still happening. I'm using tidal-dl version: 2022.10.31.1 on Fedora 40. |
Hello, If you set quality to HiFi at least you're able to download LOSSLESS |
^ If anyone is having issues with MQA after July 24, 2024... its because Tidal removed MQA support. Switch it over to 2 - HiFi in quality settings and you should be good |
If you drop to Hi-Fi it will ignore those with error (that I presume are the MQA ones), but if you remain with Master it will still download the flac ones, but will throw errors for others that are ignored by Hi-Fi, so it doesn't seem to be much change. |
Actually selecting '2'–Hi-Fi downloads 16/44.1 FLAC files even if the album has MAX quality on Tidal, and '3'-Master throws errors but does not download anything at all. Is it like this for everyone? |
An update to the max level is urgently needed. |
but in the python code master quality is no longer there instead it there is "MAX", the next code was taken from tidal.py file (it was updated a year ago) inside tidal dl folder: def getStreamUrl(self, id, quality: AudioQuality): Is interesting because tidal dl have a lot files that were updated a year ago when tidal officially announced the abandonment MQA format, the rest files inside tidal dl continue to be older than two years. But the user quality options list doesn't recognize the Max quality code updated a year ago, maybe it's a bug in python code? we always have the option to download max quality but is only a bug? tidal dl.exe file was updated almost two years ago, maybe there is the problem with the files updated a year ago. |
Which tool
tidal-dl
Version
2022.06.24.2
Platform
PRETTY_NAME="Ubuntu 22.04 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
Describe the bug
when a playlist is downloading the downloader has no possibility to retrieve the url. (any playlist official or personal)
I tried with apiKEY 1 and 4 both with master quality.
Tried also 4 in HiFi but nothing
Relevant log output
Add screenshots
No response
The text was updated successfully, but these errors were encountered: