[FFmpeg-devel] [PATCH] Update HDR10+ metadata structure.

[Vittorio Giovara]

On Fri, Feb 21, 2020 at 5:17 PM Mohammad Izadi <moh.izadi at gmail.com> wrote:

> Why does the struct belong to lavu? This struct is super similar to structs
> in libavcodec/hevc_sei.h. We just move it to a new file to share it between
> hevc and vp9 encoder/decoder.
>
> --
>

1. Please kindly stop top posting: http://www.idallen.com/topposting.html
2. It belongs to lavu because it's where the frame code generically code
is. I'm not familiar with this API too much, but from what i gather users
may need to have a way of accessing this data without pulling in all the
dependencies of lavc or lavf.

Vittorio

On Fri, Feb 21, 2020 at 2:03 PM Hendrik Leppkes <h.leppkes at gmail.com> wrote:
>
> > On Fri, Feb 21, 2020 at 7:08 PM Mohammad Izadi <moh.izadi at 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 at ffmpeg.org
> > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> >
> > To unsubscribe, visit link above, or email
> > ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".



-- 
Vittorio