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.
Optional filter specification for "ext" doesn't work #7522
Comments
|
That's not how |
|
Oh. Is that useful though? Shouldn't it mean "webm, and if that's not available, then whatever you would have picked instead." The current behavior doesn't sound useful, or at least not as useful. |
|
@realnc You may want to try |
|
@yan1212 As mentioned already, I'm using |
Videos that are provided only in "mp4" by YouTube break youtube-dl when using a filter specification such as:
I have
[ext=?webm]stored as a default option, so that WebM is preferred, but if it doesn't exist (like in the video given in the example above), then H.264 video is OK. The point is that WebM should be preferred if both are available, but it shouldn't fail if WebM is not available, since the filter operator is=?, not just=.In case it matters, the same thing happens with audio. Same error message if I try
bestvideo+bestaudio[ext=?webm].A workaround exists, but it can get rather long. For example, this doesn't work:
But the longer equivalent does work:
(The reason I prefer webm is because YouTube's H.264 encodes are lower quality compared to their VP9 encodes, even though the former has a higher bitrate compared to the latter.)