From: "Jan Ekström" <jeebjp@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v6 12/13] avcodec/libx264: add support for writing out CLL and MDCV
Date: Wed, 28 Feb 2024 01:39:24 +0200
Message-ID: <CAEu79SbEFnDkmtEkOjzp6R_JLLNp-BWccAS97ttct3jTohoxzg@mail.gmail.com> (raw)
In-Reply-To: <AS8P250MB07447D8F90B2504613382B648F592@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>
On Wed, Feb 28, 2024 at 12:24 AM Andreas Rheinhardt
<andreas.rheinhardt@outlook.com> wrote:
>
> Jan Ekström:
> > Both of these two structures were first available with X264_BUILD
> > 163, so make relevant functionality conditional on the version
> > being at least such.
> >
> > Keep handle_side_data available in all cases as this way X264_init
> > does not require additional version based conditions within it.
> >
> > Finally, add a FATE test which verifies that pass-through of the
> > MDCV/CLL side data is working during encoding.
> > ---
> > configure | 2 +
> > libavcodec/libx264.c | 79 ++++++++++++++++++++++++++++++++++++
> > tests/fate/enc_external.mak | 5 +++
> > tests/ref/fate/libx264-hdr10 | 15 +++++++
> > 4 files changed, 101 insertions(+)
> > create mode 100644 tests/ref/fate/libx264-hdr10
> >
> > diff --git a/configure b/configure
> > index bb5e630bad..f48cf46ffe 100755
> > --- a/configure
> > +++ b/configure
> > @@ -2527,6 +2527,7 @@ CONFIG_EXTRA="
> > jpegtables
> > lgplv3
> > libx262
> > + libx264_hdr10
> > llauddsp
> > llviddsp
> > llvidencdsp
> > @@ -6927,6 +6928,7 @@ enabled libx264 && require_pkg_config libx264 x264 "stdint.h x264.h" x
> > require_cpp_condition libx264 x264.h "X264_BUILD >= 122" && {
> > [ "$toolchain" != "msvc" ] ||
> > require_cpp_condition libx264 x264.h "X264_BUILD >= 158"; } &&
> > + check_cpp_condition libx264_hdr10 x264.h "X264_BUILD >= 163" &&
>
> Why don't you just check X264_BUILD in libx264.c instead of adding this
> to configure?
>
Most likely due to months ago it feeling like a cleaner option for
whatever reason (less magical numbers). Although in theory you can get
a similar named define by checking it within the module, yes.
Jan
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-02-27 23:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 22:12 [FFmpeg-devel] [PATCH v6 00/13] encoder AVCodecContext configuration side data Jan Ekström
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 01/13] avutil/frame: split side data list wiping out to non-AVFrame function Jan Ekström
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 02/13] avutil/frame: add helper for freeing arrays of side data Jan Ekström
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 03/13] avutil/frame: split side_data_from_buf to base and AVFrame func Jan Ekström
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 04/13] avutil/frame: split side data removal out to non-AVFrame function Jan Ekström
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 05/13] avutil/frame: add helper for adding side data to array Jan Ekström
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 06/13] avutil/frame: add helper for adding existing side data to set Jan Ekström
2024-02-27 23:20 ` James Almer
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 07/13] avutil/frame: add helper for getting side data from array Jan Ekström
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 08/13] avcodec: add frame side data array to AVCodecContext Jan Ekström
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 09/13] avcodec: add helper for configuring AVCodecContext's frame side data Jan Ekström
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 10/13] ffmpeg: pass first video AVFrame's side data to encoder Jan Ekström
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 11/13] avcodec/libsvtav1: add support for writing out CLL and MDCV Jan Ekström
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 12/13] avcodec/libx264: " Jan Ekström
2024-02-27 22:26 ` Andreas Rheinhardt
2024-02-27 23:39 ` Jan Ekström [this message]
2024-02-28 18:07 ` Jan Ekström
2024-02-27 22:12 ` [FFmpeg-devel] [PATCH v6 13/13] avcodec/libx265: " Jan Ekström
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEu79SbEFnDkmtEkOjzp6R_JLLNp-BWccAS97ttct3jTohoxzg@mail.gmail.com \
--to=jeebjp@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git