From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 5/8] lavfi/vf_vpp_qsv: add has_passthrough flag in VPPContext
Date: Thu, 12 Jan 2023 05:31:55 +0100
Message-ID: <AS8P250MB0744ADF18CCE5525FB32DA808FFD9@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20230109071210.1829699-5-haihao.xiang@intel.com>
Xiang, Haihao:
> From: Haihao Xiang <haihao.xiang@intel.com>
>
> QSV filters may set this flag in preinit callback to turn on / off pass
> through mode
>
> This is in preparation for reusing the code for other QSV filters. E.g.
> scale_qsv filter doesn't support pass through mode.
>
> Signed-off-by: Haihao Xiang <haihao.xiang@intel.com>
> ---
> libavfilter/vf_vpp_qsv.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/libavfilter/vf_vpp_qsv.c b/libavfilter/vf_vpp_qsv.c
> index 2a7b06fa33..b04307b644 100644
> --- a/libavfilter/vf_vpp_qsv.c
> +++ b/libavfilter/vf_vpp_qsv.c
> @@ -102,6 +102,7 @@ typedef struct VPPContext{
>
> int async_depth;
> int eof;
> + int has_passthrough; /* apply pass through mode if possible */
> } VPPContext;
>
> static const AVOption options[] = {
> @@ -269,6 +270,8 @@ static av_cold int vpp_preinit(AVFilterContext *ctx)
> vpp->contrast = 1.0;
> vpp->transpose = -1;
>
> + vpp->has_passthrough = 1;
> +
> return 0;
> }
>
> @@ -552,7 +555,8 @@ static int config_output(AVFilterLink *outlink)
>
> if (vpp->use_frc || vpp->use_crop || vpp->deinterlace || vpp->denoise ||
> vpp->detail || vpp->procamp || vpp->rotate || vpp->hflip ||
> - inlink->w != outlink->w || inlink->h != outlink->h || in_format != vpp->out_format)
> + inlink->w != outlink->w || inlink->h != outlink->h || in_format != vpp->out_format ||
> + !vpp->has_passthrough)
> return ff_qsvvpp_create(ctx, &vpp->qsv, ¶m);
> else {
> av_log(ctx, AV_LOG_VERBOSE, "qsv vpp pass through mode.\n");
I don't get how this patch either. In the current patchset,
has_passthrough is always 1 (after the preinit callback) for the vpp_qsv
filter. The code here is only used by said filter and no other filter at
all, so has_passthrough is always 1 in config_output(), i.e. this whole
change is pointless.
- 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".
next prev parent reply other threads:[~2023-01-12 4:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 7:12 [FFmpeg-devel] [PATCH 1/8] lavfi/vf_vpp_qsv: add "a", "dar" and "sar" variables Xiang, Haihao
2023-01-09 7:12 ` [FFmpeg-devel] [PATCH 2/8] lavfi/vf_vpp_qsv: handle NULL pointer when evaluating an expression Xiang, Haihao
2023-01-12 4:01 ` Andreas Rheinhardt
2023-01-12 6:20 ` Xiang, Haihao
2023-01-16 4:34 ` Xiang, Haihao
2023-01-09 7:12 ` [FFmpeg-devel] [PATCH 3/8] lavfi/vf_vpp_qsv: allow special values for the output video dimensions Xiang, Haihao
2023-01-09 7:12 ` [FFmpeg-devel] [PATCH 4/8] lavfi/vf_vpp_qsv: add vpp_preinit callback Xiang, Haihao
2023-01-12 4:11 ` Andreas Rheinhardt
2023-01-12 4:44 ` Xiang, Haihao
2023-01-12 4:49 ` Andreas Rheinhardt
2023-01-12 5:41 ` Xiang, Haihao
2023-01-09 7:12 ` [FFmpeg-devel] [PATCH 5/8] lavfi/vf_vpp_qsv: add has_passthrough flag in VPPContext Xiang, Haihao
2023-01-12 4:31 ` Andreas Rheinhardt [this message]
2023-01-12 4:53 ` Xiang, Haihao
2023-01-09 7:12 ` [FFmpeg-devel] [PATCH 6/8] lavfi/vf_vpp_qsv: check output format string against NULL pointer Xiang, Haihao
2023-01-09 7:12 ` [FFmpeg-devel] [PATCH 7/8] lavfi/qsvvpp: set output frame durations Xiang, Haihao
2023-01-09 7:12 ` [FFmpeg-devel] [PATCH 8/8] lavfi/qsv: use QSVVPPContext as base context in vf_vpp_qsv/vf_overlay_qsv Xiang, Haihao
2023-01-12 3:58 ` [FFmpeg-devel] [PATCH 1/8] lavfi/vf_vpp_qsv: add "a", "dar" and "sar" variables Xiang, Haihao
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=AS8P250MB0744ADF18CCE5525FB32DA808FFD9@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