Doofus
Doofus
The reason I need the profile at all, is because when running Windows in HDR, Dolby Vision is way too bright (low target-peak) and I have to specify the `target-peak`...
You're confusing metadata passthrough and tone-mapping. Tone-mapping doesn't use `pq` transfer. The `d3d11-output` should be negated, both lines. And `target-trc`. Windows is gonna get all kinds of confused.
You need to choose between letting your TV use the metadata and mpv tone mapping. I'd suggest letting your TV do the work. Are you running Windows in HDR? If...
So this is about SDR to HDR?
I'm not sure hassn has adjusted the black point for that use case.
> The default target is SDR, so I'm not sure how this is an actual issue? > > If you want HDR + 2020, specify it in your config: >...
Also, using pq ruins the picture. I run windows in HDR and the picture degrades when increasing the gamut and/or using pq transfer.
> > using pq ruins the picture > > I suppose tonemapper should be turned off. And you need to force HDR context d3d11-output-csp=pq I don't think so. If I'm...
> > no mechanism to hook the metadata to the windows swapchain, like the Dolby addon for windows > > Yes, dynamic metadata is not supported, but still you should...
I currently have everything running with bt.2020 and pq, and I'm mostly satisfied with it. But with gpu-next, it isn't useable. I'm waiting to see what happens with the d3d11...