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.
ytdl falls back to 'best' format even for JSON output when no ffmpeg/avconv #7289
Comments
|
This is expected. Why don't you specify |
|
Because youtube-dl's default is already what we want (except when it isn't for reasons that make no sense), so we would like to avoid forcing anything that doesn't need forcing. |
|
|
|
Yes, I totally understand how it comes to this. But since it makes no sense for the JSON output to be influenced by completely irrelevant factors, I'd like you to improve this. According to the documentation: |
|
No, that makes no sense. How one would guess what format(s) has(ve) been downloaded by default when no ffmpeg/avconv is available if JSON will contain data for |
|
After some discussion with @dstftw via IRC PM ... The point @dstftw was trying to make was that the JSON info should match the actual download behaviour, since 3rd party applications may use the JSON output to gather further information on what youtube-dl downloaded. However, if we just added HOWEVER, the manual specifically states "Simulate" for the
Ooor ... we can just always force |
Is not that simple,
I would probably safe to use |
Would be fine, but maybe label it the other way round like |
|
+1 |
Title says pretty much everything. This is a problem for mpv. We want to use the youtube DASH streams by default, but the user only gets them if they happen to have ffmpeg or avconv installed.