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>
Cc: "Clément Bœsch" <u@pkh.me>
Subject: Re: [FFmpeg-devel] [PATCH] Revert "avfilter/vf_palette(gen|use): support palettes with alpha"
Date: Sun, 30 Oct 2022 22:55:31 +0000
Message-ID: <DM8P223MB03652D145FF34A6D9A6FC527BA349@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DM8P223MB03653424D89B55C2D3720173BA349@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Soft Works
> Sent: Sunday, October 30, 2022 10:41 PM
> 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"
> 
> 
> 
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> > Clément Bœsch
> > Sent: Sunday, October 30, 2022 10:30 PM
> > 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 Sun, Oct 30, 2022 at 09:19:05PM +0000, Soft Works wrote:
> > [...]
> > > At the time of submission I did a lot of experiments and the
> > results
> > > seemed to be very useful:
> > >
> > >
> https://gist.github.com/softworkz/deef5c2a43d3d629c3e17f9e21544a8f
> > >
> >
> > On that page, the result of the command using palette* filters for
> > the
> > colored "O" gives a broken output, and it's not a simple bug, it's
> > more
> > fundamental. You cannot just just average the colors with different
> > levels
> > of alpha, it makes no sense.
> >
> > Do you understand why or do you need me to elaborate?
> 
> I understand why. I know that it's not perfect. But it's the best
> what's achievable within the way the filter is working.
> 
> But I wouldn't go that far as saying it would be "broken". I think
> the result is quite acceptable with regards to the method being
> using.
> 
> The patch I had submitted doesn't change the previous behavior
> without the use_alpha parameter.
> And when using the use_alpha parameter, the results are still
> useful in many cases - maybe not always.
> 
> But it don't see any reason to remove this just because it's not
> perfect. If you would have a patch to improve the results - that
> would be a different story and of course very welcome.

I'm really not an expert in image processing algorithms, and I 
haven't tried the following yet:
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?

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".

  reply	other threads:[~2022-10-30 22:55 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 [this message]
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
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=DM8P223MB03652D145FF34A6D9A6FC527BA349@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz@hotmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=u@pkh.me \
    /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