Nouvelle release Chromapure.
Plus que 28 minutes pour faire une calibration 9x9x9
Je me souviens d'avoir mis plusieurs heures la dernières fois (il y a plus d'un an), avec une ID 3 PRO
De même la 2.5.7 (version actuelle) est la dernière avant la V3. L'upgrade V2 vers V3 sera facturé $79.
http://www.chromapure.com/news.asp
ChromaPure 2.5.4 Release Notes
New Features
Added support for the Lumagen 17x17x17 (4913 colors) LUT calibration
Added support for the Colorimetry Research CR-100 professional colorimeter.
See the article in our New Gear page about this new product.
Added support for the Minolta CL-200 colorimeter
Added a Test Gamut report
This report is available to all ChromaPure Standard users. It measures a broad sample of the gamut (215 colors) and generates a report that describes performance throughout the gamut. Use this to determine whether the display requires an LUT calibration. Running this report only requires an active meter and signal generator. The built-in signal generator may be used.
Improvements
Inspired by the need to support the new 17^3 Lumagen LUT, we implemented a much faster method for advanced auto-calibration. The new method reduces the time required to run an advanced auto-calibrate session by more than half. Using an i1Display Pro the time required to cycle through one pass of the color matrix is now approximately
125 Colors: 6 minutes
729 Colors: 28 minutes
4913 Colors: 194 minutes
When using a Klein K-10a or CR-100 the time required is now
125 Colors: 3 minutes
729 Colors: 13 minutes
4913 Colors: 90 minutes
We added support for additional gamma targets in the Gamma module.
Bug Fixes
When selecting the 75% of Rec. 709 Reference Gamut, the Advanced Color Management module remains fixed at Rec. 709.
Known Issues
If, for whatever reason, you want to run Advanced Auto-cal more than once, we recommend that you close ChromaPure and then re-start between attempts. There is a as-yet-unidentified problem when performing multiple runs of advanced auto-cal during the same calibration session. We are investigating the problem and hope to have a fix in a future release.
