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.
Problems with AdultSwim #13306
Problems with AdultSwim #13306
Comments
|
Dish MSO is not supported. |
|
dump-json? Thank you, now to figure out how to use that. Re: Dish MSO: Pull request #12000 works wonders and is ready for merging. |
Please follow the guide below
xinto all the boxes [ ] relevant to your issue (like that [x])Make sure you are using the latest version: run
youtube-dl --versionand ensure your version is 2017.06.05. 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?
So attempting to fetch from Adult Swim does not work. (Big surprise). Here's what I found when I tried, and some thoughts/ideas -- and, a feature request that comes out of this.
Now, the things to note:
First, it works for a while, and then fails.
Second, a big difference between this and watching in a browser: This is downloading much faster than watching in a browser.
Third, I decided to try to play around. I read up on the docs for ffmpeg, and found, among other things, both "seekable" and "-re".
Seekable is interesting -- you specify seekable of 0, so every time ffmpeg starts up, it has to start from the beginning. It never has a chance to say "lets resume from where we left off", which would allow the file to eventually complete.
-re is an ffmpeg option for, essentially, "real time" downloading -- instead of trying to fetch the file as fast as possible, about 8 times faster than watching speed, fetch at watching speed. Now, this will make things slow, but it will make things look like watching in a browser.
Fourth, and the feature request: I decided to try to plop that ffmpeg command line into a file, and try executing it. This was step 1 to trying to play around with the command line options.
What happened?
So what happened? It looks like this --
is a one-use cookie. Since you pass it to ffmpeg, and ffmpeg fails, I cannot reuse it.
So a feature request: Prepare an ffmpeg command, but instead of executing it, either output it, or put it into a file, so that the user can play around / alter it to test things out.