Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavfi: protection against premultiplied alpha (was: The patch series about premultiplied alpha)
Date: Mon, 11 Aug 2025 11:32:56 +0200
Message-ID: <aJm4yDIXXVw2Za-J@phare.normalesup.org> (raw)
In-Reply-To: <20250811111935.GB506966@haasn.xyz> <20250811111812.GB506149@haasn.xyz>

Niklas Haas (HE12025-08-11):
> I still think this series overall is a step in the wrong direction; and that
> our goal should be to move towards negotiation, and not towards some IMO hacky
> flag that is already deprecated on arrival.

In terms of work, this patch series is 5% trivial code easily removed
and 95% work that is necessary for real negotiation.

Which means this patch series is a step in the right direction anyway.

> However, I decided I would rather just implement the full negotiation at this
> point, to save ourselves the continued discussion; especially in light of the
> TC's inaction / radio silence.
> 
> Can you confirm that, if we implement full negotiation (thus allowing every
> filter to decide for itself which alpha modes it can ingest), your remaining
> your remaining objection to this series would be withdrawn?

Of course. I suspect you widely underestimate the amount of work
necessary for real negotiation, but I would be happy to be proven wrong
on this issue.

As I said multiple time, work on negotiation in libavfilter must start
with adding test coverage to avoid breaking the myriad of corner cases
that have been implemented over the years. I would be happy to review
your patches in this direction. Feel free to take over the old
preliminary ones I had posted a few years ago and never pushed.

But whatever you choose, negotiation or hackish flag, I will stand firm
on the fact that the default must be to protect users from creating
invalid output. 

Regards,

-- 
  Nicolas George
_______________________________________________
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".

      parent reply	other threads:[~2025-08-11  9:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-02 15:18 [FFmpeg-devel] The patch series about premultiplied alpha Nicolas George
2025-08-02 18:03 ` Nicolas George
2025-08-03 10:42   ` Niklas Haas
2025-08-03 10:50     ` Niklas Haas
2025-08-03 14:35     ` Nicolas George
2025-08-03 15:49       ` Nicolas George
2025-08-03 18:15         ` [FFmpeg-devel] [PATCH] lavfi: protection against premultiplied alpha (was: The patch series about premultiplied alpha) Nicolas George
2025-08-03 20:04           ` Michael Niedermayer
2025-08-03 20:50             ` Kacper Michajlow
2025-08-05  8:51           ` Niklas Haas
2025-08-05  8:58             ` Robert Nagy
2025-08-05  9:05             ` Nicolas George
2025-08-05  9:16               ` Nicolas George
2025-08-05  9:25                 ` Robert Nagy
2025-08-05  9:31                   ` Nicolas George
2025-08-05  9:31                     ` Robert Nagy
2025-08-11  9:18           ` Niklas Haas
2025-08-11  9:19             ` Niklas Haas
2025-08-11  9:32             ` Nicolas George [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=aJm4yDIXXVw2Za-J@phare.normalesup.org \
    --to=george@nsup.org \
    --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