Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Revert "avfilter/vf_palette(gen|use): support palettes with alpha"
Date: Mon, 31 Oct 2022 15:11:13 +0000
Message-ID: <DM8P223MB03655C1302505694CBECD326BA379@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <Y1+qDCehfrC+0Fzy@ssq0.pkh.me>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Clément Bœsch
> Sent: Monday, October 31, 2022 11:57 AM
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] Revert
> "avfilter/vf_palette(gen|use): support palettes with alpha"
> 
> On Mon, Oct 31, 2022 at 01:43:11AM +0000, Soft Works wrote:
> [...]
> > > > > The patch I had submitted doesn't change the previous
> behavior
> > > > > without the use_alpha parameter.
> > >
> > > Yes I noticed, but unfortunately I'm reworking the color distance
> to
> > > work
> > > in perceptual color space, and the way that alpha is mixed up in
> the
> > > equation just doesn't make any sense at all and prevents me from
> > > doing
> > > these changes.
> >
> > If you want to implement a new color distance algorithm, it should
> > be either a new filter or a new (switchable) mode for the existing
> > filter.
> 
> Why?
> 
> > Photoshop has these different modes as well and it would
> > surely be useful, but I don't think it should be replacing the
> > existing behavior.
> >
> 
> There is no point in keeping a ton of complexity exposed as user
> options
> for something implementation specific. We offer no guarantee over how
> the
> quantization is expected to run.

Says who?

> > When it turns out that the use_alpha implementation doesn't fit
> > with your new color distance calculation and you add it as
> > an additional mode, then it would be fine IMO when the filter
> > errors in case it would be attempted to use that mode in
> > combination with use_alpha.
> 
> IMO The use_alpha option shouldn't exist in the first place, it
> should be
> the default behaviour because honoring the alpha is the correct thing
> to
> do. That's not what the option is currently doing though.
> 
> > > > Do you think it might make sense to put more weight on the
> > > > alpha value by tripling it? So it would be weighted equally to
> the
> > > > RGB value?
> > >
> > > You cannot mix alpha with colors at all, they are separate
> domains
> > > and you
> > > need to treat them as such.
> >
> > What's interesting is that I've followed the same (simplified)
> > way for adding a use_alpha option to vf_elbg and it provides
> excellent
> > results without treating alpha separately.
> 
> I don't know how the filter works and what it's supposed to do, but
> if
> it's indeed using the same approach as the palette ones, it cannot
> work.

Then it's magic, I guess.
The commands and results are on the same page I have posted.

And pngquant doing the impossible as well:

> Interestingly, pngquant which is supposed to have the best open source
> quantization algorithms seems to be using weights (albeit in a more 
> sophisticated way) and does not handle alpha separately for calculating 
> color distance, variance and averaging:

https://github.com/ImageOptim/libimagequant/blob/a16c9ca66a24158496da02d86925cc0167831205/pam.h#L163-L182 
https://github.com/ImageOptim/libimagequant/blob/a16c9ca66a24158496da02d86925cc0167831205/mediancut.c#L29-L49 
https://github.com/ImageOptim/libimagequant/blob/a16c9ca66a24158496da02d86925cc0167831205/mediancut.c#L449-L476

> That's not how it's going to work, sorry; I'm not going to increase
> complexity and maintenance effort for no gain. Implementing a correct
> support for the alpha will likely involve a revert of that commit
> anyway.

If you want to improve the way it works that's another story.

But at this point, we're talking about removal. And I disagree to that.

Best regards,
softworkz
_______________________________________________
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:[~2022-10-31 15:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 17:58 Clément Bœsch
2022-10-30 21:19 ` Soft Works
2022-10-30 21:30   ` Clément Bœsch
2022-10-30 21:37     ` Clément Bœsch
2022-10-30 21:41     ` Soft Works
2022-10-30 22:55       ` Soft Works
2022-10-31  0:29         ` Clément Bœsch
2022-10-31  1:43           ` Soft Works
2022-10-31 10:57             ` Clément Bœsch
2022-10-31 11:58               ` Paul B Mahol
2022-10-31 12:41                 ` Clément Bœsch
2022-10-31 15:11               ` Soft Works [this message]
2022-10-31 18:51                 ` Clément Bœsch
2022-10-31 20:41                   ` Soft Works
2022-10-31 21:58               ` Michael Niedermayer
2022-10-31 23:34                 ` Soft Works
2022-11-01 10:18                 ` Clément Bœsch
2022-10-31  2:09           ` Soft Works

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=DM8P223MB03655C1302505694CBECD326BA379@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz@hotmail.com \
    --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