On 08/09/2012 10:36 AM, Martin Storsjö wrote:
> The latter case fails, since if using -latm 1, it still uses the normal
> AAC codec id, and the mpegts muxer can't identify it as LATM (ending up
> with "AAC bitstream not in ADTS format and extradata missing"). If I
> make the fdk-aac wrapper change the codec id to AV_CODEC_ID_AAC_LATM if
> the latm flag is set, this seems to work fine. But is it even valid for
> an encoder to change the codec id during initialization?

Looks like we should deliver this kind of information (both for aac and
h264) in a more reliable way.

lu

_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to