[FFmpeg-trac] #11109(avformat:closed): Matroska output format missing supported video codec tags (additional_video_tags)

[FFmpeg]

#11109: Matroska output format missing supported video codec tags
(additional_video_tags)
------------------------------------+------------------------------------
             Reporter:  SuRGeoNix   |                    Owner:  (none)
                 Type:  defect      |                   Status:  closed
             Priority:  normal      |                Component:  avformat
              Version:  git-master  |               Resolution:  invalid
             Keywords:  mkv         |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+------------------------------------
Comment (by SuRGeoNix):

 Thanks mkver...

 Just trying to see if there is a proper way to check if a codec (and/or
 codec_tag) is supported by the output format. I was missing
 avformat_query_codec which seems to be the closest on what I'm looking for
 (fftools using it as well - only for video).

 It is not clear when we have the codec_tags (+audio/video/subs/data codec)
 in the AVOutputFormat and at the same time you have the query_codec (which
 is mainly for matroska as I can see +img2/mp3) which checks different
 codecs from ff_mkv_codec_tags and the mkv_init blacklists some other
 codecs (query_codec will return them as supported when std_compliance <
 FF_COMPLIANCE_NORMAL).

 So, I'm afraid that the answer to my (last) question is we can't trust
 what is supported or not from the output format. That would be possible
 only if every muxer had a related query_codec func that return only
 true/false and not unknown (or even falsely true/false).

 Finally, I've noticed that matroska audio and video muxers have the same
 name (seems the only case that two muxers sharing the same name) and
 probably it should be unique?
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11109#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker