Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Hardware purchase request: HDR monitor
Date: Sat, 1 Apr 2023 17:00:52 +0200
Message-ID: <20230401150052.GE1164690@pb2> (raw)
In-Reply-To: <20230401135714.GB16650@haasn.xyz>


[-- Attachment #1.1: Type: text/plain, Size: 1806 bytes --]

On Sat, Apr 01, 2023 at 01:57:14PM +0200, Niklas Haas wrote:
> 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/

here the same monitor seems to be for 1298€ with free shipping:
https://www.electronic4you.de/samsung-odyssey-oled-g8-g85sb-34-234606.html


> 
> If other developers agree to it, I would request to purchase this with
> SPI funds.

i think its for the community to decide this, my reply is not meant to
either say i agree or disagree, just wanted to reply with the cheaper
shop

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The misfortune of the wise is better than the prosperity of the fool.
-- Epicurus

[-- 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".

  reply	other threads:[~2023-04-01 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01 11:57 Niklas Haas
2023-04-01 15:00 ` Michael Niedermayer [this message]
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=20230401150052.GE1164690@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