On Fri, Feb 21, 2020 at 7:08 PM Mohammad Izadi <moh.iz...@gmail.com> wrote:
>
> If you believe lavc is at the top of the hierarchy, I can simply move the
> file to lavc. Then both lavc and lavf can use it and hierarchy is
> respected. Can I do that? Doesn't break API? Any objection (with solution)?
> Let's make right decisions to speed up the process please :).
> --


The struct itself belongs in lavu with everything else of AVFrame. The
parsing of the mpeg-specific SEI data belongs in avcodec. You can't
just blindly move everything.

- Hendrik
_______________________________________________
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".

Reply via email to