The most recent ColorLogic product versions are:

• CoPrA 2.4
• ColorAnt 2.0
• DocBees-ProfileManager 2.3
• DocBees-Reprofiler 1.6
• DocBees-ProfileTagger 1.1.1
• ZePrA 3.5.1

Note: To use the multicolor features, a multicolor license is needed.

This are the new MultiColor Modes:

• As a default method, the Strong mode is used. It corresponds to the calculation method for the separations, as used in earlier versions of CoPrA to 2.3. Here, much of the spot color is taken into account and the spot color channels are precalculated based on the measurement data. This leads to a strong use of spot color channels and accordingly to highly saturated colors in the printout. The disadvantage of this method is that the CMY separations may appear less smooth depending on the measurement data.
• In case you want a particularly smooth and harmonious color separation, you may select the Smooth mode. Here, however, not as much spot color is generated depending on the data set. The color results will be less saturated in the printout with this method than with the Strong method.
• The method Sparse Inks is very interesting for the packaging market.    In this case for example, the color separations are applied so that a red hue uses much of the special reddish spot color channel and very little to no magenta and yellow inks. Likewise, the black generation will be built at best level with only two to three colors. To archive this goal, the gray balance may use spot colors channels, too.
• Note: For the other methods, however, the gray balance is exclusively built with CMYK and without using spot colors inks. Unlike the methods Strong, Smooth and None, you have no influence on the black generation and the black point. These values are automatically calculated from CoPrA. Accordingly, when using the Sparse Inks mode, those setting parameters are grayed out.
  
• With the fourth method None, a multicolor printer or DeviceLink profile is created that consists of the desired number of channels (e.g. 7 channels). It is however, composed only of CMY or CMYK.
  Note: In packaging production, occasionally the wish exists that the original images and vectors built out of CMYK shall continue to be built with CMYK only despite conversion to a multicolor color space. In such a scenario, only spot colors in the DeviceN color space in the PDF file shall be converted in the large multicolor color space. With a CMYK-to-Multicolor DeviceLink profile created from CoPrA using the None multicolor mode and using the Preserve separation method, this is going to be possible. Especially when using this DeviceLink in combination with the ColorLogic ColorServer ZePrA and the spot colors conversion module.

After selecting an image (TIFF, JPEG or PSD), which is to be color converted, both a preview of the image as well as a possibly embedded profile is displayed.

You may choose to apply either a normal ICC conversion with source and target profile or a DeviceLink conversion. By the information of the embedded profile, you know that you should select this profile as your Source Profile. If you would like a DeviceLink conversion, you know which source profile your DeviceLink should have.

In a normal ICC conversion from the Source to the Target Profile, you will be able to specify the rendering intent for the conversion. Besides the typical four ICC rendering intents, a fifth option Blackpoint Compensation is available.

Note: It is the relative colorimetric intent with additional black compensation, as it is also known from Adobe Photoshop.

Want a DeviceLink conversion to perform?  Just select the desired DeviceLink profile from the drop-down menu of the Source Profile. Other options, such as the choice of the target profile or a rendering intent, is no longer necessary. These options are disabled accordingly.

Note: The image conversion supports coded and demo profiles, too. Coded profiles are those created with CoPrA SP (serialized profiles). In this way, you can evaluate the profile quality from either coded or demo profiles when converting images. If using the Embedd target profile option, it is possible that a coded profile needs to be embedded in the converted image file. In order for other applications to correctly display the converted files, CoPrA will decode a coded or demo profile and embed it with a smaller grid size in the converted image. Note, however, that you can not use this profile for production purpose, because the profile quality is reduced. For this reason, such profiles are marked as LOW QUALITY VERSION FOR DEMO ONLY in the file name.

• The Alternate Color Space in PDF files is not changed from CMYK to Lab in certain cases unless necessary.
  Note: This change is important for some workflows that used the Alternate Color Space for displaying of spot colors.
• Separation color spaces in PDF files are not changed to DeviceN unless necessary.
• Removed memory leaks that could lead to increasing memory usage of ZePrA.
• Fixed problems which happened after moving or deleting a spot color from a library. For example double clicking the last color in the list, an index error was raised.
• Fixed the bug that after moving a spot color to another library, that library was not saved automatically and the moved spot color could get lost.
• Support for RGB profiles for spot color conversion and fixed the spot color mixing in RGB.
  Note: This enables conversion of spot colors to RGB output devices like monitors, tablets and RGB printers.
• Improved error message when a pixel file is processed and a spot color is set to conversion by Alternate Color Space.
• Unused color spaces are removed from soft mask objects in PDF files.
• When embedding an profile into TIFF, the resource with ID 1039 is removed from the PhotoShop image resource block.
• Spot color names no longer get lost in CMYK+x PSD files.
• Support of PhotoShop image resource 1077 needed in newer Photoshop files to correctly handle colorant information.
• Fixed issues with ACO color tables
• Fixed the problem that when empty spot color libraries, which do not yet exist on the system, have been imported via Configuration import, the import failed. At the next program start, a file not found error was raised during initialization and ZePrA did not work properly.

Applications

(access to the download section of the applications is only available for registered users)