From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] lavfi/vf_colorspace: Add SMPTE ST 2084 support
Date: Mon, 06 Feb 2023 10:51:53 +0100
Message-ID: <48f214ffb3a3be3519765fb0d3a16416bf73eb37.camel@haerdin.se> (raw)
In-Reply-To: <95e1040f9212ae3a5362a40f1dc838a642c810ad.camel@haerdin.se>
mån 2023-02-06 klockan 10:35 +0100 skrev Tomas Härdin:
> fre 2023-02-03 klockan 08:29 -0800 skrev Pierre-Anthony Lemieux:
> > On Fri, Feb 3, 2023 at 7:54 AM Tomas Härdin <git@haerdin.se> wrote:
> > >
> > > We need something better for proper tonemap support, but this is
> > > at
> > > least useful for getting the HDR discussion going.
> >
> > Below is a demonstration of two tonemap methods:
> >
> > https://www.sandflow.com/public/tone-mapping/index.html
>
> Does not work in Firefox. But it does work in Chromium. Looks like it
> could be static images only.
>
> Anyway what I feel bears discussion is whether we should add a field
> to
> AVCodecContext like "nits" that says how many nits the max values of
> integer pixel formats correspond to, and similarly for float formats
> what 1.0 corresponds to. The latter is usually 203 cd/m² but is it
> always? The link you posted appears to use 100 cd/m²:
>
> > l_sdr = 100;
Another thing: we probably need a float YUV format
/Tomas
_______________________________________________
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-02-06 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 15:53 [FFmpeg-devel] [PATCH 1/2] lavfi/vf_colorspace: Add support for 14- and 16-bit YUV Tomas Härdin
2023-02-03 15:54 ` [FFmpeg-devel] [PATCH 2/2] lavfi/vf_colorspace: Add SMPTE ST 2084 support Tomas Härdin
2023-02-03 16:29 ` Pierre-Anthony Lemieux
2023-02-06 9:35 ` Tomas Härdin
2023-02-06 9:51 ` Tomas Härdin [this message]
2023-02-06 14:53 ` [FFmpeg-devel] [PATCH 2/2 v2] " Tomas Härdin
2023-02-13 10:14 ` [FFmpeg-devel] [PATCH 1/2] lavfi/vf_colorspace: Add support for 14- and 16-bit YUV 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=48f214ffb3a3be3519765fb0d3a16416bf73eb37.camel@haerdin.se \
--to=git@haerdin.se \
--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