Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavfilter: vf_scale: Properly take in->color_range into account
Date: Sat, 5 Mar 2022 23:33:15 +0200 (EET)
Message-ID: <bc40effc-a6b-dec9-6abb-d9b57062b0ba@martin.st> (raw)
In-Reply-To: <20220304200900.GF2829255@pb2>

On Fri, 4 Mar 2022, Michael Niedermayer wrote:

> On Thu, Mar 03, 2022 at 02:06:45PM +0200, Martin Storsjö wrote:
>> While swscale can be reconfigured with sws_setColorspaceDetails,
>> the in/out ranges also need to be set before calling
>> sws_init_context, otherwise the initialization might choose
>> fastpaths that don't take the ranges into account.
>>
>> Therefore, look at in->color_range too, when deciding on whether
>> the scaler needs to be reconfigured.
>>
>> Add a new member variable for keeping track of this, for being
>> able to differentiate between whether the scale filter parameter
>> "in_range" has been set (which should override whatever the input
>> frame has set) or whether it has been configured based on the
>> latest frame (which should trigger reconfiguring the scaler if
>> the input frame ranges change).
>>
>> Signed-off-by: Martin Storsjö <martin@martin.st>
>> ---
>> To test this (without risking running many conflicting swscale
>> filters in one filter pipeline), we'd need to be able to tag
>> the incoming raw yuv data with colorspace and range without setting
>> the in_color_matrix and in_range options on the scale filter.
>>
>> When using the rawvideo demuxer, the pixel format is set via the
>> ffmpeg -pix_fmt option, but there's no corresponding option for
>> setting color matrix or range for it.
>> ---
>>  libavfilter/vf_scale.c | 13 +++++++++++++
>>  1 file changed, 13 insertions(+)
>
> This changes the output for:
> ffmpeg -i tickets/524/AVCI50.mov   -vframes 3 file-avci50dec.nut
> ffmpeg -i tickets/4493/AVCI100.mov -vframes 3 file-avci100dec.nut
>
> https://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket524/
>
> Is that intended ?
>
> - 233903 file-avci100dec.nut
> - 383853 file-avci50dec.nut
> + 196558 file-avci100dec.nut
> + 333893 file-avci50dec.nut

Looks like these source files have full range content; for any data with 
full range input, this patch makes sure it uses the right intended 
conversion through swscale. So yes, I guess it's expected that these 
conversions change.

// Martin
_______________________________________________
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:[~2022-03-05 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 12:06 Martin Storsjö
2022-03-03 12:08 ` Diederick C. Niehorster
2022-03-04 20:09 ` Michael Niedermayer
2022-03-05 21:33   ` Martin Storsjö [this message]
2022-03-05 23:08     ` Michael Niedermayer
2022-03-06 22:47       ` Martin Storsjö

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=bc40effc-a6b-dec9-6abb-d9b57062b0ba@martin.st \
    --to=martin@martin.st \
    --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