Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavfi/vf_fieldmatch: keep fields as-is if not matched properly
Date: Fri, 4 Nov 2022 14:24:13 +0100
Message-ID: <CAPYw7P6asUNJe4RJT+x6xqAaNXvERLLh-v8ysYbnfUZ8FBAaZg@mail.gmail.com> (raw)
In-Reply-To: <399842a707482604827e62860e98cb37@nodoa.me>

On 11/3/22, mail@nodoa.me <mail@nodoa.me> wrote:
> Makes it possible to use deinterlacers which output one frame for each field
> as fallback if field
> matching fails (combmatch=full).
>
> Currently, the documented example with fallback on a post-deinterlacer will
> only work in case the
> deinterlacer outputs one frame per first field (as yadif=mode=0). The reason
> for that is that
> fieldmatch will attempt to match the second field regardless of whether it
> recognizes the end
> result is still interlaced. This produces garbled output with for example
> mixed telecined 24fps and
> 60i content combined with a field-based deinterlaced such as yadif=mode=1.
> This patch orders fieldmatch to revert to using the second field of the
> current frame in case the
> end result is still interlaced and a post-deinterlacer is assumed to be
> used.
>

Are there samples, ways to reproduce this?

> Signed-off-by: lovesyk <lovesyk@users.noreply.github.com>
> ---
>  libavfilter/vf_fieldmatch.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/libavfilter/vf_fieldmatch.c b/libavfilter/vf_fieldmatch.c
> index 40e559df9e..bf946beec9 100644
> --- a/libavfilter/vf_fieldmatch.c
> +++ b/libavfilter/vf_fieldmatch.c
> @@ -680,7 +680,7 @@ static int filter_frame(AVFilterLink *inlink, AVFrame
> *in)
>      AVFilterLink *outlink = ctx->outputs[0];
>      FieldMatchContext *fm = ctx->priv;
>      int combs[] = { -1, -1, -1, -1, -1 };
> -    int order, field, i, match, sc = 0, ret = 0;
> +    int order, field, i, match, interlaced_frame, sc = 0, ret = 0;
>      const int *fxo;
>      AVFrame *gen_frames[] = { NULL, NULL, NULL, NULL, NULL };
>      AVFrame *dst = NULL;
> @@ -793,6 +793,12 @@ static int filter_frame(AVFilterLink *inlink, AVFrame
> *in)
>          }
>      }
>
> +    /* keep fields as-is if not matched properly */
> +    interlaced_frame = combs[match] >= fm->combpel;
> +    if (interlaced_frame && fm->combmatch == COMBMATCH_FULL) {
> +        match = mC;
> +    }
> +
>      /* get output frame and drop the others */
>      if (fm->ppsrc) {
>          /* field matching was based on a filtered/post-processed input, we
> now
> @@ -813,7 +819,7 @@ static int filter_frame(AVFilterLink *inlink, AVFrame
> *in)
>
>      /* mark the frame we are unable to match properly as interlaced so a
> proper
>       * de-interlacer can take the relay */
> -    dst->interlaced_frame = combs[match] >= fm->combpel;
> +    dst->interlaced_frame = interlaced_frame;
>      if (dst->interlaced_frame) {
>          av_log(ctx, AV_LOG_WARNING, "Frame #%"PRId64" at %s is still
> interlaced\n",
>                 outlink->frame_count_in, av_ts2timestr(in->pts,
> &inlink->time_base));
> --
> 2.34.2
> _______________________________________________
> 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".
>
_______________________________________________
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-11-04 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 14:40 mail
2022-11-04 13:24 ` Paul B Mahol [this message]
2022-11-04 14:59 mail

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=CAPYw7P6asUNJe4RJT+x6xqAaNXvERLLh-v8ysYbnfUZ8FBAaZg@mail.gmail.com \
    --to=onemda@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