From: Kyle Swanson <k@ylo.ph>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Chema Gonzalez <chemag@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH 3/3] lavfi/vf_libvmaf: add warning when color ranges differ
Date: Mon, 17 Apr 2023 12:09:22 -0700
Message-ID: <CALbjROJJ5WiFA+0VTMv9migX_rmuYCHS95n_rhZo21pGNRA3MQ@mail.gmail.com> (raw)
In-Reply-To: <20230401174737.85192-3-chemag@gmail.com>
Hi,
I think the warning is probably OK, but maybe better to put it into
config_input_ref along with the other input checks.
On Sat, Apr 1, 2023 at 10:48 AM Chema Gonzalez <chemag@gmail.com> wrote:
> ---
> libavfilter/vf_libvmaf.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/libavfilter/vf_libvmaf.c b/libavfilter/vf_libvmaf.c
> index 2586f37d99..67f0d6a22f 100644
> --- a/libavfilter/vf_libvmaf.c
> +++ b/libavfilter/vf_libvmaf.c
> @@ -141,6 +141,13 @@ static int do_vmaf(FFFrameSync *fs)
> if (ctx->is_disabled || !ref)
> return ff_filter_frame(ctx->outputs[0], dist);
>
> + if (dist->color_range != ref->color_range) {
> + av_log(ctx, AV_LOG_WARNING, "distorted and reference "
> + "frames use different color ranges (%s != %s)\n",
> + av_color_range_name(dist->color_range),
> + av_color_range_name(ref->color_range));
> + }
> +
> err = copy_picture_data(ref, &pic_ref, s->bpc);
> if (err) {
> av_log(s, AV_LOG_ERROR, "problem during vmaf_picture_alloc.\n");
> --
> 2.39.2
>
Thanks,
Kyle
_______________________________________________
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:[~2023-04-17 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 17:47 [FFmpeg-devel] [PATCH 1/3] lavfi/vf_psnr: " Chema Gonzalez
2023-04-01 17:47 ` [FFmpeg-devel] [PATCH 2/3] lavfi/vf_ssim: " Chema Gonzalez
2023-04-01 17:47 ` [FFmpeg-devel] [PATCH 3/3] lavfi/vf_libvmaf: " Chema Gonzalez
2023-04-17 19:09 ` Kyle Swanson [this message]
2023-04-17 21:14 ` Chema Gonzalez
2023-09-23 14:55 ` Kyle Swanson
2023-09-23 14:54 ` [FFmpeg-devel] [PATCH 1/3] lavfi/vf_psnr: " Niklas Haas
-- strict thread matches above, loose matches on Subject: below --
2023-03-31 16:49 [FFmpeg-devel] [PATCH 0/3] add warnings to quality metrics on color range mistmatch Chema Gonzalez
2023-03-31 16:49 ` [FFmpeg-devel] [PATCH 3/3] lavfi/vf_libvmaf: add warning when color ranges differ Chema Gonzalez
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=CALbjROJJ5WiFA+0VTMv9migX_rmuYCHS95n_rhZo21pGNRA3MQ@mail.gmail.com \
--to=k@ylo.ph \
--cc=chemag@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