2 ms·
I wish more software developers understood these things. A lot of games IMO have been marred by this, usually you can see it via really bad banding in dark are
by DiabloD3 11y ago
I wish more software developers understood these things.
A lot of games IMO have been marred by this, usually you can see it via really bad banding in dark areas.
My recommendation? A working temporal dither implementation while baking it to sRGB yourself in the final stage of your pipeline.
My other recommendation? 10 and 12 bit output becoming the norm, which Rec 2020 is mandating and future HDMI and Displayport specs will be forced to support for proper 4k support (currently, no 4k TV or monitor being sold meets 4k compatibility requirements due to not supporting Rec 2020's colorspace nor colordepth) (HDMI 2.0 already supports Rec 2020, but does not mandate support for).
- anon4 11y ago12bit will be pretty awful to work with though. That will mean 36 bits per pixel, which doesn't fit into a whole number of 8-bit-bytes. Best to just bite the bullet and go 16bit for internal representation.
- DiabloD3 11y agoThat's how a lot of software that can handle 12 bit already does it. It is only baked to whatever format the display wants (yes, 12 bit displays exist, they are tens of thousands of dollars, and only used very sparingly during post-production). Presumably, it is either padded to 5 bytes, or two pixels are shoved into 9 bytes when shipped to the monitor.