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: Tue, 5 Aug 2025 11:16:34 +0200
Message-ID: <aJHL8nVRBc_AoMa6@phare.normalesup.org> (raw)
In-Reply-To: <aJHJchHFpWBZVJWU@phare.normalesup.org>
Nicolas George (HE12025-08-05):
> > I will repeat myself briefly here that such a flag should be an opt-out, not
> > an opt-in. Supporting premultiplied alpha should be the default assumption
> > unless provable otherwise.
>
> Absolutely not.
>
> Do you dereference a pointer when you can prove it cannot be NULL or
> when you cannot prove it can be NULL? It is the same: if you cannot
> prove a filter produces a valid result, then we protect by default. It
> is already too much that it is not blocking when it is unspecified. On
> this I will stand firm.
Just an extra point:
Imagine we had done it opt-out as you suggest, and you were looking at
the list of >300 video filter source files.
Would you have thought to set the opt-out flag to drawbox?
I know you have the integrity to do so, so please take the time to think
about it and answer honestly.
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".
next prev parent reply other threads:[~2025-08-05 9:16 UTC|newest]
Thread overview: 16+ 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 [this message]
2025-08-05 9:25 ` Robert Nagy
2025-08-05 9:31 ` Nicolas George
2025-08-05 9:31 ` Robert Nagy
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=aJHL8nVRBc_AoMa6@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