From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/ffv1: Implement 2D RLE for remap
Date: Mon, 24 Mar 2025 02:53:27 +0100
Message-ID: <20250324015327.GO4991@pb2> (raw)
In-Reply-To: <5b9a3c4b-1b77-413f-9f7b-cd6c33bea02e@mediaarea.net>
[-- Attachment #1.1: Type: text/plain, Size: 2145 bytes --]
Hi Jerome
On Sat, Mar 22, 2025 at 06:54:25PM +0100, Jerome Martinez wrote:
> 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.
Ok, ive done some more tests
mul_count>1 is for fixed point in float and decimal mantisse*exponent
formats. This is also what the paper concentrated on that ive looked at.
Real world sensors return integers (to the best of my knowledge), so these
fixed point in float cases are expected to be significant.
Sadly i have very little of any float32 material. So to test this i
had to generate my own. using the same tonemap and source from last time
i put a gbrp16 in the middle to make it 16bit fixed point in float.
and then encode this with a single static repeated dumb handwritten
mul_count=512 table vs the computer optimized mul_count=1 table optimized
for each slice. Still the mul_count=512 tables are 6% smaller overall
I see the same effect with a random gbrp10 image in float32, just that
the tables are all smaller.
I thus will move forward with commiting the code i have
I also have simplified the code more today.
Droping all mul_count > 1 code would require an alternative solution.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Modern terrorism, a quick summary: Need oil, start war with country that
has oil, kill hundread thousand in war. Let country fall into chaos,
be surprised about raise of fundamantalists. Drop more bombs, kill more
people, be surprised about them taking revenge and drop even more bombs
and strip your own citizens of their rights and freedoms. to be continued
[-- 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-24 1:53 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
2025-03-24 1:53 ` Michael Niedermayer [this message]
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=20250324015327.GO4991@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