From: Jerome Martinez <jerome@mediaarea.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/ffv1: Store slices*planes with the minimum bits needed after remap
Date: Wed, 2 Apr 2025 23:31:53 +0200
Message-ID: <72c55c0a-3bb2-44dc-a646-663421c20630@mediaarea.net> (raw)
In-Reply-To: <20250402211317.3079829-1-michael@niedermayer.cc>
Le 02/04/2025 à 23:13, Michael Niedermayer a écrit :
> [...]
>
> This improves compression as wrap around can be cheaper to reach a
> value.
There is an issue in FFV1 version <=3 with RCT, bit depth of resulting
luminance plane was 1 more than needed (RCT adds 1 bit to chrominance
but not to luminance, but with current spec all planes have 1 additional
bit), preventing in practice the wrap around for luminance, do I
understand well that the remap would mitigate such issue?
I wonder if with remap it would still be interesting to have a specific
code for having luminance without this additional useless bit, or if we
just go with the remap.
Maybe it needs tests (performance impact of remap when not really useful
vs just keeping the right bit depth of luminance? would remap be faster
if we keep the right bit depth of luminance?).
Jérôme
_______________________________________________
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-04-02 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 21:13 Michael Niedermayer
2025-04-02 21:31 ` Jerome Martinez [this message]
2025-04-03 0:07 ` Michael Niedermayer
2025-04-03 0:35 ` 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=72c55c0a-3bb2-44dc-a646-663421c20630@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