On 7/29/2021 1:39 AM, James Almer wrote: > It's not a problem for AV1 (we correctly tag all packets that should be > sync samples).
I meant for the rest of the boxes ;) > I'm not going to bother with HEVC right now, but this all can be > simplified once we introduce a new parser API that exposes the important > per-codec bitstream values, CBS-style (and for example based on it), > that can be used by muxers, instead of relying purely on values present > in packets as exported by either a demuxer (from container info or > derived from auto inserted AVCodecParserContext in utils.c) or just made > up by the library user. That certainly sounds less insane than what currently exists in our APIs. - Derek _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
