Displaycal asus verification#

Why? because if Asus calibration fails here too that means that Asus software is unable to calibrate properly even if it has the good correction. You situation is more difficult because since there is no base EDR to copy you’ll have to interpolate 3nm to 1nm, only after that you can replace data.Īlso if you know which wrong EDR is used in Asus software, then you should try it to verify calibration with Displaycal using the same correction (if no available by default you can convert EDR to CCSS with argyll’s oeminst): check whitepoint, contrast and grey range (RGB + gray balance). Search in this forum for a thread about Eizo CS2731 by Midas. If you know which EDR is being used in Asus software you may try to forge a new EDR with the same headers but QLED spectral data. There is no QLED backlight support in Xrite or Asus software. PA32UGG looks like a QLED backlight (it does not matter leds size, just their light): Is there a different way to verify without any alterations from displaycal that I’m missing?

Displaycal asus verification#

However, the verification page wouldn’t let me run a verification unless I had a previous display profile selected at the very top. instead of the 6500k that I calibrated for.Įven weirder is that to my eyes the white balance seems visually accurate, is there a reason why the white balance would measure incorrectly? In the “verification” tab I was sure to check the “use simulation profile as display profile” box since the calibration is hardware loaded onto the monitor. What’s odd is that the results were spot on, except for the white balance which measured a flat 6000. I tried calibrating using this method for the first time today, and then used displaycal to verify the calibration inside of DaVinci Resolve.

I recently purchased an Asus ProArt display that has the ability to load a calibration directly onto the hardware chip of the monitor, however you have to use Asus’ own calibration software in order to do so.