Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Console spam, lagging downloader, unable to extract html5 player #17510
Comments
|
Turns out the video URL part was empty due to a logic error elsewhere. This may beg the question of whether this library should be verifying this before it goes ahead and performs a load of requests on the user's behalf though. Regardless, I will close this issue. Thanks for the time |
Please follow the guide below
Make sure you are using the latest version: run
youtube-dl --versionand ensure your version is 2018.09.08. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.Before submitting an issue make sure you have:
What is the purpose of your issue?
If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the
-vflag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):
Description of your issue, suggested solution and other information
On adding a playlist mix generated by YouTube. The process takes around 5 minutes. Only around 5 or 6 videos ever get resolved.
I am invoking this module as part of a larger chunk of code, which runs multiple downloaders concurrently. Since the API changed on YouTube prompting yesterday's update, the module has been extremely slow and spammy in terms of network usage, where it was not before.
...will get output roughly 1,400 times before any playlist begins to be resolved. This is a massive performance hit if it is constantly polling the website.