- This topic has 64 replies, 4 voices, and was last updated 1 year, 5 months ago by
.
-
Posts
-
Yes it drifts if I don’t have vcgt enabled. With it enabled its fine.
I guess it is broken because the 3D LUT should contain grayscale calibration without the need for 1D LUT.
Yes it drifts if I don’t have vcgt enabled. With it enabled its fine.
I guess it is broken because the 3D LUT should contain grayscale calibration without the need for 1D LUT.
The it’s user missconfiguration (99% times this is what happens), not a failure of relative colorimetric intent
The profile describes display WITH vcgt applied, that how it’s measured.
It has been explained lots of times in Resolve/DWMLUT threads. If you embed VCGT in LUT3D, do not use system wide grey calibration. If you do not embed VCGT calibration, then VCGT needs to be applied system wide.
Why? because profile was made from measurements with VCGT applied.Yes but as I explained before I do not use any system wide gray calibration. I have sRGB IEC611966-2.1 loaded in DisplayCal profile loader. This is Windows default profile. So effectively I have gray calibration turned off. And I’m still getting this issue.
This was explained to me by Florian Hoch years ago that this turns off 1D LUT calibration.
I just wanted to post something here again. I haven’t tried much since last post but I did end up buying a i1Pro (an older model) a while ago. With that one I tried setting a few different observers that DisplayCAL has in their list and from all of those in the list the CIE2012 2″ observer (CIE2012 10″ was yet again very offset on a side note) was the one with the closest whitepoint match between the monitors (basically a visual match). Even with the whitepoints being matched by the device I still got the same color offsets that I have described before. Things I haven’t mentioned that I find weird are for example that red in sRGB calibration appear more saturated on my XF270HUA than when I calibrate my XV272UX which actually has more saturated reds out of the box. It should theoretically be able to produce the same red but when calibrated the saturation is different.
A side note, if you were such an outlier to human model vision… you just need to use as “source colorspace” in LUT3D creation a visually matched RGB colorspce with alternative xy coord for some minimum common colorspace like sRGB.
You can get those coords from a visually match in MS paint, feeding that RGB value (beware scalling!) to xicclu to get xy coordinate. Then make a synth profile, then freed it to LUT3D creator. You’ll have fixed 4 ends of the needle thread example. That will always match and if it does not it means that your device is not even close to linear, that some color cannot be expresed as some K1, K2 and K3 gains applied to native RGB primaries… and your need a igh end spectrophotometer and a very densely populated XYZLUT mesh to capture such bad behavior. It won’t be your eyes the issue.
I still need to test this as I think this might be the only way to fix the issue,
Still if anyone has any other idea please tell me ^^
Things I haven’t mentioned that I find weird are for example that red in sRGB calibration appear more saturated on my XF270HUA than when I calibrate my XV272UX which actually has more saturated reds out of the box. It should theoretically be able to produce the same red but when calibrated the saturation is different.
DisplayCAL or i1Profiler or any other software with the same functionality cannot calibrate reds or any other color. Just greyscale. Whatever it was before will be the same after VCGT grey calibration is loaded (unless some extreme VCGT where you loose 1/2 of a channel).
Then display os profiled and color coords measured and stored in profile so color managed apps will know how display behaves.
