Yes will do that, it may take a little time though When I get a chance I will also do a correction matrix for my I1D3 too but using the actual screen this time.To do this can there be a variation if using DisplayCal instead of HCFR ?
Manni: maybe a typo, but the I1 Pro 2 is Rev E, same for the EFI ES-2000 that actually is an X-rite I1 Pro 2 simply rebadged.
There has been a lot of misinformation and assumptions posted in the thread recently, so after running a few tests I'm going to try to correct a few mistruths...Regarding the i1pro2 driver:1) The driver for the i1pro2 doesn't make any difference for the Autocal, at least here. Both in V11 and V12, the i1pro2 is detected if you leave it on the calibration tile when you select it in the software, irrespective of the driver (2006 or 2009). No idea why that didn't work for me in the past, or why it still doesn't work for some.2) The 2009 driver is installed by Calman, so unless you want to replace the driver with an older version every time you install a new version of Calman, I don't see any reason to revert to the 2006 driver if you're running the latest windows build. The 2009 driver seems to be working just as well as the 2006 one.3) There is no accuracy issue with the 2009 driver here, I have no idea where that comes from, at least with Calman. There might be a bug in Autocal V12, but it doesn't seem to have anything to do with the driver itself.This is with Windows 10 Pro x64 build 1909 and with an i1pro2 REV E. Of course it could be different with older versions of Windows, or with unsupported clones of the i1pro2, but this is what I observe here. If you observe anything different, please list the exact model of your meter and windows version and provide actual measurements, so we can try to see if there are incompatible combinations.Regarding the results of Autocal V12 with the Spyder X:I haven't received a version of Calman supporting the X yet, but I've done some limited tests in Lightspace with my Spyder X unit. It has a 5dE error on white, and a 1-2dE error on red and green (I didn't measure blue). The reading from the Autocal itself show the same errors when you do a log with the i1pro2 and the Spyder X, so there is nothing that suggests that V12 is doing anything wrong with the Spyder X. It just reads what the Spyder X reports and takes it as reality.
@ManniNo correction matrix with DisplayCal?
You can create correction matrix in DisplayCAL or use correction matrix created elsewhere (like HCFR) with it too.
Special note about the X-Rite i1 Display Pro, ColorMunki Display and Spyder4/5 colorimetersThese instruments greatly reduce the amount of work needed to match them to a display because they contain the spectral sensitivities of their filters in hardware, so only a spectrometer reading of the display is needed to create the correction (in contrast to matching other colorimeters to a display, which needs two readings: One with a spectrometer and one with the colorimeter). That means anyone with a particular screen and a spectrometer can create a special Colorimeter Calibration Spectral Set (.ccss) file of that screen for use with those colorimeters, without needing to actually have access to the colorimeter itself.
I was referring to something subtly different. When you create a new session within colorHCFR, it is asked which correction matrix to apply from a predefined list. This list seems to be embedded in the meter (or driver?). For sure it changes with the meter. And it alters significantly the measures. One of them was able to make the spyder measures closer to the reference. I was asking if displaycal does the same and in that case which one Manni selected.