From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] FFV1 float support
Date: Fri, 7 Mar 2025 01:58:58 +0100
Message-ID: <20250307005858.GX4991@pb2> (raw)
In-Reply-To: <b52af26f-852f-4a9c-a363-f1b0b3699de7@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1309 bytes --]
Hi Traneptora
On Thu, Mar 06, 2025 at 01:17:30PM -0500, Leo Izen wrote:
> On 3/6/25 11:37 AM, Michael Niedermayer wrote:
> > Hi
> > >
> > > I did mention this once before, but you should look into the Daala/Opus way
> > > of storing rawbits into a separate chunk at the end of the bitstream. It
> > > avoids polluting the range context with equiprobable bits.
> >
> >
> > I didnt like it, but it seems more popular
> >
>
> May also be worth considering the JPEG XL way, where each entropy-coded
> symbol is a "hybrid integer" of a token read from the entropy stream (ANS)
> followed by zero or more "raw bits" that are spliced in.
Adding a 3rd entropy coder is outside the scope of implementing float support
If such a encoder makes sense, that should be a seperate thing.
And if you belive it performs better than what we have, submit a
patch and benchmarks. Please make sure only to use material free of
patent issues, aka things that predate patents in a way that invalidates
the patents
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Let us carefully observe those good qualities wherein our enemies excel us
and endeavor to excel them, by avoiding what is faulty, and imitating what
is excellent in them. -- Plutarch
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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-03-07 0:59 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 [this message]
2025-03-06 21:20 ` Jerome Martinez
2025-03-07 1:13 ` Michael Niedermayer
2025-03-07 8:37 ` Jerome Martinez
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=20250307005858.GX4991@pb2 \
--to=michael@niedermayer.cc \
--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