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.
Re: Embedding subtitles ends in ERROR: Conversion failed! #22090
Comments
|
Once again: do not hardcode the extension in output template. Output template is the template of the file to be downloaded not the target file. Extension of A is |
|
@dstftw I see, it was unclear to me, that there was this distinction. |
|
|
|
I am sorry, I was mentally blind. I read the FAQ entry multiple times but I seem to have missed the correct meaning of "if a merge is required". It's obvious now in hindsight. |
Regarding an investigation I did that is related to a previously reported issue (#21929):
Consider these two youtube-dl calls:
A:
youtube-dl -v -i -f "22/136+bestaudio[ext=m4a]/bestvideo[height<=720]+bestaudio[ext=m4a]/best[height<=720]" --all-subs --embed-subs --merge-output-format mkv -o A.mkv "https://www.youtube.com/watch?v=oGVhOWqsBWM"B:
youtube-dl -v -i -f "bestvideo+bestaudio" --all-subs --embed-subs --merge-output-format mkv -o B.mkv "https://www.youtube.com/watch?v=oGVhOWqsBWM"They only differ in their
-fparameter and their-ofilename (A.mkvvsB.mkv).A ends up with:
while B completes without errors:
Comparing the respective ffmpeg calls from A (first line) and B (second line):
The only difference between these two merge-calls to ffmpeg is that A adds an extra
-c:s mov_text.Question
Is this a bug or an oversight? If not, what is the explanation for youtube-dl specifying a subtitle format that is incompatible with
mkvwhen--merge-output-format mkvis explicitly specified?Is the subtitle codec chosen based on
-f? Why, wouldn't it make more sense to have it chosen based on what the target file container supports?