Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: [RFC] Funded Task Ideas
Date: Sun, 2 Nov 2025 03:09:39 +0100
Message-ID: <aQa9Y0QwDbsl1f4R@neo> (raw)
In-Reply-To: <20251101233846.GB1030693@haasn.xyz>


[-- Attachment #1.1: Type: text/plain, Size: 1521 bytes --]

Hi Niklas

On Sat, Nov 01, 2025 at 11:38:46PM +0000, 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.
> 
> Thoughts?

I like the idea

Note, the SPI Vice President, who helped us with the STF stuff is possibly
on vacation ATM (not 100% sure). And also this is the first sw development task we do without
STF/GSoC/OPW. So there could be some extra delay.
I thus suggest if we want to do this, that we move forward with it ASAP so that
we dont add additional delay

thx


[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

It is what and why we do it that matters, not just one of them.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 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

      parent reply	other threads:[~2025-11-02  2:13 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
2025-11-02  2:09   ` Michael Niedermayer via ffmpeg-devel [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=aQa9Y0QwDbsl1f4R@neo \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    /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