From: Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Timo Rothenpieler <timo@rothenpieler.org>
Subject: [FFmpeg-devel] Re: [RFC] Funded Task Ideas
Date: Sun, 2 Nov 2025 01:50:24 +0100
Message-ID: <68d8b1e4-29de-4f5b-9aa4-09e289f38e75@rothenpieler.org> (raw)
In-Reply-To: <20251101233846.GB1030693@haasn.xyz>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1175 bytes --]
On 02.11.2025 00:38, Niklas Haas via ffmpeg-devel wrote:
> Hi all,
>
> at VDD'25 multiple people discussed interest in the ability to improve the
> filter negotiation around hardware filters; specifically about avoiding
> the need to constantly set the pixel formats manually when going from HW to
> SW, and also automatically insert hwupload/hwdownload filters when needed.
>
> I raised the possibility of funding it via an SPI bounty, and received
> widespread approval.
>
> I am familiar with this code and have previously attempted solving this
> exact problem on my own time, so I feel like I have a good understanding of
> what needs to be done to make it possible.
>
> I would like to formally propose allocating a bounty of 10,000 EUR for this
> task; which would cover all necessary prerequisite changes (such as fixing
> the hwupload/hwmap), full negotiation of swformats, and automatic
> hwupload/hwdownload insertion.
Definitely one of the bigger pain-points when using FFmpeg with hardware
accelerated filter chains, specially when you start mixing different
flavours like Vulkan, VAAPI, CUDA, ... in one chain.
So I'm all for it.
[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3203 bytes --]
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-11-02 0:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 2:40 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-14 19:16 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-14 20:35 ` Michael Niedermayer via ffmpeg-devel
2025-10-14 22:28 ` Timo Rothenpieler via ffmpeg-devel
2025-10-14 22:52 ` Michael Niedermayer via ffmpeg-devel
2025-10-15 4:39 ` Kieran Kunhya via ffmpeg-devel
2025-10-15 8:31 ` Nicolas George via ffmpeg-devel
2025-10-16 9:28 ` Kieran Kunhya via ffmpeg-devel
2025-10-16 11:20 ` Michael Niedermayer via ffmpeg-devel
2025-10-30 19:42 ` Nicolas George via ffmpeg-devel
2025-11-01 23:09 ` Michael Niedermayer via ffmpeg-devel
2025-10-15 14:53 ` Nicolas George via ffmpeg-devel
2025-10-16 11:59 ` Michael Niedermayer via ffmpeg-devel
2025-11-01 23:38 ` Niklas Haas via ffmpeg-devel
2025-11-02 0:50 ` Timo Rothenpieler via ffmpeg-devel [this message]
2025-11-02 2:09 ` Michael Niedermayer via ffmpeg-devel
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=68d8b1e4-29de-4f5b-9aa4-09e289f38e75@rothenpieler.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=timo@rothenpieler.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