- This topic has 7 replies, 2 voices, and was last updated 3 years, 5 months ago by
.
-
Posts
-
The monitor which I use has a IC chip which stores the calibration of the monitor, as well as it’s own personal calibration software to calibrate the monitor. The software which comes with the monitor also has the ability to calibrate the display by means of a 3×3 or 5×5 grid. I’m not familiar with this, besides assuming that 5×5 is obviously better ?
There is no way to load an ICC profile into the software which is designed for the monitor; therefore, should I ignore calibrating with the software which comes with the monitor, as it’s main purpose is, if you are moving the monitor around and connecting it to other devices you don’t need to do re-calibration, and instead use DisplayCAL ?
When doing a calibration using DisplayCAL, since the monitor is capable of a fairly large percentage of Rec2020 as well as HDR, DisplayCAL did not calibrate give me a report which mentioned neither of those ?
Asus HW calibration software is garbage, also its user uniformity compensation in 3 or 5 grid (just brightness, no color). Plenty of examples in reviews (prad.de). Just in case it is an asus. HW & uniformity is very poor too, waste of money & time.
With a monitor with HW cal (all manufacturers) user must copy ICC/ICM obtained by calibration software to each computer where it is plugged.
***IF*** HW and calibration SW was superb and user chose as calibration target an standard/idealized display (like sRGB or Rec709+gamma2.4) you “may” try to assign such target profile as display profile (which is usually present on computers) because it will be very close to custom icc with post calibration measurements.If you do GPU calibration for greys (DisplayCAL) you can do the same. Just copy ICM to computers and ensure you use DisplayCAL LUT loader (in windows).
Also, exactly the same as in HW cal, OSD preset and OSD values must remain unchanged. This holds even if you use just 1 computer.HDR/Rec2020 does not work as you may think. To be “HDR compatible” (compatible is not the same as able to do HDR) display needs to accept HDR signal and use its internal mapping from Rec2020 & whatever TRC (PQ) to display’s actual capabilities. Making an ICC profile with DisplayCAL in display’s HDR preset will be mostly useless since you cannot disable intenal mapping from rec2020 content to actual display capabilities. Same for other kind of calibration software.
You may try to profile it at full native gamut and display configured to accept SDR signal. Then you can profile it and make a LUT3D from Rec2020/PQ “in” to display capabilities out and use it in compatible software like madVR. Since most HDR displays are not HDR at all, just HDR to SDR translation (“compatible”), or extremely poor FALD with halo issues, using it in SDR mode is a general recomendation. If you need to play HDR content use software translators to SDR native gamut as instructed (madVR LUT3D)If you do GPU calibration for greys (DisplayCAL) you can do the same. Just copy ICM to computers and ensure you use DisplayCAL LUT loader (in windows).
I assume under Color Management in Windows, the default profile if created in DisplayCAL is listed here ?
Also, exactly the same as in HW cal, OSD preset and OSD values must remain unchanged. This holds even if you use just 1 computer.
In other words, off ?
HDR/Rec2020 does not work as you may think. To be “HDR compatible” (compatible is not the same as able to do HDR) display needs to accept HDR signal and use its internal mapping from Rec2020 & whatever TRC (PQ) to display’s actual capabilities. Making an ICC profile with DisplayCAL in display’s HDR preset will be mostly useless since you cannot disable intenal mapping from rec2020 content to actual display capabilities. Same for other kind of calibration software.
You may try to profile it at full native gamut and display configured to accept SDR signal. Then you can profile it and make a LUT3D from Rec2020/PQ “in” to display capabilities out and use it in compatible software like madVR. Since most HDR displays are not HDR at all, just HDR to SDR translation (“compatible”), or extremely poor FALD with halo issues, using it in SDR mode is a general recomendation. If you need to play HDR content use software translators to SDR native gamut as instructed (madVR LUT3D)This I did not understand ?
If you do GPU calibration for greys (DisplayCAL) you can do the same. Just copy ICM to computers and ensure you use DisplayCAL LUT loader (in windows).
I assume under Color Management in Windows, the default profile if created in DisplayCAL is listed here ?
If you want to copy it to another computer it is placed in C:\Windows\System32\spool\drivers\color and shpuld be copied there (or double click to install whcih copies profile there)
Also, exactly the same as in HW cal, OSD preset and OSD values must remain unchanged. This holds even if you use just 1 computer.
In other words, off ?
No. After calibration settings must remain unchanged between computers.
HDR/Rec2020 does not work as you may think. To be “HDR compatible” (compatible is not the same as able to do HDR) display needs to accept HDR signal and use its internal mapping from Rec2020 & whatever TRC (PQ) to display’s actual capabilities. Making an ICC profile with DisplayCAL in display’s HDR preset will be mostly useless since you cannot disable intenal mapping from rec2020 content to actual display capabilities. Same for other kind of calibration software.
You may try to profile it at full native gamut and display configured to accept SDR signal. Then you can profile it and make a LUT3D from Rec2020/PQ “in” to display capabilities out and use it in compatible software like madVR. Since most HDR displays are not HDR at all, just HDR to SDR translation (“compatible”), or extremely poor FALD with halo issues, using it in SDR mode is a general recomendation. If you need to play HDR content use software translators to SDR native gamut as instructed (madVR LUT3D)This I did not understand ?
HDR compatible just means it accepts HDR signal (encoding)… but that display may not be able to display HDR content at all. Most “HDR” displays” are not able to display actual HDR content. They display the portion of SDR content they can using a translator.
Translation can be inside monitor (SDR panel, HDR=ON on OSD, HDR=ON on OS) or in software (SDR panel, HDR=Off on OSD and OS, a software LUT3D). DisplyCAL can make the 2nd one LUT3D.If you do GPU calibration for greys (DisplayCAL) you can do the same
?
No. After calibration settings must remain unchanged between computers.
Therefore both computers must have both their OSD the same ?
HDR compatible just means it accepts HDR signal (encoding)… but that display may not be able to display HDR content at all. Most “HDR” displays” are not able to display actual HDR content. They display the portion of SDR content they can using a translator.
Translation can be inside monitor (SDR panel, HDR=ON on OSD, HDR=ON on OS) or in software (SDR panel, HDR=Off on OSD and OS, a software LUT3D). DisplyCAL can make the 2nd one LUT3D.Is there a way to check how the display is doing the translation; how it’s doing it, and if it’s doing it ?
DisplayCAL can take the translation SDR to HDR signal and make it into a LUT3D depending on the nits or it doesn’t matter ?
If you do GPU calibration for greys (DisplayCAL) you can do the same
?
grey calibration is on profile. After calibration display behavior description is in profile. White & other settings are in monitor… so just do not modify OSD settings and copy ICM.
No. After calibration settings must remain unchanged between computers.
Therefore both computers must have both their OSD the same ?
OSD is on monitor. Just do not modify it when you plug that monitor to another computer.
HDR compatible just means it accepts HDR signal (encoding)… but that display may not be able to display HDR content at all. Most “HDR” displays” are not able to display actual HDR content. They display the portion of SDR content they can using a translator.
Translation can be inside monitor (SDR panel, HDR=ON on OSD, HDR=ON on OS) or in software (SDR panel, HDR=Off on OSD and OS, a software LUT3D). DisplyCAL can make the 2nd one LUT3D.Is there a way to check how the display is doing the translation; how it’s doing it, and if it’s doing it ?
Verify HDR behavior with HCFR or DisplayCAL for example. At some point PQ curve is going to clip.
DisplayCAL can take the translation SDR to HDR signal and make it into a LUT3D depending on the nits or it doesn’t matter ?
DisplayCAL tranalates the opposite way: HDR signal IN -> display SDR signal out. It uses a ICM as input for making LUT3D and user input display brightness ad reference HDR brightness.
Verify HDR behavior with HCFR or DisplayCAL for example. At some point PQ curve is going to clip.
How do I verify the PQ curve with DisplayCAL to see when the clipping occurs ?
