- This topic has 161 replies, 25 voices, and was last updated 1 month, 3 weeks ago by
.
-
Posts
-
@noiremk2 Set your monitor profile in Windows to sRGB. Profile your monitor. Set that profile in novideo_sRGB. Enable clamp. Profile the monitor again. Set this new profile as your monitor profile in Windows.
Should I be doing that with the black offset at 0% or the 50% I usually use? (for the final profiling)
And should I be using the profile/test chart I just did, or do a new one?@noiremk2 Set your monitor profile in Windows to sRGB. Profile your monitor. Set that profile in novideo_sRGB. Enable clamp. Profile the monitor again. Set this new profile as your monitor profile in Windows.
Should I be doing that with the black offset at 0% or the 50% I usually use? (for the final profiling)
And should I be using the profile/test chart I just did, or do a new one?Verify your single profile first, Displaycal verify tab is good for that. Then you can see what kind of benefit a dual profile setup gives you. If your display is well behaved it will be likely that one profile is all you need accuracy-wise(low DeltaA) for sRGB content. This implies sticking to consistent BOO settings, more like BOO 100% than other settings.
Put it in a different way, for XYZLUT in novideo_srgb there is an internal conversion from XYZLUT to curves+matrix. The conversion results in a loss of accuracy. When given a curves+matrix profile instead there is no conversation and accuracy is maintained, because it’s 1:1.
<svg style=”display: none;”><filter id=”_videostyler_filter_”></filter></svg>
I guess it may be, but for my display curves+matrix is not working well.
It’s possible but not typical. Share verification reports and we can find out what’s going on.
A heads up to avoid Nvidia drivers higher than version 581.94 at thsi time, since it breaks novideo_srgb functionality: https://github.com/ledoge/novideo_srgb/issues/122
Is this project no longer supported, if so what are the alternatives people are using? Unfortunately rolling back drivers is not a feasible solution for gamers who need most current video game drivers. Thank you
Is this project no longer supported, if so what are the alternatives people are using? Unfortunately rolling back drivers is not a feasible solution for gamers who need most current video game drivers. Thank you
It seems there is a fork https://github.com/methlas/novideo_srgb/releases/tag/v4.2.1 but I use AMD so I cannot test it.
I created a fork of novideo_srgb: https://github.com/guzenco/msovideo_srgb. It uses MHC2 profiles to achieve results similar to novideo_srgb and additionally provides options for whitepoint calibration and HDR calibration (static metadata, whitepoint, and EOTF)
However, it produces the same results as novideo_srgb only when gamma (EOTF) calibration is set to sRGB, due to MHC2 limitations (matrix + 1D LUT control instead of degamma [1D LUT] + matrix + regamma [1D LUT]).
Using a different EOTF will cause desaturation or oversaturation depending on the deviation from sRGB (the main reason) and the difference between the target color space and the display’s native color space. Due to the nature of the problem, it can only be mitigated with matrix optimization, but it cannot be completely fixed.Also, this fork is not tied to Nvidia GPUs, because it uses MHC2 profiles. However, some users have problems with the latest Nvidia drivers (additional unknown color transformation occurs when clamp is active and ACM is disabled, enabling ACM resolves this).
Does Win 11 apply MHC2 also in SDR mode or only in HDR like Win 10?
Windows 11 applies MHC2 in both modes from the corresponding profiles (Windows separates profiles for SDR and HDR), and from what I know, this must be the same for Windows 10 (20H1) and later.
On my Win 10 test machine I have ICC Profiles and ICC Profiles (Advanced Color). Neither does anything in SDR mode when I test my MHC2 profile that invers red and blue. HDR inverts the colors.
