On Tue, Apr 10, 2018 at 07:21:29PM +0530, Gyan Doshi wrote:
> On 4/10/2018 4:49 AM, Michael Niedermayer wrote:
> >To implement generic "codec supported" checks, muxers would have to
> >list what they support.
> >There are 3 ways i know how this can be done in the current API
> >1. the audio_codec / video_codec / ... fields
> >2. the codec_tag array (this was in fact IIRC one of the intended uses of it)
> >3. the querry_format callback
> These are raw single stream muxers - most only dump packets and _should_
> accept exactly one codec_id. A couple may insert bitstream filters. Only one
> writes a trailer. So none of them have a codec_tag member or a query_codec
> callback. Personally, I agree that the current method is inelegant but these
> "muxers" are stable and these tests shouldn't need changes. But I can go the
> query_codec route if you advise it.

yes please do
note query_codec is only needed for the few special cases that do more than
one codec_id


Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The real ebay dictionary, page 2
"100% positive feedback" - "All either got their money back or didnt complain"
"Best seller ever, very honest" - "Seller refunded buyer after failed scam"

Attachment: signature.asc
Description: PGP signature

ffmpeg-devel mailing list

Reply via email to