From: Dash Santosh Sathyanarayanan <dash.sathyanarayanan@multicorewareinc.com> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2 1/2] avfilter: add scale_d3d11 filter Date: Thu, 26 Jun 2025 05:24:15 +0000 Message-ID: <05d1ece3-f06f-4aa2-af31-60daf44d98a3@multicorewareinc.com> (raw) In-Reply-To: <CA+anqdzLd3V8+9QB3NHmnyDpkEQueBT52cbr00YmTxNVBjZYLA@mail.gmail.com> On 24-06-2025 13:26, Hendrik Leppkes wrote: + if (frames_ctx->sw_format == AV_PIX_FMT_NV12) { + frames_hwctx->BindFlags |= D3D11_BIND_VIDEO_ENCODER; + } The filter should be designed universally rather than expecting to be connected to something specific at its output. Whether or not the bind_encoder bind flag should be set, needs to be determined during negotiation of the output connection. The above change is in dxva2.c, when the decoder output surface is passed directly to supported encoder, it requires BIND_VIDEO_ENCODER flag to be set. This does not affect any intermediate steps. A surface with encoder bindflags set can be used as input for any supported filters as well (confirmed with the scale_d3d11 filter). This part is still not acceptable. You blindly set a flag based on what you need, if special flags on the context are needed they should be negotiated between the different components, guided by the users use-case and input, and not hardcoded based on an arbitrary condition of a pixel format. You are right, but the bind flags will have to be set before the D3D11 texture2D surfaces are allocated and I could not find a way to negotiate and set those either from the encoder or other components and even as a configurable decoder option. Do you have any suggestions? Appreciate the feedback. Thanks, Dash _______________________________________________ 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".
prev parent reply other threads:[~2025-06-26 5:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-24 7:47 Dash Santosh Sathyanarayanan 2025-06-24 7:56 ` Hendrik Leppkes 2025-06-26 5:24 ` Dash Santosh Sathyanarayanan [this message]
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=05d1ece3-f06f-4aa2-af31-60daf44d98a3@multicorewareinc.com \ --to=dash.sathyanarayanan@multicorewareinc.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