Peter · AI Assistant
Need help choosing the right path into ChromaChecker? I can guide you based on your role and workflow.
ChromaChecker is designed as a Central Repository for different kinds of data.
One of the key prerequisite steps before the system can be launched is to organize all assets that the system needs for proper data evaluation.
In Color Inspector there is a tab Assets - which lists all Color Libraries and Pallets that all other tools and all users can have access to. Additionally, there is the ability to import libraries from CxF files or from CC Public Library.
Take into account that Print Inspector requires Color Library or/and Color Palette as a source of references for spot colors.
Global Preferences are used by several ChromaChecker tools. Color Inspector and QuickChecker are the most important. If in your Spot Color Tracking you prefer to use one uniform tolerance - specify it there.
Print Inspector uses D50/2° Observer but the user may want to select any M-condition. In the Color Inspector potentially the user may need to specify any Illuminant ( including Custom), and select any Observer and M-condition.
For this purpose, the Color Specification tool makes it possible to create a predefined combination and save it with a unique name
Especially for QC tasks Projects are very practical. With the small subset of spot colors, substrate Projects can use auto-recognition mode. Learn more here.
ICC profiles are typical sources of reference data mainly for Print Inspector, but also other tools like Color Inspector, and Lighting Inspector. ChromaChecker ICC Public Profile Library offers moist of common profiles to be imported, but some of them might be already preinstalled. Go to ICC Profile Inspector and examine if all-important profiles are listed there, delete unwanted and upload all which are missed.
If you want to scan control strips the proper definition has to be accessible for the software. During installation, the basic default set is installed - but the user may need any additional - browse CC {Public Library or create own.
Please note that ChromaChecker offers control straps with Placeholders - that specific kind of control strips can have dynamic patches that the operator can assign to specific spot colors - a single template can support most of the production scenarios. Learn more before.
ControlStrip is just an ordered list of patches - to make it scannable by instrument a few additional parameters have de specified - e.g. physical patch dimension. Some instruments have additional requirements and formatting limitations. Some basic Scanning templates might be preinstalled - but any missed has to be created. Of course, all custom charts require manual creation. Once the scanning template is created it can be downloaded as a PDF file (except iSis).
Substrates can be tracked by Print Inspector, Color Inspector (via Projects), or directly in Substrate Inspector.
If you want to use custom Lighting - create it in Lighting Inspector. Please note that if you want to evaluate Color Inconstancy Index or Metamerism Index in Custom Lighting — it has to exist in the system, and be selected in Color Inspector Global Preferences.
Also, perform an ISO3664 audit of all critical areas.
To track your Instruments - register all your Instrument Inspector Targets. Create a baseline to make the first fingerprint of each Instrument. Compare baselines to see if differences between Instruments are acceptable.
If you have iSis
Register Instrument Inspector Target
Additional information and Support Form is available for logged users.
