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
Youtube: --get-url option not always returning direct video links #23324
Comments
Oh and almost forgot to mention that I found that the directly downloadable links are duplicated in a way that for each video there is a link with the audio and an other with the video. Judging by the fact that there are 2 times more links than how many videos I have, it's probably true for the other links too. |
There are no direct links for formats you're requesting cause they are served in segments. This has been answered numerous of times. Bother to use search. |
this is partially valid as the direct URLs for the same formats can be extracted(from the webpage) when
|
I bothered to use search (for @remitamine with this option yt-dl gives the right links, thank you |
because there is no such option as |
Oh! You're right. I don't know why I remembered --get-links, sorry! |
I wondered about this again, and thought I could ask if you could change the |
Checklist
Verbose log
Description
There are videos (example) for which the -g option returns a link containing video info instead of direct download link to video. Currently it prevents the user from easily downloading multiple videos at once, for example exporting a playlist's videos' into a file and using an external downloader to download them.
The video is on my channel and it's an unlisted video. There are a lot more actually, and most of them are outputted in this format. The ones that were outputted in the directly downloadable format are mostly old (or just small/low quality?) videos. I currently mainly use my account as an archive account, and it doesn't really have any viewer traffic on it, so I expect these videos to be deleted in the near future (when the new ToS will activate).
The text was updated successfully, but these errors were encountered: