From: Leo Izen <leo.izen@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/exr: tag gamma=1.0 output as linear light
Date: Thu, 17 Aug 2023 14:04:18 -0400
Message-ID: <27a30bdf-32d7-498e-b38c-15e250749328@gmail.com> (raw)
In-Reply-To: <4bec3985332b135433854d97cb551f8ef2a4285c.camel@haerdin.se>
On 8/17/23 08:59, Tomas Härdin wrote:
> ons 2023-08-16 klockan 01:20 -0400 skrev Leo Izen:
>> By default the OpenEXR decoder outputs linear light pixel data by
>> applying a gamma=1.0 transfer (i.e. a no-op). When it does so, it
>> should tag the data as linear so color-managed filters or other tools
>> can work with it correctly.
>>
>> Signed-off-by: Leo Izen <leo.izen@gmail.com>
>> ---
>> libavcodec/exr.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/libavcodec/exr.c b/libavcodec/exr.c
>> index fae1d08ab0..518066facf 100644
>> --- a/libavcodec/exr.c
>> +++ b/libavcodec/exr.c
>> @@ -2088,6 +2088,8 @@ static int decode_frame(AVCodecContext *avctx,
>> AVFrame *picture,
>>
>> if (s->apply_trc_type != AVCOL_TRC_UNSPECIFIED)
>> avctx->color_trc = s->apply_trc_type;
>> + else if (s->gamma > 0.9999f && s->gamma < 1.0001f)
>> + avctx->color_trc = AVCOL_TRC_LINEAR;
>
> I'm going to be difficult here and point out that gamma=0.99991 is not
> linear. It's probably linear *enough* most of the time, but also 1.0
> can be exactly represented by float so an equality check seems
> appropriate.
This exact check exists elsewhere in the source file. There's a branch
where it sets up a LUT if gamma is not between those values, and has a
no-op track otherwise - so in the event you request 0.99995 or something
of that form, the code that does the color conversion treats it as 1.0f.
- Leo Izen
_______________________________________________
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:[~2023-08-17 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 5:20 Leo Izen
2023-08-16 10:48 ` Paul B Mahol
2023-08-17 12:59 ` Tomas Härdin
2023-08-17 18:04 ` Leo Izen [this message]
2023-08-20 13:00 ` Tomas Härdin
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=27a30bdf-32d7-498e-b38c-15e250749328@gmail.com \
--to=leo.izen@gmail.com \
--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