Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Jerome Martinez <jerome@mediaarea.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/ffv1: Implement 2D RLE for remap
Date: Sat, 22 Mar 2025 18:54:25 +0100
Message-ID: <5b9a3c4b-1b77-413f-9f7b-cd6c33bea02e@mediaarea.net> (raw)
In-Reply-To: <20250322174520.GN4991@pb2>

Le 22/03/2025 à 18:45, Michael Niedermayer a écrit :
> [...]
> Also I failed to find any worthy gain from adjusting mul_count so
> while the code in the encoder looks complex ATM alot of that can be
> dropped later if for example we choose to never put mul_count > 1 into
> the specification and ATM it makes no sense to put that in as theres no
> significant gain with the material i tested

I would prefer we don't put mul_count > 1 related code in FFmpeg, even 
if it is still experimental, without a use case demonstrating that this 
is useful.
_______________________________________________
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:[~2025-03-22 17:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20 22:30 Michael Niedermayer
2025-03-20 23:07 ` Lynne
2025-03-21 20:13   ` Michael Niedermayer
2025-03-21 21:12     ` Michael Niedermayer
2025-03-21 21:36       ` Michael Niedermayer
2025-03-21 22:22         ` Michael Niedermayer
2025-03-22 17:45           ` Michael Niedermayer
2025-03-22 17:54             ` Jerome Martinez [this message]
2025-03-24  1:53               ` Michael Niedermayer
2025-03-24 12:31                 ` Michael Niedermayer
2025-03-22 18:01 Michael Niedermayer

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=5b9a3c4b-1b77-413f-9f7b-cd6c33bea02e@mediaarea.net \
    --to=jerome@mediaarea.net \
    --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