FoLLgoTT

I got the same problem. But when I use the overload with refreshRate of CustomResolution() it works. With ColorFormat I never got it to work.

FrequencyInMillihertz is also wrong. It shows 60 Hz instead of 59,94 Hz. Only the PixelClock seems to make the difference and so the real refresh rate is correct. NVIDIA control...

Ok, I suspected that the cause is more inside Windows/drivers. Thank you for the answer.

> It could be the mastering colorspace primaries. Just to confirm, does `--gamut-mode=clip` make the difference go away? Yes, with clip the problem completely goes away.

@kasper93 I don't seen any difference anymore. Thank you! :-)

> You should try the gpu-next VO. See #9788 I already use gpu-next in my config. The problem is the same.

> I can't reproduce the clipping with bt.2446a and spline (param 0.15). Yes, bt.2446a with target-peak=auto darkens those ultra bright scenes better. But the picture has less contrast then bt.2339...

> Isn't this literally what `--hdr-compute-peak` does? I always use this option, but it doesn't make any noticable difference in those bright scenes. > Incidentally, in the past, we used...

> You cannot be serious right now. Even though HDR is available you do not use it, instead you tonemap ST2084 transfer to SRGB transfer. Of course I am. In...

> You do not "tonemap" here, you convert to SDR here, even though HDR is available due to a bug in gpu-next. Use > > mpv.com **--target-trc=pq --target-prim=bt.2020** --vo=gpu-next --gpu-context=d3d11...