From: SOHAM KUTE via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: SOHAM KUTE <10er36sohamk@gmail.com>
Subject: [FFmpeg-devel] [Vulkan] Clarification on hwdownload transfer formats in hwcontext_vulkan
Date: Tue, 13 Jan 2026 07:33:05 +0530
Message-ID: <CADb1QX6e5QnmZS1+08wdmzWmmH_HAHm6G0e3VdqCQm16MLz6yw@mail.gmail.com> (raw)
Hi,
I’m testing a Vulkan filter chain:
hwupload → scale_vulkan → hwdownload → format
and looking into the transfer path implemented in
libavutil/hwcontext_vulkan.c, specifically:
vulkan_transfer_get_formats()
Currently this function only exposes:
- hwfc->sw_format
- AV_PIX_FMT_CUDA (when enabled)
As a result, hwdownload sometimes fails format negotiation even though
the Vulkan → system memory transfer itself works.
I wanted to confirm the intended design:
1. Is the limited format list in vulkan_transfer_get_formats() intentional?
2. Should Vulkan hwdownload advertise more pixel formats, or is the
expectation that conversion must always happen after hwdownload?
3. If this is not by design, is extending this list something that would
be acceptable in a patch?
Before attempting any change, I want to make sure I’m not violating an
assumption in the hwcontext API.
Thanks,
Soham
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2026-01-13 2:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CADb1QX6e5QnmZS1+08wdmzWmmH_HAHm6G0e3VdqCQm16MLz6yw@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=10er36sohamk@gmail.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