From: Niklas Haas <ffmpeg@haasn.xyz>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] Hardware purchase request: HDR monitor
Date: Sat, 1 Apr 2023 13:57:14 +0200
Message-ID: <20230401135714.GB16650@haasn.xyz> (raw)
Hi,
As some of you might know, I develop HDR->SDR tone mapping methods under
the libplacebo project, which is also available in FFmpeg as a video
filter (vf_libplacebo) and to my knowledge currently represents the
highest quality method of tone-mapping HDR to SDR with a filter.
I would like to further improve the quality of these algorithms, but I
am running into a lack of a proper HDR monitor to test on - most of my
existing work is done by a combination of guesswork, user feedback, and
staring at mathematical curves in a void.
I have done some research into the current state of the market and
determined that the current best compromise for an affordable,
HDR-capable OLED desktop monitor is the Samsung Odyssey OLED G8 Gaming
Monitor. (Which, despite the "gaming" name, accurately tracks PQ up to
~1000 nits peak at 2%, has wide gamut coverage, and a decent enough
resolution thus representing an ideal budget monitor for my workflow)
The current price on Amazon is listed as 1329 EUR:
https://www.amazon.de/Samsung-S34BG850SU-UWQHD-Aufl%C3%B6sung-Reaktionszeit-Bildwiederholrate/dp/B0BF5S7LSK/
If other developers agree to it, I would request to purchase this with
SPI funds.
_______________________________________________
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 reply other threads:[~2023-04-01 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 11:57 Niklas Haas [this message]
2023-04-01 15:00 ` Michael Niedermayer
2023-04-01 18:57 ` Kieran Kunhya
2023-04-01 23:34 ` Stefano Sabatini
2023-04-02 1:12 ` Michael Niedermayer
2023-04-05 13:48 ` Niklas Haas
2023-04-06 6:32 ` Stefano Sabatini
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=20230401135714.GB16650@haasn.xyz \
--to=ffmpeg@haasn.xyz \
--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