Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v3 11/12] avcodec/libx264: add support for writing out CLL and MDCV
Date: Tue, 22 Aug 2023 19:45:23 +0200
Message-ID: <AS8P250MB0744175D47782C15C7E12F278F1FA@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CABLWnS-yy_EGGXtJ2QsCyraz0q_GaGxqTrcPVEWRyMTCwoKj4Q@mail.gmail.com>

Vittorio Giovara:
> On Mon, Aug 21, 2023 at 9:49 PM Andreas Rheinhardt <
> andreas.rheinhardt@outlook.com> wrote:
> 
>> Actually, x264 allows to select only eight or ten bit bitdepth (or both)
>> at configure-time. IIRC opening the encoder will fail if an eight-bit
>> only libx264 is used when one tries to use a 10bit pixel format.
>> (This is actually a regression since x264 version 153; with older
>> versions the codec's advertised pixel formats actually match the really
>> supported pixel formats.)
>>
> 
> This changed a few years ago, x264 supports both bitdepths in a single
> binary since 153 (hence why the codepath got updated like so)

But if you use an x264 build that only supports one bitdepth, you can
run into the regression I mentioned (and the test will fail if you use
an 8-bit only libx264).

- Andreas

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

  reply	other threads:[~2023-08-22 17:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 21:48 [FFmpeg-devel] [PATCH v3 00/12] encoder AVCodecContext configuration side data Jan Ekström
2023-08-17 21:48 ` [FFmpeg-devel] [PATCH v3 01/12] avutil/frame: add AVFrameSideDataSet for passing sets of " Jan Ekström
2023-08-17 21:48 ` [FFmpeg-devel] [PATCH v3 02/12] avutil/frame: split side data list wiping out to non-AVFrame function Jan Ekström
2023-08-17 21:48 ` [FFmpeg-devel] [PATCH v3 03/12] avutil/frame: add helper for uninitializing side data sets Jan Ekström
2023-08-17 21:48 ` [FFmpeg-devel] [PATCH v3 04/12] avutil/frame: split side_data_from_buf to base and AVFrame func Jan Ekström
2023-08-17 21:48 ` [FFmpeg-devel] [PATCH v3 05/12] avutil/frame: add helper for adding side data to set Jan Ekström
2023-08-18  4:52   ` Andreas Rheinhardt
2023-08-17 21:48 ` [FFmpeg-devel] [PATCH v3 06/12] avutil/frame: add helper for getting side data from set Jan Ekström
2023-08-17 21:48 ` [FFmpeg-devel] [PATCH v3 07/12] avutil/frame: add helper for extending a set of side data Jan Ekström
2023-08-20  9:45   ` Andreas Rheinhardt
2023-08-28 20:30     ` Jan Ekström
2023-08-17 21:48 ` [FFmpeg-devel] [PATCH v3 08/12] avcodec: add side data set to AVCodecContext Jan Ekström
2023-08-17 21:48 ` [FFmpeg-devel] [PATCH v3 09/12] ffmpeg: pass first video AVFrame's side data to encoder Jan Ekström
2023-08-17 21:48 ` [FFmpeg-devel] [PATCH v3 10/12] avcodec/libsvtav1: add support for writing out CLL and MDCV Jan Ekström
2023-08-20  7:11   ` Andreas Rheinhardt
2023-08-21 21:38     ` Jan Ekström
2023-08-21 22:00       ` Andreas Rheinhardt
2023-08-22 21:49         ` Jan Ekström
2023-08-17 21:48 ` [FFmpeg-devel] [PATCH v3 11/12] avcodec/libx264: " Jan Ekström
2023-08-19 16:53   ` Michael Niedermayer
2023-08-19 22:25     ` Jan Ekström
2023-08-20  6:32       ` Andreas Rheinhardt
2023-08-20 13:12       ` Michael Niedermayer
2023-08-21 19:31         ` Jan Ekström
2023-08-21 19:50           ` Andreas Rheinhardt
2023-08-22 13:19             ` Vittorio Giovara
2023-08-22 17:45               ` Andreas Rheinhardt [this message]
2023-08-20  6:55   ` Andreas Rheinhardt
2023-08-21 20:31     ` Jan Ekström
2023-08-17 21:48 ` [FFmpeg-devel] [PATCH v3 12/12] avcodec/libx265: " Jan Ekström
2023-08-20  7:04   ` Andreas Rheinhardt

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=AS8P250MB0744175D47782C15C7E12F278F1FA@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM \
    --to=andreas.rheinhardt@outlook.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