vo_gpu_next: use reported display contrast value also in SDR mode - #16928
Conversation
It is useful in SDR mode to use correct target-contrast too.
OLEDs report min luminance of 0.0002 nits, while we couldn't set this with options due to limit. Set limit, so that we cannot exceed the hdr black value used in libplacebo in worst case scenario of target peak 10 nits.
|
On my SDR display, STATS page 1 shows HDR10
The value of Lines 821 to 833 in 233e896 |
If this is what is reported, sounds good. You can adjust contrast if needed. |
|
It's unreasonable to identify a 203 nits display as HDR10, #16702 may need optimization |
|
It's honestly a bit confusing since my monitor was marketed as being HDR ready but it was awful I never enabled it and in the last few years it became impossible to even enable in Windows but games were able to request it (like CoD which enabled it by default despite Windows being in SDR mode). Also, previously I set target-contrast to 950 (from the then capped 1000) to workaround some issues with gamma (currently shows 0.21 / 203 cd/m² but now that looks very wrong since some other changes that seem to have occurred. If I remove it, I see 0.049 / 203 cd/m². |
In which scenario looks wrong? Generally you can adjust |
Both look very wrong now and super bright/washed out, for now I've settled with target-contrast=7800 which isn't perfect. Setting to icc-profile-auto (sets that figure to 0) looks far more natural but blacks are getting crushed. I could probably find a better solution but with so much changing on MPV/libplacebo side and probably going to get a new monitor soonish, I'm not going to bother. EDIT: Decreasing target-peak significantly improved dark scenes but scenes with a lot of bright whites got messed up so just switched to setting higher contrast for now. |

No description provided.