[FFmpeg-devel] [PATCH v23 05/10] avcodec/evc_encoder: Provided support for EVC encoder

[Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of James
> Almer
> Sent: poniedziałek, 29 maja 2023 15:10
> To: ffmpeg-devel at ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v23 05/10] avcodec/evc_encoder:
Provided
> support for EVC encoder
> 
> On 5/26/2023 7:32 AM, Dawid Kozinski wrote:
> > - Added EVC encoder wrapper
> > - Changes in project configuration file and libavcodec Makefile
> > - Added documentation for xeve wrapper
> >
> > Signed-off-by: Dawid Kozinski<d.kozinski at samsung.com>
> > ---
> >   configure                 |   4 +
> >   doc/encoders.texi         |  69 +++++
> >   doc/general_contents.texi |  11 +
> >   libavcodec/Makefile       |   1 +
> >   libavcodec/allcodecs.c    |   1 +
> >   libavcodec/libxeve.c      | 616 ++++++++++++++++++++++++++++++++++++++
> >   6 files changed, 702 insertions(+)
> >   create mode 100644 libavcodec/libxeve.c
> 
> Does libxeve provide a function to retrieve global headers, which you can
export
> as extradata? If so, it would be nice to use it, so the muxer doesn't need
to
> generate it from the first packet.

Currently, libxeve does not have a function that would allow us to retrieve
global headers that we could export as extradata. For now, the muxer has to
generate them from the first packet.

> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://protect2.fireeye.com/v1/url?k=cb34bac1-aabfaff1-cb35318e-
> 000babffaa23-93b106ee824575a8&q=1&e=7351e73f-ded9-4fba-bef2-
> 547578554ef8&u=https%3A%2F%2Fffmpeg.org%2Fmailman%2Flistinfo%2Fffmp
> eg-devel
> 
> To unsubscribe, visit link above, or email ffmpeg-devel-request at ffmpeg.org
> with subject "unsubscribe".