Modules | |
| ICM2 CMM example | |
| This example provides a core color management example module that acts as an interface to Microsoft's Image Color Management (ICM2) library. | |
| Common code for all CMM examples | |
| The CMM examples share functions to call the sw_memory_api callback API provided by the RIP for allocation and deallocation. | |
| Custom color space CMM example | |
This example provides a core color management module that implements a collection of custom color spaces that may be used by the setinterceptcolorspace and setreproduction color operators. | |
| LittleCMS CMM example | |
| This example provides a core color management example module that acts as an interface to the open source LittleCMS color management library. | |
| Pure color preservation with ICC transforms | |
| This example module handles colors conversions that normally require an ICC CMM. | |
Beyond the built-in CMM, the Core RIP provides two APIs that extend the color management options:
Modules built using these APIs can be linked directly into an HHR RIP.
A CCS-CMM module augments the RIP with custom color spaces implemented in C callout functions. These may be used in the setinterceptcolorspace and setreproduction color operators. To configure the RIP to use a CCS-CMM module, use this fragment in the configuration PostScript:
An ICC-CMM module augments the RIP with an alternate ICC CMM that replaces the RIPs built-in ICC CMM. To configure the RIP with an ICC-CMM module, use this fragment in the configuration PostScript:
The SDK includes these examples of Core Color Management modules:
@note The memory allocation and deallocation funtions provided by the CMM API should be used by alternate CMMs whenever possible, rather than the functions supplied by the operating system. Failure to do so may result in difficulties when configuring the RIP for optimal memory performance, especially in memory constrained environments.