-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
-f
parameter and their-o
filename (A.mkv
vsB.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
mkv
when--merge-output-format mkv
is 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?The text was updated successfully, but these errors were encountered: