From: "Wu, Tong1" <tong1.wu-at-intel.com@ffmpeg.org> To: "\"zhilizhao(赵志立)\"" <quinkblack@foxmail.com>, "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/3] avfilter/vf_hwmap: get the AVHWDeviceType from outlink format Date: Thu, 30 Jun 2022 02:31:32 +0000 Message-ID: <SN6PR11MB2990817E829CB04A54475B05C0BA9@SN6PR11MB2990.namprd11.prod.outlook.com> (raw) In-Reply-To: <tencent_05AB164E7670C52DE49A6640659A509F3308@qq.com> > > On Jun 29, 2022, at 2:32 PM, Tong Wu <tong1.wu-at-intel.com@ffmpeg.org> > wrote: > > > > When a derive_device_type is not specified, the hwmap filter should be > > able to retrieve AVHWDeviceType from outlink->format and create > > corresponding hwdevice context. > > > > Signed-off-by: Tong Wu <tong1.wu@intel.com> > > --- > > libavfilter/vf_hwmap.c | 26 +++++++++++++++++--------- > > 1 file changed, 17 insertions(+), 9 deletions(-) > > > > diff --git a/libavfilter/vf_hwmap.c b/libavfilter/vf_hwmap.c index > > 2e03dfc1fe..a0c2e134cf 100644 > > --- a/libavfilter/vf_hwmap.c > > +++ b/libavfilter/vf_hwmap.c > > @@ -72,26 +72,34 @@ static int hwmap_config_output(AVFilterLink > *outlink) > > if (inlink->hw_frames_ctx) { > > hwfc = (AVHWFramesContext*)inlink->hw_frames_ctx->data; > > > > - if (ctx->derive_device_type) { > > - enum AVHWDeviceType type; > > + enum AVHWDeviceType type; > > mixed declarations and code. > > > > > + if (ctx->derive_device_type) { > > type = av_hwdevice_find_type_by_name(ctx->derive_device_type); > > if (type == AV_HWDEVICE_TYPE_NONE) { > > av_log(avctx, AV_LOG_ERROR, "Invalid device type.\n"); > > err = AVERROR(EINVAL); > > goto fail; > > } > > - > > - err = av_hwdevice_ctx_create_derived(&device, type, > > - hwfc->device_ref, 0); > > - if (err < 0) { > > - av_log(avctx, AV_LOG_ERROR, "Failed to created derived " > > - "device context: %d.\n", err); > > + } else { > > + type = av_hwdevice_get_type_by_pix_fmt(outlink->format); > > + if (type == AV_HWDEVICE_TYPE_NONE) { > > + av_log(avctx, AV_LOG_ERROR, "Could not get device type from " > > + "format %s.\n", av_get_pix_fmt_name(outlink->format)); > > + err = AVERROR(EINVAL); > > goto fail; > > } > > - device_is_derived = 1; > > } > > > > + err = av_hwdevice_ctx_create_derived(&device, type, > > + hwfc->device_ref, 0); > > I think a new device should be created only if > > if (device == NULL || ctx->derive_device_type != NULL) > > Now a new device is created unconditionally. Thanks a lot for the review. That makes sense. Will update them in v2. > > > + if (err < 0) { > > + av_log(avctx, AV_LOG_ERROR, "Failed to created derived " > > + "device context: %d.\n", err); > > + goto fail; > > + } > > + device_is_derived = 1; > > + > > desc = av_pix_fmt_desc_get(outlink->format); > > if (!desc) { > > err = AVERROR(EINVAL); > > -- > > 2.35.1.windows.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".
next prev parent reply other threads:[~2022-06-30 2:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-29 6:32 [FFmpeg-devel] [PATCH 1/3] avutil/hwcontext: add a function to get the AVHWDeviceType Tong Wu 2022-06-29 6:32 ` [FFmpeg-devel] [PATCH 2/3] avfilter/vf_hwmap: get the AVHWDeviceType from outlink format Tong Wu 2022-06-29 7:00 ` "zhilizhao(赵志立)" 2022-06-30 2:31 ` Wu, Tong1 [this message] 2022-06-29 6:32 ` [FFmpeg-devel] [PATCH 3/3] avfilter/avfiltergraph: add an auto hwmap filter Tong Wu
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=SN6PR11MB2990817E829CB04A54475B05C0BA9@SN6PR11MB2990.namprd11.prod.outlook.com \ --to=tong1.wu-at-intel.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=quinkblack@foxmail.com \ /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