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.
Please follow the guide below
xinto all the boxes [ ] relevant to your issue (like this:[x])Make sure you are using the latest version: run
youtube-dl --versionand ensure your version is 2019.01.24. 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?
The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to 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):
Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
Description of your issue, suggested solution and other information
When attempting to use AtomicParsley on a file > 2GB (I'm making a small guess here) it errors with the message.
I'm taking a small guess that it is limited to 32-bit right now and that would end up being right around 2GB. Currently this actually stops script. What's more it just spits out the text ERROR: in red and nothing more. I got the above by running the command directly that came up in the verbose output during debugging.
At this point the script should either catch the return code when the program is run and an attempt to embed fails
or flat out limit it in the scripting and not even run it when the step comes up if the file is > 2GB.Either waythe thumbnail that has already been downloaded should be left in place in case the user wants to try to embed it via another route.Update: This seems to be version dependent. I'm on Ubuntu 16.04 and it seems the repository version is rather old. I found a forked repository that seems to be a bit more up to date and it handled the file fine.
With that said catching the return code is still a valid case to try and handle since it will indicate that the user has an older version that can't handle the larger files properly.
Ubuntu 18.04 and higher has 0.9.6 which is what I had built myself. This is what people should be using for proper support.