- This topic has 81 replies, 13 voices, and was last updated 5 months, 2 weeks ago by
.
-
Posts
-
The VCGT (same for MHC2) is very subtle, so it will be hard to see if it’s applied by ACM or not.
Did you also try my previous profile which should produce more noticeable changes? That is to understand what correction ACM actually applies.I missed your post with the linked icc. Tried it out and the 1D lut is definitely applied. Everything starts crushing black. In terms of inverting red and blue, do you mean swapping them? Blue should look red and red should look blue? If that’s the case, then that did not apply with this profile.
….
Just played around with creating profiles a bit more. I took my 2.2 flat gamma profile and used MHC2Gen to create two more profiles – one with –calibrate-transfer and one without. The one without –calibrate-transfer looks like the gamma matches pretty much exactly to my non MHC2 profile if I swap back and forth between them. The one with that flag looks like it changes the tone curve to the srgb tone curve. I can tell because I have a profile made with the srgb tone curve and if I swap between them they look almost identical. When I tested this earlier, I must have made a mistake because I thought both with the flag and without the flag looked the same, but they do not. I’m a little unsure why the one with the flag would look like srgb, but it’s calibration was done to 2.2 relative.
Now this is testing a game that isn’t colour managed. Not sure what I have on my pc that would be colour managed. I guess I could compare images in firefox to see what differences there are? Don’t know what applications are actually using the new Microsoft Advanced Color APIs that would take advantage of the MHC2 tag.
So I think I misunderstood how this was written for MHC2Gen sdr-acm [–calibrate-transfer]:
LUT: vcgt, or vcgt(sRGB transfer to device transfer) if –calibrate-transfer is specified
My understanding now is it uses the vcgt (in my case 2.2 relative calibration) if the flag is not applied, but it uses sRGB transfer to device transfer if –calibrate-transfer is specified
Hi all,
I recently got into calibrating since I owned a Ultrasharp monitor for many, many years that was my main one for play & work at home, and at work I have an Ultrasharp too. Never cared much about anything.
Prices dropped, I bought a gaming one since I really loved how the really really cheap ones now at 180Hz & GSync perform. I didn’t know much about P3, sRGB… and then when I got the monitor it was like “what the hell is this”.
I tried eyeballing it to my U2719D, succeded, but crushed my blacks. Also, I use my Dell at 45 nits, the 2 gaming ones I got can’t go below 120 nits on white at 0% brightness. I got some kind of photophobia, strong screen light hurts me unless ambient matches it.
Then I got a Spyder 2024 as that was the only thing I can get in Serbia, only one shop was selling it. Stock software didn’t work for any reason, didn’t care, went straight for DisplayCAL.
Now, before getting the Spyder, I used the ACM and set the sRGB ICM. Right now, I wonder if it’s possible to keep all calibration data, including gamma changes that reduce my white luminance from 120 nits to 50 nits like that, or I’m in full need of a LUT change for that?
Thank you all for all shared knowledge here. There’s some of us amateurs here that actually just want a normal looking screen, not doing photo/video work that appreciate it.
Hello Dani,
I have a RTX 3060Ti. The NVidia panel does have a slider. Should I use that instead of DisplayCAL’s GPU gamma settings?
I found it to work not really well though, but that was before I got the Spyder. Seems to wash everything out instead of lowering brightness.
In that case, let’s ignore the GPU slider.
Assuming the peak white is around 120 nits and the display tracks a sRGB gamma, the following profiles should reduce peak white to around 45 nits without black crush.
One is using VCGT and the other MHC2, as I’m not sure which one ACM prefers.
