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] [RFC] FFV1 float support
Date: Fri, 7 Mar 2025 09:37:06 +0100
Message-ID: <2908d53f-08d0-4b94-aa40-1db724901f22@mediaarea.net> (raw)
In-Reply-To: <20250307011314.GY4991@pb2>

Le 07/03/2025 à 02:13, Michael Niedermayer a écrit :
> [...]
> We have a generic remap table with the float code.
> 1. This is not really float specific, it could be used with integers

IMO it is important to have a clear split of "tools" available in the 
bitstream, so it can be used whatever is the pixel kind.
the spec should not have many "if".
As I have a practical example with 16-bit integer having 4 bits of 0 
padding, I'll give it a try.


> 2. Its per slice, so each slice can have a different table or none
>
> Any bits that are always 0 or 1 will be perfectly optimized out using
> that table. No mattter if LSB, MSB or in the middle
> even if every color is a multiple of 13 the remap table will still perfectly
> remove that and produce a continous range that is one thirteenth
>
> If you disagree, please explain how thats not already solving every
> variant and more ?

I'll do more tests on that.
_______________________________________________
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-07  8:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06  0:15 Michael Niedermayer
2025-03-06  2:14 ` Lynne
2025-03-06 16:37   ` Michael Niedermayer
2025-03-06 18:17     ` Leo Izen
2025-03-06 21:25       ` Jerome Martinez
2025-03-07  0:58       ` Michael Niedermayer
2025-03-06 21:20     ` Jerome Martinez
2025-03-07  1:13       ` Michael Niedermayer
2025-03-07  8:37         ` Jerome Martinez [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=2908d53f-08d0-4b94-aa40-1db724901f22@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