dantmnf / amdcolortweaks Goto Github PK

It shows artifacts after reboot with just primaries change... then tried reseting in many ways and it was not effective until loading a ICC profile like 709 reference or any other.

AMD has an API that lets you control the type of dithering.
I think having an option for that would be a great addition.

On transfer a option for HLG would be nice.

ICC profiles doesn't work after pc restart/shutdowns. Gotta reapply settings after every startup.

Whichever ICC profile I apply with AMD Color Tweaks, the TRC is always forced to sRGB, even when creating the ICC within DisplayCAL a different tone curve has been selected (e.g. Gamma 2.2).

I've attached an example screenshot, this was a measurement of an ICC profile with gamma 2.2 tone curve applied via AMD Color Tweaks. The measurement clearly indicates a sRGB tone curve instead of the intended 2.2 tone curve.

If possible, it would be desirable if AMD Color Tweaks either respects the TRC set by the ICC profile, or provide preset configurations for applying TRCs other than sRGB (such as gamma 2.2 or 2.4), similar to what the novideo_srgb program provides.

it is works until i close the game.

how about hdr

Even if P3 content is usually in a Rec2020 container, for IO (source/destination) completeness option for P3 is needed.

Thank you so much for your effort @dantmnf!

I'm trying to use it to clamp my wide gamut display (75% BT.2020, 99,88% DCI-P3, 100% sRGB coverage) to sRGB and Display P3. However I'm unsure if it's working correctly. I'm using Windows 10, version 21H2 and AMD Software: Adrenalin Edition 23.9.1.

Would you kindly provide an update on the current state and compatibility of the project?

This tool works flawlessly for me on RDNA2, calibration sticks after reboots, in fullscreen etc. and verification results with VCGT of the ICC profile applied are very good (BT.1886 gamma curve). It's really perfect for me.

Your other tool that makes use of Windows ACM also works great, but it seems there is a driver bug, as the driver doesn't parse the custom EDID information about non-available HDR correctly until GPU scaling in Radeon Settings is toggled once (Maybe there is some CLI workaround for it available? No idea.).