Esko 16 Pack Proof User Guide
Mainos
Mainos
04 - 2017
Pack Proof 16
User Guide
ii
Pack Proof
Contents
1. Copyright Notice........................................................................................................................................4
2. What is Pack Proof?.................................................................................................................................. 6
2.1 The Pack Proof Workflow .................................................................................................................. 6
2.2 Color Management ............................................................................................................................ 7
2.2.1 Devices and Color Spaces ....................................................................................................... 7
2.2.2 Devices' Profiles ....................................................................................................................... 7
2.2.3 Using Profiles for Color Management ....................................................................................8
2.2.4 Color Strategies ........................................................................................................................9
2.2.5 Rendering Intents .................................................................................................................. 10
2.2.6 The Color Management Database ....................................................................................... 12
2.2.7 PantoneLIVE ............................................................................................................................13
2.3 Rasterizing Vector Graphics to Bitmaps .........................................................................................13
2.4 Verification ........................................................................................................................................ 14
2.4.1 Choosing Color Deviation Tolerances .................................................................................. 14
2.4.2 Choosing a Verification Strip ................................................................................................ 17
2.4.3 Measuring with a Spectrophotometer .................................................................................20
2.4.4 Reviewing the Verification Feedback ....................................................................................20
3. Pack Proof Installation and Configuration.........................................................................................21
3.1 Licensing ............................................................................................................................................21
3.2 Installation .........................................................................................................................................21
3.2.1 Installation Overview ............................................................................................................. 21
3.2.2 Preparing for the Installation ............................................................................................... 22
3.2.3 Activating the Licenses .......................................................................................................... 23
3.2.4 Installing the Proof Server .................................................................................................... 23
3.2.5 Installing Pack Proof .............................................................................................................. 26
3.3 Configuration in the Automation Engine Pilot ...............................................................................29
3.3.1 Imaging Engine Configuration for Pack Proof ..................................................................... 29
3.3.2 Pack Proof Configuration ...................................................................................................... 30
4. The Proof for Contract Approval Task.................................................................................................32
4.1 General ..............................................................................................................................................33
4.2 Proofer ...............................................................................................................................................35
4.3 Transformations ............................................................................................................................... 36
4.4 PDF Objects ...................................................................................................................................... 38
4.5 Document Inks ................................................................................................................................. 39
4.5.1 Selecting Inks Manually .........................................................................................................40
4.5.2 Selecting Inks Using Selection Criteria .................................................................................41
4.5.3 Switching How You Select Inks ............................................................................................. 44
Contents
4.6 Color Management .......................................................................................................................... 45
4.6.1 Color Management for Standard Proof ............................................................................... 45
4.6.2 Color Management for Emulation Proof ............................................................................. 48
4.7 Output ............................................................................................................................................... 50
4.7.1 Color Managing your Proofer's White Ink ........................................................................... 56
4.8 Verification ........................................................................................................................................ 57
4.9 Summary ...........................................................................................................................................60
iii
1
Pack Proof
1. Copyright Notice
©
Copyright 2017 Esko Software BVBA, Gent, Belgium
All rights reserved. This material, information and instructions for use contained herein are the property of Esko Software BVBA. The material, information and instructions are provided on an AS IS basis without warranty of any kind. There are no warranties granted or extended by this document. Furthermore Esko Software BVBA does not warrant, guarantee or make any representations regarding the use, or the results of the use of the software or the information contained herein. Esko Software BVBA shall not be liable for any direct, indirect, consequential or incidental damages arising out of the use or inability to use the software or the information contained herein.
The information contained herein is subject to change without notice. Revisions may be issued from time to time to advise of such changes and/or additions.
No part of this document may be reproduced, stored in a data base or retrieval system, or published, in any form or in any way, electronically, mechanically, by print, photoprint, microfilm or any other means without prior written permission from Esko Software BVBA.
This document supersedes all previous dated versions.
PANTONE
®
, PantoneLIVE and other Pantone trademarks are the property of Pantone LLC.
All other trademarks or registered trademarks are the property of their respective owners.
Pantone is a wholly owned subsidiary of X-Rite, Incorporated.
©
Pantone LLC, 2015. All rights reserved.
This software is based in part on the work of the Independent JPEG Group.
Portions of this software are copyright
©
1996-2002 The FreeType Project (www.freetype.org).
All rights reserved.
Portions of this software are copyright 2006 Feeling Software, copyright 2005-2006 Autodesk
Media Entertainment.
Portions of this software are copyright
©
1998-2003 Daniel Veillard. All rights reserved.
Portions of this software are copyright
©
1999-2006 The Botan Project. All rights reserved.
Part of the software embedded in this product is gSOAP software. Portions created by gSOAP are Copyright
©
2001-2004 Robert A. van Engelen, Genivia inc. All rights reserved.
Portions of this software are copyright
©
1998-2008 The OpenSSL Project and
©
1995-1998 Eric
Young ([email protected]). All rights reserved.
This product includes software developed by the Apache Software Foundation (http:// www.apache.org/).
Adobe, the Adobe logo, Acrobat, the Acrobat logo, Adobe Creative Suite, Illustrator, InDesign,
PDF, Photoshop, PostScript, XMP and the Powered by XMP logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Microsoft and the Microsoft logo are registered trademarks of Microsoft Corporation in the
United States and other countries.
SolidWorks is a registered trademark of SolidWorks Corporation.
Portions of this software are owned by Spatial Corp. 1986 2003. All Rights Reserved.
4
Pack Proof
JDF and the JDF logo are trademarks of the CIP4 Organisation. Copyright 2001 The International
Cooperation for the Integration of Processes in Prepress, Press and Postpress (CIP4). All rights reserved.
The Esko software contains the RSA Data Security, Inc. MD5 Message-Digest Algorithm.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun
Microsystems in the U.S. and other countries.
Part of this software uses technology by Best Color Technology (EFI). EFI and Bestcolor are registered trademarks of Electronics For Imaging GmbH in the U.S. Patent and Trademark
Office.
Contains PowerNest library Copyrighted and Licensed by Alma, 2005 – 2007.
Part of this software uses technology by Global Vision. ArtProof and ScanProof are registered trademarks of Global Vision Inc.
Part of this software uses technology by Qoppa Software. Copyright
©
2002-Present. All Rights
Reserved.
All other product names are trademarks or registered trademarks of their respective owners.
Correspondence regarding this publication should be forwarded to:
Esko Software BVBA
Kortrijksesteenweg 1095
B – 9051 Gent [email protected]
1
5
2
Pack Proof
2. What is Pack Proof?
Pack Proof is a proofing software solution that enables you to proof your jobs on the most commonly used proofers in the market, using the proofers’ native language.
Pack Proof is integrated with Automation Engine, so you can send a job through your proofing workflow to the proofer without having to leave the Automation Engine Pilot.
On top of that, Pack Proof ensures color accuracy:
• Color management ensures color matching throughout your workflow, thanks to Esko’s
Color Engine Pilot.
• Verification allows you to add a color strip to your proof and, if you have a verification license (optional), to verify the strip's color accuracy using a measuring device and the Esko
Verification software.
2.1 The Pack Proof Workflow
6
1.
When sending files to Pack Proof's Proof for Contract Approval task , you can:
• Perform general file transformations to make sure the output is as expected (select the right page box, rotate/invert/mirror/scale the file as needed...).
• Color manage your file so that your proof accurately reflects what your press output will look like (using color management settings from Color Engine Pilot ).
•
Rasterize the vector graphics to continuous tone bitmaps (using Imaging Engine's
RIP'ing capabilities).
Rasterizing Vector Graphics to Bitmaps
on page 13.
• Set verification options to later verify your proof's color accuracy using Esko
Verification.
Pack Proof
2. The Proof for Contract Approval task sends the files to be proofed to the Esko Proof
Server .
3. The Esko Proof Server proofs the file on the proofer of your choice. This proofer can be one of many types of proofing devices supported by the Esko Proof Server.
4. If you have a verification license, you can verify that the colors on your proof match the colors you were expecting, using a
measuring device and the Esko Verification software
.
See the
Esko Verification documentation
for more information.
2.2 Color Management
Color management is making sure that colors are reproduced consistently at different stages of the printing process.
This consistency is especially important for specific "brand" colors, that have to look the same when printed on different substrates (cardboard, paper, plastic...).
2.2.1 Devices and Color Spaces
Different devices (a digital camera, computer monitor, proofer, press...) display or reproduce colors in different ways.
Colors in photographs are generally defined in the RGB color space (Red, Green, Blue), and monitors also use RGB to display colors.
Proofers and presses use CMYK (Cyan, Magenta, Yellow and Black -or "Key") for printing, and sometimes additional inks (for example Orange, Green and Blue, to be able to reproduce more colors, or one or two spot colors -generally Pantone inks- used in a particular file).
Files coming from a graphic designer may contain CMYK, spot colors and sometimes images in
RGB.
2.2.2 Devices' Profiles
Even within one color space, different devices can reproduce colors differently. For example, two CMYK proofers from different brands may print completely differently.
A device's gamut is the totality of the colors that device can reproduce (for example, the area shown in light green below).
2
7
2
Pack Proof
This is captured in the device's profile, which describes all the colors achieved when using different combinations of percentages from the base colors (RGB, CMYK, or CMYK + extra colors).
To create a profile for a press or proofer, you need to print and measure a profiling chart containing these combinations of percentages.
8
See the
Color Engine Pilot documentation
for more information about creating profiles.
Pack Proof support the following types of device profiles:
• Esko profiles, created in the Color Engine Pilot,
• ICC profiles, created in a third party application and written in a standard format.
2.2.3 Using Profiles for Color Management
You need to have a profile for each of your devices to perform color management.
Pack Proof
2
Note:
Proofers and presses' profiles need to reflect the device's exact printing characteristics (inks, substrate...).
So if for example you change your substrate, you need to make a new profile taking that substrate into account.
Once you have made the profiles, you can perform a controlled conversion of the colors between the different device profiles.
For example if you are printing a photograph, you need to convert its colors from the digital camera's RGB profile (the source profile) to the printer's CMYK profile (the destination
profile).
This means that every color in the source profile is converted to the closest possible color that can be reproduced by the destination profile.
Note:
If you want to proof a file that will be printed on your press, you are trying to reproduce your
press' colors on your proofer.
This means that the press profile is your source profile, and the proofer profile is your
destination profile.
2.2.4 Color Strategies
If you want to refine your color management, you can use color strategies.
A color strategy is a bundle of color management settings that contains at least the source
of the devices you are using, and can contain other color management
settings (for example a
spot colors and the background color, other settings for converting specific spot colors, etc).
Your company's color management expert can create these color strategies in the Color Engine
Pilot, and you can simply select the one you need in your proofing ticket.
9
2
Pack Proof
For more detailed information about Color Strategies, see the
Color Engine Pilot documentation
.
2.2.5 Rendering Intents
A
Rendering Intent is a part of your
that handles the conversion of
spot colors and of the background color.
Each of the four rendering intents available does this in a different way, so you should choose the one that is more adapted to the way you are printing and the result you want to achieve:
• Use the Relative Colorimetric rendering intent if you don't want to simulate the source background (the point that has 0% of all inks in the source profile).
This will proof your file as if the proofer substrate was exactly the same as the substrate defined in your source profile.
For example: your press prints on cream colored card stock whereas your proofer prints on bright white paper, but you don't want to simulate the cream background on your proof.
10
With this rendering intent, colors from the source profile that cannot be reproduced by the proofer will be converted to the closest color(s) the proofer can reproduce.
In some cases several colors will be converted to the same color, which means that you can sometime lose some detail, especially in dark saturated areas and the dark parts of gradations.
Pack Proof
2
Note that typically the proofer profile has a bigger gamut than the press profile, so there are not many colors that the proofer cannot reproduce.
• Use the Absolute Colorimetric rendering intent if you want to simulate the source background to get as exact a color match as possible.
For example: you do want to simulate the cream colored card stock used on your press on your proofer substrate, to see how the final output will look like.
As with the Relative Colorimetric rendering intent, colors from the source profile that cannot be reproduced by the proofer will be converted to the closest color(s) the proofer can reproduce, meaning you can sometime lose some detail, although there are typically not many press colors that a proofer cannot reproduce.
• Use the Perceptual rendering intent if you are not trying to get an exact color match but want the proof to look visually pleasing.
If there are colors from the source profile that cannot be reproduced by the proofer, this will shrink the source gamut to fit inside the gamut of the proofer, so that all colors are converted (even the colors already in the proofer's gamut), but the relationship between colors is kept.
11
2
Pack Proof
This means that colors won't be really accurate, but you won't lose detail in dark saturated areas or gradations.
This rendering intent is most commonly used in commercial printing (for newspapers, magazines, posters...).
• Use the Saturation rendering intent if you mostly want to make sure the colors on your proof are saturated enough.
Colors from the source profile that cannot be reproduced by the proofer will be mapped onto close saturated colors that are in the proofer's gamut.
This rendering intent is most commonly used for business presentations containing graphics, or cartoons/comics.
Note: You can only use a Perceptual or Saturation rendering intent if you are working with
source and destination profiles.
2.2.6 The Color Management Database
All your
and inks are stored in a color management database (also called "CMS database").
You install this color management database when installing Automation Engine. You can install it on your Automation Engine server or on another server (the server you install your color management database on is called the "resources server").
After this, the profiles, color strategies and inks in your color management database are automatically available in the
Proof for Contract Approval task
12
Pack Proof
2
Important:
You should also install the Color Engine Pilot when installing Pack Proof.
This will enable you to create your own profiles, color strategies and inks, and to access
(if you have a PantoneLIVE license).
2.2.7 PantoneLIVE
PantoneLIVE is a database of Pantone inks in the cloud. It contains information about how different tints of an ink look like, and how the ink will look like on different substrates.
Because it is in the cloud, the same color data is accessible to every actor of the packaging production, globally (while being protected by a login). This ensures that you get predictable and accurate color every step of the way, saving time and costs.
To use PantoneLIVE inks, you need the Color Engine Pilot and a PantoneLIVE license.
After logging on to the PantoneLIVE cloud from the Color Engine Pilot, you will be able to download PantoneLIVE ink books from the cloud, and use PantoneLIVE inks in your files.
Please see the
Color Engine Pilot documentation
for more information about accessing
PantoneLIVE ink books.
Note:
If you don't have a PantoneLIVE license, any PantoneLIVE ink in your files will be treated as an unregistered ink (an ink not present in your color database), and you will not be able to proof or RIP it accurately.
In this case you should ask the file's designer to replace the PantoneLIVE ink by an ink that is present in your color management database.
2.3 Rasterizing Vector Graphics to Bitmaps
Files coming from a graphic designer may contain vector graphics or "linework" (especially for fonts or logos).
Vector graphics are highly scalable without any loss of quality (as they are not based on pixels but on mathematical formulas), but they are not printable.
To be able to print those graphics, you need to rasterize them with a RIP (Raster Image
Processor). This means converting them to bitmap images, or "contones" (continuous tone images), which are based on pixels.
13
2
Pack Proof
Low-resolution bitmaps can look pixellated, but Pack Proof generates high-resolution bitmaps.
2.4 Verification
Once you have color managed and proofed your file(s), you may want to check the color accuracy of your proof. This is especially important for contract proofing, as it is a measure of the proof's quality that you can show your customers.
Provided you have a verification license, you can do this in Pack Proof the following way:
1. Before proofing, you define
(how close the colors on your proof
must be to the colors in your input file for you to accept the proof as color accurate).
2. When proofing your file, you add a
, containing patches of the separations present in your input file.
3. Once your file is proofed, you measure this verification strip in
Esko Verification
, with a
.
4. In Pack Proof, you get detailed
about whether the measured separations are within your tolerances, helping you decide to either accept or reject the proof.
Tip: You can also use verification to monitor your proofer's stability over time (for example by printing a test job with a verification strip at regular intervals).
2.4.1 Choosing Color Deviation Tolerances
Quantifying Colors
The Lab Color Space
Colors are generally defined by their position in the Lab color space, which is a 3D color model representing all colors visible to the average human eye (developed by the Commission
Internationale de l'Eclairage).
It is based on three axes:
• the L axis (going from 0 to 100) defines the lightness of the color (a dark color has a low L value, a light color has a high one),
• the
a axis (going from -128 to 128) defines how green or red a color is (a greenish color has a low
a value, a reddish color has a high one),
• the b axis (going from -128 to 128) defines how blue or yellow a color is (a blueish color has a low b value, a yellowish color has a high one).
14
Pack Proof
2
For example:
Color
light yellow dark green medium gray
Lab values
Lab (100, 0, 60)
Lab (15, -128, 0)
Lab (50, 0, 0)
Difference Between Colors: Delta E
The difference between two colors is the difference between their respective positions on the L, a and b axes. This difference is called the Delta E (or ), and is calculated using a mathematical formula.
15
2
Pack Proof
16
The more different two colors are, the higher the Delta E number is. Generally a human eye can perceive color differences that are above 2 Delta E.
Note:
There are several Delta E formulas, that have been developed at different points in time ( CIE76,
CMC, CIE94 and CIE2000).
• If your company is already using one of those formulas, we recommend that you use the same one.
• If not, you should use the most recent one, CIE2000, which is the best reflection of the visual difference between colors.
• However, if you are trying to verify a proof according to the ISO 12647-7 proofing standard, you should use the formula specified in the standard, CIE76.
Difference Between Colors: Other Measures
Apart from Delta E, there are additional color differences indicators, that measure other colors characteristics.
You can use those if you want to have a more comprehensive picture of how well your colors are reproduced, or to quantify a particular color problem of your press.
Delta CH
Delta H
Use this to measure the difference in saturation (or "chroma") between the colors in your job and the printed colors.
This is based on the positions of the two colors on the a and b axes in the Lab color space, and can be a good indication of whether the gray balance on your press is good or not.
Use this to measure the difference in hue between the colors in your job and the printed colors.
The hue is the angle between two colors relative to the a and b axes in the Lab color space.
Pack Proof
2
Delta T
Use this to measure the difference in colorimetric tone value between the colors.
Colorimetric tone value means that the dot gain is measured by a spectrophotometer instead of a densitometer.
This gives more information about the colors (for example 50% of a warm yellow and 50% of a cold yellow look the same to a densitometer, but different to a spectrophotometer).
This is only applicable to the primary colors (CMYK).
2.4.2 Choosing a Verification Strip
You can choose from different types of verification strips to add to your job.
Keep in mind that the type of strip you can use depends on:
• what is available on your Esko Proof Server (by default, the Esko Proof Server comes with a large number of strips),
you will use to measure your strip (as different spectrophotometers
support different strip types).
This means that depending on your way of working, you will see a certain subset of the strips mentioned below.
Esko Strips
• Esko Strip: this strip type contains the following CMYK patches:
• patches of C, M and Y at 100%, 70% and 40%,
• overprints of C and M at 100%, 70% and 40%,
• overprints of C and Y at 100%, 70% and 40%,
• overprints of Y and M at 100%, 70% and 40%,
• an overprint of CMYK at respectively 100%, 40%, 40% and 20%,
• an overprint of CMYK at respectively 40%, 100%, 40% and 20%,
• an overprint of CMYK at respectively 40%, 40%, 100%, 20%,
• patches of K at 0%, 20%, 40%, 70% and 100%.
17
2
Pack Proof
• Esko + Solid Colors Strip: this strip type contains the same patches as the Esko Strip type, plus a 100% patch for every spot color present in the job.
Note: When using an Esko + Solid Colors Strip, you must color manage your strip.
•
Esko Equinox Strip: this strip type is only available when you use a
containing an Equinox source profile.
For more information about Equinox, see the
Equinox documentation
.
Note: When using an Esko Equinox Strip, you must color manage your strip.
Industry Standard Strips
• Fogra strip types:
•
Fogra MediaWedge V3.0 XE 1Z
•
Fogra MediaWedge V3.0 XE 2Z
•
Fogra MediaWedge V3.0 XE 3Z
These industry standard strip types are widespread and used to check compliance with the
Media Standard Print rules (based on ISO 12647).
1Z has one line, 2Z has two and 3Z has three.
• IDEAlliance strip types:
•
IDEAlliance ISO 12647-7 2009
•
IDEAlliance ISO 12647-7 Control Wedge 2013 (2 lines)
•
IDEAlliance ISO 12647-7 Control Wedge 2013 (3 lines)
•
IDEAlliance ISO 12647-7 Control Wedge 2013 (4 lines)
•
IDEAlliance ISO 12647-7 Control Wedge 2013 (6 lines)
These industry standard strip types are widespread and used to check compliance with ISO
12647-7.
• Japan Color strip types:
•
Japan Color
•
Japan Color 54 (1 line)
•
Japan Color 54 (2 lines)
These strip types have 54 patches and are used to check compliance with the Japan Color standard.
• Ugra Fogra strip types:
•
Ugra Fogra-MediaWedge V2.2
•
Ugra Fogra-MediaWedge V3.0
These industry standard strip types are widespread and used to check compliance with ISO
12647-7.
18
Pack Proof
They consists of 72 CMYK patches, which correspond to the most important patches of the
ECI 2002 color chart.
Other Strips
• 3DAPv3 CMYK Wedge: this strip type is used to check compliance with the 3DAPv3 proofing specifications (based on ISO 12647-2 and ISO 12647-7).
• EFI Color Verifier Chart and EFI Color Verifier Chart US: these strip types come with Esko
Verification.
The EFI Color Verifier Chart US is used to check compliance with the SWOP specifications.
Strip Layouts
For each strip type, several strip layouts are available, each layout being designed for a type of spectrophotometer (i1, i1io, etc.).
Pack Proof automatically uses the correct strip layout, based on the spectrophotometer and strip type you selected.
For example, for the Esko Strip type, the following layouts can be used:
Spectrophotometer Strip layout
Epson
SpectroProofer
2
X-Rite i1io
HP DesignJet Zx100
X-Rite i1iSis
X-Rite SpectroScan
19
2
Pack Proof
Spectrophotometer
Strip layout
2.4.3 Measuring with a Spectrophotometer
After proofing your job with its verification strip on your Proof Server, you can measure it in
Esko Verification with your spectrophotometer.
Supported Spectrophotometers
Inline
• Epson SpectroProofer (X-Rite ILS20)
• Epson SpectroProofer (X-Rite ILS30)
• HP DesignJet Zx100 non UV
• HP DesignJet Zx100
Offline
• X-Rite i1Pro 2
• X-Rite i1Pro
• X-Rite i1iO
• X-Rite i1iSis UV
• X-Rite i1iSis
• X-Rite SpectroScan
• Barbieri Spectro Swing
• Barbieri Spector LFP Basic
Note:
Make sure the spectrophotometer you want to use is available on your Proof Server!
For example, if you want to measure with an X-Rite ILS30, make sure that the Proof Server workflow you are working with connects to an Epson SpectroProofer that has an X-Rite ILS30 spectrophotometer embedded.
2.4.4 Reviewing the Verification Feedback
In Pack Proof
You get feedback in the Pilot's Files and Tasks views:
• When sending the file(s) ready to be proofed to the Proof Server: the
Proof for Contract
Approval task has a Send to Proof Server subtask; it has a green check when the files have been sent to the Proof Server.
• After measuring and verifying your strip: you can see either Verification successful or
Verification failed .
You can see verification details in the log file (which color deviation tolerances and Delta E formula you used, which tolerances were met or not met...).
On the Proof
on the proof itself.
This report shows information relative to the proof and verification (the printer used, the date and time, the verification strip used, the tolerances and whether they were met...).
20
Pack Proof
3
3. Pack Proof Installation and
Configuration
3.1 Licensing
To use the Pack Proof functionality in Automation Engine, you need a Pack Proof license (in the form of a product key file).
If you don't have this license, you will not be able to
configure Pack Proof in the Automation
Proof for Contract Approval Task
For more information about the Pack Proof license, please contact your Esko representative.
3.2 Installation
3.2.1 Installation Overview
To use Pack Proof, you will need:
• Automation Engine,
• the Esko Proof Server,
• Pack Proof.
You can either install these applications on the same server, or on two or three different servers. For details, see:
• the
Automation Engine system requirements
• the
Esko Proof Server system requirements
• the
Pack Proof system requirements
Note: You should have already installed Automation Engine before starting to install the Esko
Proof Server and Pack Proof. See the Automation Engine installation documentation for details if needed.
1. Make sure you have the relevant DVDs.
• To install the Esko Proof Server, you need the Suite 16 Esko Proof Server Installation DVD.
• To install Pack Proof, you need the Suite 16 Imaging Engine Software Installation DVD.
Note: If you downloaded the software from
MySoftware.esko.com
, you will need to mount the corresponding .iso files as virtual DVDs, or unpack the .iso files first.
21
3
Pack Proof
2. Make sure you have the relevant licenses.
You need a product key file for Pack Proof 16 (which includes all necessary licenses). If you do not have a product key file yet, contact
Esko Customer Support
.
3. On all servers on which you want to install Esko software,
4. On your license server (which can be either your Automation Engine server or a central license server),
5. On the server on which you want to install the Esko Proof Server, perform the steps listed in
6. On the server on which you want to install Pack Proof, perform the steps listed in
3.2.2 Preparing for the Installation
Before you install Pack Proof 16 on your system, check the following:
• You need to have Administrator privileges.
• You need Internet access.
• Your computer must meet the minimum requirements for the installation, as described on
www.esko.com/en/SystemRequirements/
.
•
Data Execution Prevention (DEP) must not block the installation. See
Data Execution Prevention (DEP) Settings
on page 22.
• The Password Policy must not block the installation. See
How to Change the Password Policy
on page 22.
• You must make sure your anti-virus software is not blocking the installation or configuration.
How to Change the Data Execution Prevention (DEP) Settings
Data Execution Prevention (DEP) is a security feature that helps prevent damage from viruses and other security threats by monitoring your programs to make sure they use the computer's memory safely. Before installing Pack Proof, make sure that DEP does not block the installation.
1. In Control Panel, click System > Advanced System Settings .
2. Click the Advanced tab.
3. Under Performance, click Settings.
4. Click the Data Execution Prevention tab.
5. Select Turn on DEP for essential Windows programs and services only.
6. Click OK.
7. Restart the computer.
How to Change the Password Policy
A password policy is a set of rules designed to enhance computer security by encouraging users to employ strong passwords and use them properly. Before installing Pack Proof, make sure that the password policy on your system does not block the installation.
1. In Control Panel, click Administrative Tools.
22
Pack Proof
2. In the Administrative Tools window, double-click Local Security Policy.
3. In the Local Security Policy window, double-click Account Policies > Password Policy .
4. In the right pane, double-click Password must meet complexity requirements.
5. Select Disabled.
6. Click OK.
3.2.3 Activating the Licenses
Pack Proof 16 is protected with licenses. These licenses are distributed as a product key file
(in .html).
You need to activate the product keys in the product key file using the
Network License
Manager application, on the server that you are using as a license server (this can be either your Automation Engine server or a central license server).
You should have installed the Network License Manager as part of your Automation Engine installation. See the Automation Engine installation documentation if needed.
You need:
• A product key file for Pack Proof 16 (which includes all necessary licenses). If you do not have a product key file yet, contact
Esko Customer Support
.
• Internet access on the server that you are using as a license server.
• An Esko ID in order to activate the licenses. Get one at
http://www.esko.com/licensing/
CreateAccount
.
On the server that you are using as a license server:
1. Open the Network License Manager by going to Start > All Programs > Esko > Network
License Manager > Network License Manager .
2. In the Esko Network License Manager, do one of the following:
• click in the Click to activate your Product Key File area,
• drag your product key file in the area marked or drag your Product Key File here,
• click the Activate button.
3. Follow the instructions of the Activate License Wizard.
4. When asked about the product keys, choose I have received an HTML file containing my
Product Keys.
5. Click Browse to select the product key file.
6. When asked, fill in your Esko ID and Password.
7. Click Finish.
The licensed products you can use are now visible in the Network License Manager.
3.2.4 Installing the Proof Server
You need the Suite 16 Esko Proof Server Installation DVD for the installation. Use the following procedure to install the Esko Proof Server:
1. Open the Suite 16 Esko Proof Server Installation window:
3
23
3
Pack Proof
• If you insert the Suite 16 Esko Proof Server Installation DVD into the DVD drive, or mount the corresponding .iso file, the window appears automatically.
• If you unpacked a downloaded .iso file, or if the window doesn't open automatically, double-click setup.exe in the root folder.
2. Select the installation language.
3. Click Proceed to the installation.
4. On the Esko Proof Server 14.1 Installer page: a) If you are installing the Esko Proof Server on a separate server (not your Automation
Engine server), connect to your license server.
How to Connect to the License Server
on page 24 for details.
b) Run the system readiness check.
How to Perform the System Readiness Check
c) Proceed with the software installation.
How to Install the Proof Server
d) If you are installing the Esko Proof Server on a separate server, make sure that
Automation Engine can send files to the Proof Server share.
Giving Automation Engine Access to the Proof Server Share
on page 25 for details.
How to Connect to the License Server
1. On the Esko Proof Server 14.1 Installer page, click on Install, update or repair the License
Server (Network License Manager component).
2. Follow the instructions of the installation wizard.
3. Open the Network License Manager by going to Start > All Programs > Esko > Network
License Manager > Network License Manager .
4. In the Esko Network License Manager, go to Tools > License Client Configuration .
5. In the License Client Configuration dialog: a) Enter the name of the server that you are using as a
.
b) Click Apply.
c) Click Exit.
6. Close the Network License Manager to go back to the Esko Proof Server 14.1 Installer page.
How to Perform the System Readiness Check
Before you install the Esko Proof Server, a System Readiness Check is required. This checks whether the operating system is suited for installing and running the Esko Proof Server.
1. On the Esko Proof Server 14.1 Installer page, click on Run the Esko Proof Server 14.1
System Readiness Check.
2. At the end of the Readiness Check, read the resulting messages carefully.
3. If the Readiness Check resulted in a problem with:
Options Description
The password policy
The Data Execution Prevention (DEP)
.
24
Pack Proof
4. Click Exit.
How to Install the Proof Server
1. On the Esko Proof Server 14.1 Installer page, under Installation or upgrade the Proof
Server component, click Install or upgrade the Proof Server and Profiles components.
2. Follow the instructions of the installation wizard.
3. During the installation of Esko Profiles, when asked to select the setup type, choose
Custom.
Complete will install all features, which is not recommended. Only select Complete when you are not sure which printer devices you own.
4. Select the desired printer devices from the list if you have chosen Custom.
5. At the end of the Esko Profiles installation, click Finish.
6. During the installation of the Esko Proof Server, select Server and Client as the features you want to install.
7. At the end of the Esko Proof Server installation, click Finish, and restart your computer as directed by the installer.
Giving Automation Engine Access to the Proof Server Share
If you installed the Proof Server on a separate server (that has no other Esko software), you need to make sure that Automation Engine can send files to the Proof Server share.
Note: If you installed the Proof Server on the server where Automation Engine is installed, this is done automatically.
Do the following:
1. On the Automation Engine server, check under which user Automation Engine is running.
Automation Engine runs as a service under either a local user or a Windows domain user.
You can see which user that is:
• in Automation Engine's Server Admin, under System Account (see the Automation
Engine documentation for more details).
• in your Automation Engine server's Task Manager (in Processes, select Show processes
for all users, and check which user the bgmd.exe process runs under).
Tip: By default (if you haven't changed it when/after installing Automation Engine), this is the local user BGSYSTEM, with the default password BGSYSTEM.
2. On the server where you installed the Proof Server, locate the ProofFolder share in which
Automation Engine will send files to be printed by the Proof Server.
If you used the default installation location (C:\Esko), this is C:\Esko\ProofFolder.
3. Give the Automation Engine user Full Control on this share.
• If the Automation Engine user is a local user:
1. Make sure the same user exists on the Proof Server computer (with the same password).
3
25
3
Pack Proof
2. Open the ProofFolder's sharing properties (right-click it, select Properties and go to the Sharing tab).
3. Add the user to the share with full rights (click Share..., type the user name and click
Add, select Read/Write as Permission Level and click Share to confirm).
• If the Automation Engine user is a Windows domain user:
1. Open the ProofFolder's sharing properties (right-click it, select Properties and go to the Sharing tab).
2. Add the user to the share with full rights (click Share..., type the user name and click
Add, select Read/Write as Permission Level and click Share to confirm).
3.2.5 Installing Pack Proof
You need the Suite 16 Imaging Engine Software Installation DVD for the installation. Use the following procedure to install Pack Proof 16:
1. Open the Suite 16 Imaging Engine Software Installation window:
• If you insert the Suite 16 Imaging Engine Software Installation DVD into the DVD drive, or mount the corresponding .iso file, the window appears automatically.
• If you unpacked a downloaded .iso file, or if the window doesn't open automatically, double-click setup.exe in the root folder.
2. Select the installation language.
3. Click Proceed to the installation.
4. Under Imaging Engine/Pack Proof 16.0 installation, including related tools (Color
Engine Pilot, Curve Pilot, HD Flexo Screens and ScreenManager), click Install.
5. On the Imaging Engine 16.0 Installer page: a) If you are installing Pack Proof on a separate server (not your Automation Engine server or the server hosting your Esko Proof Server), connect to your license server.
How to Connect to the License Server
on page 26 for details.
b) Check and install the prerequisites.
How to Install the Pack Proof Prerequisites
on page 27.
c) Proceed with the software installation.
How to Connect to the License Server
1. On the Imaging Engine 16.0 Installer page, click on Install the Network License
Manager 16.
2. Follow the instructions of the installation wizard.
3. Open the Network License Manager by going to Start > All Programs > Esko > Network
License Manager > Network License Manager .
4. In the Esko Network License Manager, go to Tools > License Client Configuration .
5. In the License Client Configuration dialog: a) Enter the name of the server that you are using as a
.
b) Click Apply.
26
Pack Proof
c) Click Exit.
6. Close the Network License Manager to go back to the Imaging Engine 16.0 Installer page.
How to Install the Pack Proof Prerequisites
Before you install Pack Proof 16, you need to install the Pack Proof 16 prerequisites.
1. On the Imaging Engine 16.0 Installer page, click on Check and install the Imaging
Engine/Pack Proof System prerequisites.
This checks whether the operating system is suited for installing and running Pack Proof 16, and starts the Pack Proof 16 prerequisites installation.
2. If:
• you see an error message about the Windows version, your operating system is not suited for running Pack Proof 16. Read the
System Requirements
again and install Pack
Proof 16 on a suitable operating system.
• you see the message Ready to install the prerequisite components for the
Imaging Engine software. Do you want to start the installation?, click
Yes.
3. The installation wizard for the prerequisite components will check the licenses, list the prerequisite components to install on the system, request confirmation for installation and then install the required components.
Follow the instructions of the installation wizard.
The installation wizard will install the following components:
• Microsoft Visual Studio Redistributables
• Message Passing Interface service
If you are prompted to reboot your computer, do so and restart this installation procedure.
4. If the installer doesn't find a running Automation Engine 16 server on the local machine, you will see the Enter Server name window, prompting you to enter the name of the server running your Automation Engine.
Note:
• You should be able to access this server from your Pack Proof 16 machine.
• You can still use the local machine as Automation Engine server (if Automation Engine
16 is installed on it): start up Automation Engine, and leave the field in the
Enter Server
name window blank.
The installer then checks if the server you entered has a running Automation Engine 16 server.
If you get the following error:
ERROR - Imaging Engine requires
Automation Engine 16.0
The provided master server does not have
Automation Engine 16.0 running
Checked server: [yourservername]
then:
Automation Engine 16 is not running on the server you entered.
3
27
3
Pack Proof
If you get the following error:
ERROR - Imaging Engine requires
Automation Engine 16.0
The provided master server does not have
Automation Engine 16.0 installed
Checked server: [yourservername] (version
[yourserverversion])
then:
1. Check that you entered the server name correctly.
2. Make sure Automation Engine 16 is running on it.
3. Restart the Pack Proof 16 prerequisites installation.
Automation Engine 16 is not installed on the server you entered.
1. Check that you entered the server name correctly.
2. Install Automation Engine 16 on it.
3. Restart the Pack Proof 16 prerequisites installation.
5. Click Exit.
How to Install Pack Proof
1. On the Imaging Engine 16.0 Installer page, click Install the Imaging Engine/Pack Proof
16.0 products.
2. Follow the instructions of the installation wizard.
3. Read the End user license agreement carefully and select Yes, I accept the license
agreement.
4. When asked to select the products to install on this system, select System Components,
Imaging Engine 16, Color Engine Pilot 16, and the desired related products (the products available depend on your license).
• The System Components group cannot be deselected and will be installed on all systems.
• Installing Imaging Engine will install the Proof for Contract Approval task, and a basic version of Imaging Engine to RIP your files before proofing.
However, if you have also
a full Imaging Engine license, it will install a full
Imaging Engine, with the options covered in your license.
• The products' Common Components that are used by several products (for example the Color Management System) will only be installed once (each product's installer will check if the necessary components are present, and update them if necessary).
5. Select a Destination Folder for the chosen products or accept the defaults.
6. At the end of the installation, click Finish.
28
Pack Proof
3
3.3 Configuration in the Automation Engine Pilot
After installing all the software components required for Pack Proof, you need to launch the
Automation Engine Pilot and perform some configuration:
1. Configure the basic version of Imaging Engine that comes with Pack Proof, and that is used for RIP'ing your files.
Imaging Engine Configuration for Pack Proof
on page 29.
2. Configure Pack Proof itself.
3.3.1 Imaging Engine Configuration for Pack Proof
Pack Proof comes with a basic version of
Imaging Engine
the files that you want to proof. You need to configure it the following way:
1. In the Automation Engine Pilot, go to Tools > Configure .
2. Select Imaging Engines in the left pane.
3. Go to File > New or press the Insert key (on PC).
This creates an Imaging1 entry under Imaging Engines and shows settings in the right pane.
4. In the right pane's General tab: a) In Host Name, enter the name of the server running your Imaging Engine and press
Enter or Tab (or click the Connect button next to Imaging Engine).
b) Check that you see a green dot with the message Imaging Engine is up and running.
If you see...
a grey dot with the message
Imaging Engine is starting up on host
a red dot with the message
No license for Imaging Engine on host it means that...
you need to wait a few minutes before you can use Imaging Engine.
a red dot with the message
No
Imaging Engine available on host
your Imaging Engine license is missing.
Please check your licenses.
the server you have entered doesn't have Imaging Engine or even
Automation Engine installed.
Please check if you have entered the server name wrong.
29
3
Pack Proof
You may see other error messages in some cases, but you will always get some advice as to what you need to do (for example with the
Missing resource for Imaging Engine
on host message, you will get advised to Please reinstall the Imaging Engine).
Note: You can Stop and Start Imaging Engine from here for troubleshooting purposes, but this is generally not necessary, as Imaging Engine starts automatically, and will restart automatically in case of a crash or after being force quitted.
c) Set the Number of Workers. This is the number of parallel processes used to work on multiple pages of a file, or multiple files at the same time.
Note:
The maximum number of workers you can set depends on your license and on the number of cores on your server.
Please see the
system requirements page
for details.
5. If you are only using Imaging Engine for Pack Proof (you don't have a fully-fledged Imaging
Engine to output RIP'ed files), you don't need to configure the Settings tab, or the Queue tab.
6. In the left pane, select the Imaging1 entry, go to File > Rename and give it a meaningful name.
You can also select it and press F2 (on PC).
7. Go to File > Save or use Ctrl+S (on PC) to save your configuration.
3.3.2 Pack Proof Configuration
This configuration will connect your Automation Engine server (and Pack Proof) to your Esko
Proof Server, so that Pack Proof can send files to the Proof Server, for proofing on your device.
For more flexibility, you can connect to several Proof Servers, and have access to all the workflows configured on these Proof Servers. When sending files through the
Proof for
Contract Approval task, you can then select which workflow of which Proof Server you want to use.
Important: You need to perform this configuration before you can use Pack Proof.
1. In the Automation Engine Pilot, go to Tools > Configure .
2. Select Proof Servers in the left pane.
3. For each Proof Server that you want to connect to: a) Click Add at the bottom of the right pane.
b) In the New Proof Server pop-up, enter the name of the server on which your Proof
Server is running, and click Add.
30
Pack Proof
3
Note:
If you get an error message like The shared folder "ProofFolder" on the host is not writable for the user BGSYSTEM, it means that Automation Engine cannot access the Proof Server share (where it needs to send files to proof).
In this case, follow the steps in
Giving Automation Engine Access to the Proof Server Share
on page 25.
c) In the Status column, check that your Proof Server is Running.
You also can Remove the connection to a Proof Server if needed.
4. Go to File > Save or use Ctrl+S (on PC) to save your configuration.
31
4
Pack Proof
4. The Proof for Contract Approval Task
, you can use the Proof for Contract Approval task to:
• Perform general file transformations to make sure the output is as expected (select the right page box, rotate/invert/mirror/scale the file as needed...).
• Color manage your file so that your proof accurately reflects what your press output will look like (using color management settings from Color Engine Pilot).
on page 7.
• Rasterize the vector graphics to continuous tone bitmaps (using Imaging Engine's RIP'ing capabilities).
Rasterizing Vector Graphics to Bitmaps
on page 13.
• Set verification options to later verify your proof's color accuracy using Esko Verification.
For more information about Esko Verification, please see the
Esko Verification documentation
.
The Proof for Contract Approval task sends the ready-to-proof files to the workflow of your choice on the Esko Proof Server, who then proofs it on the proofer connected to that workflow. This proofer can be one of many types of proofing devices supported by the Esko
Proof Server.
Note:
To use this task, you need to have created a Proof Server workflow in the Esko Proof Client, and that workflow must:
• be connected to the Admin user,
• be connected to a physical proofer (you cannot use the predefined "Esko Linearization" workflow for example).
For information about creating a Proof Server workflow, please see the
Esko Proof Client documentation
.
Attention:
You can use several Proof Servers, but in this case, make sure that every workflow has a unique name, even across Proof Servers.
If there are workflows with the same name on several Proof Servers, you will not be able to send files to those workflows through Pack Proof.
Task Parameters
In the
Device field, select the imaging device
Then use the tabs at left to show more settings to fill in. See:
•
•
on page 35,
•
32
Pack Proof
•
on page 38,
•
on page 39,
•
on page 45,
•
•
•
Using the Proof Server Workflow Parameters
If you are using a Proof Server workflow that already has proofing parameters defined (for example the number of copies to print, or the rotation or scaling to apply to your file), those parameters will be filled in by default in the Proof for Contract Approval task, so that you don't have to go check them in the Proof Server workflow and copy them into the task.
Note: This is not the case if you are using a SmartName or a public parameter to select your
Proof Server workflow.
You can of course change those parameters as desired in the
Proof for Contract Approval
task.
4.1 General
1. Define what Page Box of the input PDF you want to proof.
You can either select Media Box, Trim Box, or insert a SmartName that must resolve to either media or trim.
After selecting your file's page box you will see its dimensions under the Page Box option.
2. If your input file is a multi-page PDF, select which Pages you want to proof: a) First select All pages, Odd pages only or Even pages only in the Pages option.
You can also insert a SmartName resolving to either All, Even or Odd.
b) Then you can refine your selection by entering page numbers or a Page Range.
You can separate page numbers by a comma, or use a dash to indicate a page range (for example 3,6-9). You can also use a SmartName resolving to page numbers and/or page ranges using this same format.
Note:
• Page numbers are always physical pages. If your document starts with page 5, you should not use 5 but 1 to get the first page.
• If you enter page numbers that are not part of your document, they will be excluded from the output (all the other valid pages will be proofed).
• If you enter the same page(s) more than once (for example 1,1-2), it/they will only be output once.
• Pages are proofed in the order of the document (entering 5-1 will be automatically changed to 1-5).
4
33
4
Pack Proof
3. If you want to invert your output so it is compatible with the output device or software system that will process it, click .
You can also click or Edit... to insert a SmartName that must resolve to 1 or true (to invert the output), or to 0 or false (to leave the output as it is).
Tip:
If that setting is already defined in your
, it will be filled in by default.
You can of course change it as desired.
4. If you want to mirror your output so it is compatible with the output device or software system that will process it, click .
You can also click or Edit... to insert a SmartName that must resolve to 1 or true (to mirror the output), or to 0 or false (to leave the output as it is).
If that setting is already defined in your Proof Server workflow, it will be filled in by default.
You can of course change it as desired.
5. If you want to add a SmartMark to your output file(s), select it in the SmartMark list, or use a SmartName that will resolve to the SmartMark name.
A SmartMark is a mark whose content is variable, so you can make it display information about that specific job. For example, you can include some of the parameters used during
RIP'ing in your output file(s) by using a SmartMark.
You need to: a) First create the SmartMark you want to use in PackEdge (see the SmartMarks section in the PackEdge manual for details).
You can create either:
• a SmartMark with proof-specific parameters,
to display this value from the Pack
Proof parameters:
Use this SmartMark parameter in
PackEdge:
Device
Image
Emulsion
V Scale
H Scale
Color Strategy
Source Profile the
whether you whether you output file(s)
you used
your output the
you applied to your the
output file(s) the
you color managed your input file(s) with the source profile contained in the color strategy you applied
34
Pack Proof
4
Use this SmartMark parameter in
PackEdge:
Destination Profile
to display this value from the Pack
Proof parameters:
the destination profile contained in the color strategy you applied the
Resolution
• another type of SmartMark (for example a corner mark).
If your PackEdge application is linked to your Automation Engine server, your SmartMark will automatically be saved in the correct location and will be available in Pack Proof.
b) Then select that SmartMark in your Proof for Contract Approval task.
The SmartMark will be added to each proof generated from your input file.
4.2 Proofer
to which the task sends your RIP'ed
output.
• In the Proof Server Workflow list, you can see all of the valid workflows found on the Proof
Server(s)
Note:
To be valid, your Proof Server workflow must:
• be connected to the Admin user,
• be connected to a physical proofer (you cannot use the predefined "Esko Linearization" workflow for example).
For information about creating a Proof Server workflow, please see the
Esko Proof Client documentation
.
Pack Proof checks whether the Proof Server and the selected workflow are available when defining ticket settings and when (re-)launching the task.
The task will end in error if it can't access the Proof Server workflow or if the workflow is invalid.
Attention:
If you are connected to several Proof Servers, make sure that every workflow has a unique name, even across Proof Servers.
If there are workflows with the same name on several Proof Servers, you will not be able to select any of those workflows here (the name will be greyed out).
You can:
35
4
Pack Proof
• select a workflow from the list,
• use SmartNames (that must resolve to the name of a valid Proof Server workflow),
• set the workflow using public parameters.
Tip:
If you select a workflow from the list, its proofing parameters (number of copies to print, rotation or scaling to apply to your file...), will be filled in by default in the
Proof for
Contract Approval task, so that you don't have to go check them in the Proof Server workflow and copy them into the task.
You can of course change those parameters as desired in the
Proof for Contract Approval
task.
4.3 Transformations
Use the Transformations settings to scale or rotate your output relative to your input file.
Tip:
If you are using a
that already has scaling and/or rotation parameters defined, those parameters will be filled in by default, so that you don't have to go check them in the Proof Server workflow and copy them into the task.
You can of course change those parameters as desired.
1. If you want to Scale your input file's contents, select either:
• Scale by percent and enter the vertical and horizontal scaling percentages to use (they must be between 10% and 1000%).
Note:
By default, you enter the vertical scaling percentage and the horizontal one is calculated automatically to keep the proportions.
If you want to enter the horizontal scaling percentage manually, click to unlink it from the vertical one first.
However, if you do this then link the percentages again, the last percentage you entered will be kept, and the other one will be recalculated automatically to keep the proportions.
• Fit to page size to fit your output to the substrate defined in your
, while keeping the proportions (this will fit it to either the width or the height of the substrate, while making sure everything is on the substrate).
• Fit to page width to fit it to the width of the substrate defined in your Proof Server workflow, while keeping the proportions.
to your output, they will be taken into account when fitting the
proof to the substrate's width or size.
36
Pack Proof
4
Note:
If you have chosen to print borderless in your Proof Server workflow, Pack Proof will take this into account when fitting your output to the substrate, and make your output slightly larger to cover the whole substrate width or height.
You can only print borderless if your proofing device supports it. Please check the
Esko Proof
Client documentation
and your proofing device documentation for more information about borderless printing.
If you don't want to scale your file's contents, leave Do not scale selected.
You can use SmartNames resolving to not (Do not scale), ByPercent (Scale by percent),
FitSize (Fit to page size) or FitWidth (Fit to page width).
When entering SmartNames for vertical and horizontal scaling percentages, they must resolve to the numerical value (without the % sign).
2. If you want to rotate your file, select the Rotation you want to apply here.
You can choose to either:
• use a fixed rotation (this can be 0°, 90° Counter Clockwise, 90° Clockwise or 180°; any other value will give an error),
• rotate your file if necessary to fit, or fit better, on the substrate (select
Minimal Media
Consumption). This can be useful when using narrow rolls of substrate for example.
If it did fit on the substrate already, this option makes sure that the largest dimension of the file will be placed in the substrate width, to use less substrate material when cutting.
37
4
Pack Proof
Note:
• If you have chosen to print borderless in your Proof Server workflow, the task will take the extra space into account when rotating your file to fit (or fit better) on the substrate.
• You can use a SmartName that resolves to 0, 90 (for 90° Counter Clockwise), 180, 270
(for 90° Clockwise), or minimal.
• When using a fixed rotation, you need to use a numerical value (ninety will not work).
• This is a public parameter, that you can fill in when submitting files through Shuttle.
4.4 PDF Objects
Use the PDF Objects settings to define:
• how to color manage RGB objects in your input file,
• what dot gain compensation to apply to your input file's images.
All parameters in this tab are public parameters, that you can fill in when submitting files through Shuttle.
1. In Default RGB Profile, specify the profile to use if no profile is specified for a certain RGB object in the input file. The default is srgb.icc.
You can use a SmartName that resolves to the full profile name.
2. Select Use PDF transfer curves if you want to use the dot gain compensation curves attached to the images in your input PDF.
These curves compensate for the unwanted characteristics of the device that created the images (scanner, digital camera...).
You can use a SmartName that resolves to true (to use the input file's curves) or false (to not use them).
3. If you experience issues with a font that doesn't look smooth enough at your selected resolution, your font may have font hinting errors.
Font hinting is the rendering of the outline (vectorized) font to pixels. For certain fonts, this rendering sometimes doesn't give a visually pleasing result, especially at low resolutions. In the image below, the top font has font hinting errors, the bottom font doesn't.
38
Pack Proof
Choose how to handle files containing font hinting errors:
• Leave Generate an error if the job contains font hinting errors selected if you want the task to end in error when encountering font hinting errors. You can also use a
SmartName resolving to true.
• Deselect Generate an error if the job contains font hinting errors if you want to output your file anyway, whether it has font hinting errors or not (your task will end with a warning). You can also use a SmartName resolving to false.
This may lead to reduced quality rendering of the text, but it will not generate incorrect characters in your output file.
4.5 Document Inks
Selecting Which Separations to Proof
Use the Document Inks settings to select which separations of the input file(s) you want to proof.
For example, you can use these settings to exclude technical and/or varnish inks from your output.
You can choose to proof either:
• All separations.
• A number of separations you select Manually.
• A number of separations you select by using selection criteria.
Selection criteria are rules that you define to select separations automatically for you when the task is launched on a file.
Tip: You can make the ink selection parameters public so that an operator can set them through Shuttle as needed for each job.
Selecting separations manually is the easiest option, but you can only do it on a file by file basis
(when you launch the task on a single input file).
Using selection criteria is more advanced but also more powerful than selecting separations manually, and you can do it anytime (when launching the task on one or more input files, when using the task in a workflow, when defining ticket settings...).
Therefore, we recommend that you first try selecting separations manually when running the task on individual files, then switch to using selection criteria to automate your workflow further.
Tip:
To get used to working with selection criteria, try the following on a few of your files:
1. select the separations you want to output manually,
2. then change Select Inks to by using selection criteria and see which rules have been created based on your manual selection.
on page 41.
4
39
4
Pack Proof
Handling Unregistered Inks
Unregistered inks are inks that are not present in your
is no information about these inks apart from their RGB values in the input file, they cannot be color managed or proofed accurately.
Therefore, we recommend you exclude them from the output, especially for contract proofing.
Choose what to do in case some unregistered inks are still in the list of inks to be proofed:
• If you want the task to end with a warning, leave
Generate an error if the job contains
unregistered inks deselected.
All the inks you chose to include in the output will be proofed, but the unregistered inks will not be color accurate.
• If you want the task to end in error, select
Generate an error if the job contains
unregistered inks.
In both cases, you will also see a message in the log.
Note: If your file contains
and you don't have a PantoneLIVE license, those
inks will be treated as unregistered inks.
4.5.1 Selecting Inks Manually
Note: You can only select inks manually when you are launching the task on a (single) file, not when you are defining a generic ticket without an input file.
When choosing to Select Inks Manually, you will see a table containing all of your document's inks, showing each ink's:
Ink Name
Ink Book
Ink Index
Spot Ink Index
If an ink book is not present in your color database, it will show here as
<unregistered "">.
The Ink index is the order in which the file's inks will be printed (the ink with ink index 1 is at the bottom of the document and will be printed first).
To find the ink index of a file:
1. select the file in the Automation Engine Pilot's Files view,
2.
click ,
3. in the Info dialog that opens, select Inks in the left panel.
The order of the inks at right is the ink index (the topmost ink has an index of 1, the second of 2, etc.).
Note that if you reorder the inks by one of the columns (for example by
Ink name), they won't be ordered by ink index anymore. You will need to close that dialog and reopen it to see the ink index order again.
The Spot Ink index is the order in which a spot ink will be printed (when counting only spot inks and not process inks).
40
Pack Proof
For example, if the first 4 inks of the document are CMYK, the first spot ink will have 5 as Ink Index but 1 as Spot Ink Index.
Ink Type
This can be for example Normal, Technical, Varnish...
Printing Method
If you have set a Printing Method for an ink it will be shown here (this can be for example Offset, Gravure, Flexo... or any custom printing method you configured).
See the Automation Engine documentation for more information about printing methods.
Select the ink(s) you want to proof, or select the toggle in the table header to select/deselect all inks.
You will see a table listing the Selected document inks, and another table with the Document
inks that are not selected.
Attention: If no ink is selected, you cannot launch the task.
4
4.5.2 Selecting Inks Using Selection Criteria
every time, you can define some rules to automatically
select certain inks in your input file(s).
You can do this:
• either when running the task on one or more files, or when creating a task ticket to use later,
• by choosing to Select Inks by using selection criteria in the Document Inks settings.
How Does it Work?
You select the inks to be output by checking a combination of criteria:
1. You define what to check. You can check any of the following ink characteristics in your criteria:
Ink name
Ink book
Ink index
The Ink index is the order in which the file's inks will be printed (the ink with ink index 1 is at the bottom of the document and will be printed first).
To find the ink index of a file:
1. select the file in the Automation Engine Pilot's Files view,
2.
click ,
3. in the Info dialog that opens, select Inks in the left panel.
The order of the inks at right is the ink index (the topmost ink has an index of 1, the second of 2, etc.).
41
4
Pack Proof
Spot ink index
Ink type
Printing method
Note that if you reorder the inks by one of the columns (for example by Ink name), they won't be ordered by ink index anymore. You will need to close that dialog and reopen it to see the ink index order again.
The Spot ink index is the order in which a spot ink will be printed
(when counting only spot inks and not process inks).
For example, if the first 4 inks of the document are CMYK, the first spot ink will have 5 as Ink index but 1 as Spot ink index.
This can be for example Normal, Technical, Varnish...
If you have set a Printing method for an ink it will be shown here
(this can be for example Offset, Gravure, Flexo... or any custom printing method you configured).
See the Automation Engine documentation for more information about printing methods.
For example, you can check whether the Ink book is process, whether the Ink name is yellow...
You can use as many criteria as you want.
2. You define how to combine your criteria into a rule. For example:
• If you want to output only process yellow, you should check for inks that match both of the criteria:
Ink book is process
Ink name is yellow
• If you want to output both all process inks and all yellow inks, you should check for inks that match
either of the criteria:
Ink book is process
Ink name is yellow
• If you don't want to output any process inks or any yellow inks, you should check for inks that match neither of the criteria:
Ink book is process
Ink name is yellow
How Do I Build Rules?
Build your rules the following way:
1. Choose how to combine the criteria in your rule:
• Select All of the following are true if you want to only select the inks that match all of the criteria you define.
• Select Any of the following are true if you want to select all the inks that match at least
one of the criteria you define.
• Select None of the following are true if you want to only select the inks that match
none of the criteria you define.
42
Pack Proof
2. Define your first selection criterion.
You can select an ink based on its:
• Ink name: you can define if it contains/begins with/ends with/is a piece of text
(alphanumerical characters), or if it is empty.
• Ink book: you can define if it contains/begins with/ends with/is a piece of text
(alphanumerical characters), or if it is empty.
• Ink index: you can define if it equals/is less than/is greater than the number you enter, or is is between the two numbers you enter (in this case the ink indexes you enter as boundaries are also selected).
• Spot ink index: you can define if it equals/is less than/is greater than the number you enter, or is is between the two numbers you enter (in this case the spot ink indexes you enter as boundaries are also selected).
• Ink type: you can define if it is a piece of text (alphanumerical characters).
• Printing method: you can define if it is a piece of text (alphanumerical characters).
For example, you could use:
All of the following are true
Ink book is designer
None of the following are true
Ink name is crease
None of the following are true
Ink type is Technical
Ink type is Varnish
to:
select all inks from the "designer" ink book exclude an ink called "crease" exclude all technical and all varnish inks
Tip:
• You can enter several values to check for: just use a semicolon (;) between them.
For example, to check for both inks called Cyan and inks called Magenta, choose Ink
name is and enter Cyan;Magenta.
• When launching the task on a file, you can also click to select one or more of the Ink
names/Ink books/Ink types/Printing methods used in your input file(s).
A criterion will automatically be created based on your selection.
3. Click + to add more criteria and define them.
To remove a criterion, click - next to it.
Tip: If you are launching the task on a single input file, you will see a table listing the Selected
document inks, and another table with the Document inks that are not selected under the rules you defined.
4
43
4
Pack Proof
Attention: If no ink is selected, you cannot launch the task.
4.5.3 Switching How You Select Inks
You can switch between the two methods of selecting inks (
and
), and this will keep the same inks selected.
Switching from Selecting Inks Manually to Selecting Inks Using Selection
Criteria
When switching from selecting inks manually to selecting inks using selection criteria, the task will translate your manual ink selection into rules, so that the same inks are selected (you can see them in the Selected document inks table).
The rules you get are based on the characteristics of the inks you selected.
For example, if you selected all the process colors but no spot color in your file, for an offset job, you will get the following rule:
All of the following are true
Ink name is Cyan;Magenta;Yellow;Black
Ink book is process
Ink type is Normal
Printing method is Offset
Note:
If you...
• first selected inks using selection criteria,
• then switched to manual selection without changing the selection,
• then switched back to selection criteria,
... then your rules will be kept.
If you did change the selection in manual mode, the task will automatically generate new rules.
Switching from Selecting Inks Using Selection Criteria to Selecting Inks
Manually
When switching from selecting inks using selection criteria to selecting inks manually, all the inks selected by the rules you defined (the inks in the Selected document inks table) become selected manually.
Note: You can only switch to selecting inks manually when you are launching the task on a
(single) file.
44
Pack Proof
4
4.6 Color Management
to your output file(s). To do this, you use a
containing your color management settings.
You can apply two types of color management, depending on the type of proof you want to make:
Standard Proof
If you are making a standard proof, you are trying to reproduce your press' output on your proofer as accurately as possible.
In this case, you should use a color strategy containing your
press profile as source profile
and your proofer profile as destination profile.
Color Management for Standard Proof
Emulation Proof
If you are working with both a regular press and a digital press, and you want to be able to move jobs between presses, you need to make sure they have comparable output.
This can be useful if you want to use your digital press instead of your main press to reprint a few copies of a job, or to print short run jobs (with the same results as on the regular press) in general.
In this case, you should make an
emulation proof, that takes both presses into account when proofing. It will:
• first simulate how your regular press prints on your digital press,
• then simulate that simulation on your proofer.
This will help you find out which colors can or cannot be reproduced on your digital press, as a digital press can have a narrower gamut than both a regular press and a proofer.
Color Management for Emulation Proof
on page 48.
4.6.1 Color Management for Standard Proof
If you are making a standard proof, you are trying to reproduce your press' output on your proofer as accurately as possible.
In this case, you should use a color strategy containing your
press profile as source profile
and your proofer profile as destination profile.
See
on page 9 for more information about color strategies.
You can either select an existing color strategy (that you have created in the Color Engine Pilot), or create a new (basic) color strategy on-demand.
Note that when creating a basic color strategy on-demand, you will only be able to use it for the current task (you will not be able to store it, edit it later or reuse it).
• If you have created a color strategy in the Color Engine Pilot, select it in the
Color Strategy
list.
45
4
Pack Proof
To be available in this list, your color strategy must be stored in the color database defined for your Automation Engine server (if your Esko software is set up correctly, the Color
Engine Pilot saved it in the right place automatically).
You can also select your desired color strategy through a public parameter, or using a
SmartName. The SmartName for the color strategy must resolve to one of the available color strategies.
The color strategies you can select depend on your proofing device:
• If your proofing device (connected to the
you selected) doesn't have a profile attached, you can select any color strategy whose destination profile
has the right ink set for the proofer (as shown in red below).
46
• If your proofing device has a profile attached, you can only select a color strategy that has that profile as destination profile.
Pack Proof
4
Note:
• We recommend you always use a proofer that has been profiled (for more accurate proofing, it should have been profiled or recalibrated within the last two weeks).
You can see when your proofer was last profiled, and manage your profiles, in the
Color Engine Pilot's Device Manager. See the
Color Engine Pilot documentation
for more information.
• If your proofing device has a profile attached and there is a recalibration for this profile, that recalibration will be applied when proofing.
You perform a recalibration when your proofer output has drifted compared to what it was when you created the proofer profile.
To recalibrate the proofer, you print and measure a recalibration chart in the Color
Engine Pilot. This creates a recalibration file that you can "apply" on your proofer profile to update it.
For more information about recalibration, please see the
Color Engine Pilot documentation
.
Tip:
If you are proofing files containing a white separation (for example for a white underprint) on an Epson Stylus Pro WT7900 proofer, and you want to color manage your white separation, make sure you select the color strategy you created for this purpose here.
Color Managing your Proofer's White Ink
• If you want to create a basic color strategy on demand: a) Select Create Custom Strategy... in the Color Strategy list.
b) Select a Source Profile and a Destination Profile.
Note:
If your input file contains a document profile, and you want to use that as the source, select Use document profile if available (or use a SmartName resolving to true).
If the input file does not contain a document profile, the Source Profile you selected will be used instead.
Important:
• If your proofing device doesn't have a profile attached, you can use any destination profile that has the right ink set for the proofer.
• If your proofing device has a profile attached, you can only use that profile as destination profile.
• If your proofing device has a profile attached and there is a recalibration for this profile, that recalibration will be applied when proofing.
c) Select a Rendering Intent.
47
4
Pack Proof
on page 10 for details on how each rendering intent handles the
spot colors and of the background color, and which to use in which case.
Note: You can only use a Perceptual or Saturation rendering intent if you are working with Esko source and/or destination profiles.
d) Click OK.
Once you have selected or created your desired color strategy, the task shows the Source and
Destination profiles used in the strategy.
4.6.2 Color Management for Emulation Proof
If you are working with both a regular press and a digital press, and you want to be able to move jobs between presses, you need to make sure they have comparable output.
This can be useful if you want to use your digital press instead of your main press to reprint a few copies of a job, or to print short run jobs (with the same results as on the regular press) in general.
In this case, you should make an emulation proof, that takes both presses into account when proofing. It will:
• first simulate how your regular press prints on your digital press,
• then simulate that simulation on your proofer.
This will help you find out which colors can or cannot be reproduced on your digital press, as a digital press can have a narrower gamut than both a regular press and a proofer.
1. Select Emulation Proof to display color management settings for an emulation proof.
2.
Under Analog Press, select your first color strategy .
This color strategy should have:
• your regular press profile as Source Profile (or the profile for a printing standard you want to match, for example ISOcoated_V2_eci.icc),
• your digital press profile as destination profile (Emulation Profile).
48
Pack Proof
To be available in this list, your color strategy must be stored in the color database defined for your Automation Engine server (if your Esko software is set up correctly, the Color
Engine Pilot saved it in the right place automatically).
You can also select your desired color strategy through a public parameter, or using a
SmartName. The SmartName for the color strategy must resolve to one of the available color strategies.
Note:
You will only be able to choose a color strategy with a destination profile that is the same as the source profile of the
.
To choose a color strategy with a different destination profile, you need to first select a second color strategy that has that profile as source profile.
3.
•
Under Digital Press, select your second color strategy
This color strategy should have: your digital press profile as Source Profile,
.
• your proofer profile as Destination Profile.
To be available in this list, your color strategy must be stored in the color database defined for your Automation Engine server (if your Esko software is set up correctly, the Color
Engine Pilot saved it in the right place automatically).
You can also select your desired color strategy through a public parameter, or using a
SmartName. The SmartName for the color strategy must resolve to one of the available color strategies.
The color strategies you can select depend on your proofing device:
• If your proofing device (connected to the
you selected) doesn't have a profile attached, you can select any color strategy whose destination profile has the right ink set for the proofer.
• If your proofing device has a profile attached, you can only select a color strategy that has that profile as destination profile.
4
49
4
Pack Proof
Note:
• We recommend you always use a proofer that has been profiled (for more accurate proofing, it should have been profiled or recalibrated within the last two weeks).
You can see when your proofer was last profiled, and manage your profiles, in the
Color Engine Pilot's Device Manager. See the
Color Engine Pilot documentation
for more information.
• If your proofing device has a profile attached and there is a recalibration for this profile, that recalibration will be applied when proofing.
You perform a recalibration when your proofer output has drifted compared to what it was when you created the proofer profile.
To recalibrate the proofer, you print and measure a recalibration chart in the Color
Engine Pilot. This creates a recalibration file that you can "apply" on your proofer profile to update it.
For more information about recalibration, please see the
Color Engine Pilot documentation
.
4.7 Output
Use the Output settings to define how many copies of your proof you want, and how to handle images that have a different resolution than the output resolution.
Note:
Pack Proof uses the output resolution defined in your
decide whether quality or speed is more important to you.
• If you have chosen High Quality in your Proof Server workflow, Pack Proof will output your file(s) at the maximum resolution supported by your proofing device (you can check this resolution in the Proof Client).
You would typically use this for your final output, where quality is much more important than speed.
• If you have chosen Standard in your Proof Server workflow, Pack Proof will output your file(s) at 50% of the maximum resolution supported by your proofing device.
• If you have chosen Fast, Pack Proof will output your file(s) at 25% of the maximum resolution supported by your proofing device.
You would typically use this for drafts, where you don't need high quality yet but want a fast result.
For more information, please see the
Esko Proof Client documentation
.
1. If you experience problems with jagged edges, for example in small text, you can set an
Anti-aliasing factor to smooth those edges.
In the example below, you can see the difference between output without anti-aliasing (on the left), and with anti-aliasing applied (on the right).
50
Pack Proof
4
You can adjust the amount of anti-aliasing applied by choosing a factor of either 2, 3 or 4
(note that using a higher anti-aliasing factor may slow down processing).
You can also set this with a SmartName resolving to None (if you don't need anti-aliasing), or to the anti-aliasing factor you want (for example 2).
Attention: Because anti-aliasing changes the output sampling to smooth the jagged edges, you cannot resample your images (with the Image Resampling option) if you use anti-aliasing.
2. If your input file contains images, the images' pixels may not map exactly to output pixels because:
• the images' resolution is different from the output resolution you chose,
• scaling and rotation effects change the size and placement of the images' pixels.
You then need to resample these images to be able to output them at the same resolution as the rest of the file.
In the Image Resampling option, choose the resampling method you want to use (you will have to make a trade-off between processing time and image quality).
• Choose From File to use the resampling method defined in the input PDF (this is the default option). This method can be either:
• the "nearest neighbor" algorithm, which keeps the image very sharp but can make it look jagged (pixellated but sharp). This is mostly recommended if you have small images with sharp lines/sudden differences in intensity, and/or you do not want your images to be fuzzy at all.
51
4
Pack Proof
52
This resampling method is very fast.
• the "PDF interpolation" algorithm, that smooths the image while resampling (see below).
Note: Most PDF files don't specify a preferred resampling method, so the default
("nearest neighbor" algorithm) is used. If you want to make sure that the "PDF interpolation" algorithm is used, choose
PDF Interpolation instead of From File in the
Image Resampling option.
You can also use a SmartName resolving to FromPDF.
• Choose PDF Interpolation to smooth the image while resampling.
With this method, you get images that are pixellated and fuzzy, so it is only recommended if you have small images with gradual differences in intensity, like photographs of nature.
Pack Proof
4
This is slightly less fast.
You can also use a SmartName resolving to PDFInterpolate.
• Choose Auto Resampling to upsample the images to an automatically calculated resolution (generally half or a third of the output resolution) before smoothing it.
When using this, images are a lot less pixellated and fuzzy.
53
4
Pack Proof
This method is quite slow but gives images of a good quality, so it is recommended in most cases (unless you want an extra sharp image, in which case you should choose
From File).
You can also use a SmartName resolving to ResampleAuto.
• Choose Full Resampling to upsample the images to the full output resolution.
This is the slowest method but gives the highest quality images (not pixellated and only slightly fuzzy).
54
Pack Proof
4
Use this if Auto Resampling doesn't give you the results you want.
Attention:
Resampling to full resolution can require significant amounts of memory when the output resolution is high (especially from 4000 dpi).
If you want to do this, we recommend that you have at least 8GB of RAM available for each worker (see the installation documentation).
You can also use a SmartName resolving to ResampleFull.
3. If you are proofing files containing a white separation (for example for a white underprint), and your chosen
is connected to an Epson Stylus Pro WT7900 proofer,
you can tweak how to proof the white objects in your file(s) with that proofer's white ink.
For example, you can use this to get a cooler or warmer white when printing on transparent or metallic foil.
To do this, select White Coloring and choose either:
• No Coloring if you just want to print the white objects using the proofer's white ink, without tweaking the white ink's color.
• Custom Values if you want to tweak the color of the proofer's white ink manually.
In this case, click Set Custom Values... and enter the CMYK values to add to the white ink.
• Values From Color Management if you want to use the color strategy you defined in
to tweak the proofer's white ink.
55
4
Pack Proof
Note:
This color strategy must have a white Extra Output Ink (called white) and map the white separation in your file(s) to this white output ink.
Color Managing your Proofer's White Ink
on page 56 for information about how to
create such a color strategy in the Color Engine Pilot.
You can also use a SmartName resolving to NoColoring, CustomValues or
FromColorManagement.
4. Enter the number of Copies you want to print (at least 1).
You can use SmartNames and/or public parameters.
Tip:
If the number of copies to print is already defined in your
number will be filled in by default.
You can of course change it as desired.
5. Select Keep job files for relaunch purposes if you want to be able to proof jobs a second time without having to RIP them again.
In this case, the files created for proofing will not be automatically cleaned up. When you don't need to keep them anymore, you will have to delete them manually from the \\[Esko
Proof Server]\ProofFolder share.
You can set this option with a SmartName resolving to true to keep the files, or false to discard them.
Note:
To re-proof files that you have kept using this option, do the following:
1. Double-click the Send to Proof Server sub-task that was run on the job you want to reuse.
2. This reopens the ticket with a limited number of settings. Change your desired setting as necessary (for example the number of Copies).
3. Click Launch.
If you didn't select the Keep job files for relaunch purposes, you will see The job cannot be reprinted as the files from the job were not kept when reopening the ticket.
4.7.1 Color Managing your Proofer's White Ink
If:
• you are proofing files containing a white separation (for example for a white underprint),
is connected to an Epson Stylus Pro WT7900 proofer,
... you can color manage your proofer's white ink using a color strategy, for example to get a cooler or warmer white on your substrate.
56
Pack Proof
To do this, open the Color Engine Pilot and do the following:
1. Add the following inks to the designer ink book:
• the white separation used in the file you want to proof (for example cool white),
• a generic white separation, that must be called white.
2. Create a color strategy that will color manage your file’s white ink: a) Add your generic white ink as an Extra Output Ink in your color strategy.
b) Map your file’s white ink (cool white) to your generic white output ink.
4
c) Make sure that Ink Mapping... and Extra Output Inks... are selected in your main color strategy dialog.
Tip: If you need more details to perform these steps, please see the
Color Engine Pilot documentation
.
When using this color strategy in Pack Proof, your file's white objects will be color managed so that they are "cool white" on the proof from your Epson WT7900 proofer (and not simply white).
4.8 Verification
verify the colors on your proof
once you have color managed and proofed your
file(s), you can add a
here.
Color verification is especially important for contract proofing, as it is a measure of the proof's quality that you can show your customers.
Note:
If you have recalibrated your proofing device, that recalibration will be applied to the verification strip too.
See
on page 45 for more information about recalibration.
1. Select Print verification strip if you want to verify your proof.
The other settings become available once you have selected this.
2. Select the Measuring Device you will use to measure your strip.
Measuring with a Spectrophotometer
on page 20 for a list of supported measuring
devices.
57
4
Pack Proof
Note: The Epson SpectroProofer ILS20 and ILS30 devices are not supported for measuring proofs with nesting or step and repeat.
3. In Strip Type, select the strip you want to print.
The list automatically shows all strips that are available on the
selected, and compatible with your Measuring Device.
on page 17 for more information about the verification strips.
Note: Pack Proof automatically uses the correct strip layout, based on the Measuring
Device and Strip Type you selected.
4. Select Apply color management to strip if you want to color manage your strip.
Whether you color manage and/or verify your strip depends on what you want to achieve:
If you want to...
verify your job’s colors leave the verification for later
• monitor the proofer’s stability over time
Print your strip with...
both color management and verification color management but no verification no color management but verification
• compare the output of different proofers of the same model
Note: In this case, you will have to manually enter the first proofer’s values as reference in Esko Verification when measuring the other proofer’s output.
Note: If you selected an Esko + Solid Colors Strip or an Esko Equinox Strip, the strip
is always color managed, and the
always set to
Automatically load reference
values from source profile.
5. If you have a verification license, the Verify strip (with verification tool) option is available. Select it if you want to verify your strip.
6. If you are verifying your strip, you also need to set the following parameters: a) In the Reference list, choose what kind of reference values you are trying to match:
If you are trying to match...
• a standard (for example Ugra/
Fogra)
then select...
Manually load reference values when your verification strip is...
either color managed or not color managed
58
Pack Proof
4
If you are trying to match...
• another proofer of the same model
• a previous measurement from your proofer
(for example measurements from a test chart) an established profile that you are using for color management
(for example
ISOcoated_V2_eci.icc)
• the way your proofer prints as defined in its profile
• another proofer of the same model
(with the same profile)
then select...
Note: You need to load the standard or measurements manually in Esko
Verification.
Automatically load reference values from source profile
(this is the source
Automatically load reference values from destination
profile (your proofer profile)
when your verification strip is...
color managed not color managed
Note:
If you are using a Ugra Fogra-MediaWedge V2.2 or Ugra Fogra-MediaWedge V3.0 verification strip, additional reference values are available ( FOGRA11L_MCheck10,
FOGRA12L_MCheck10...).
Those are also available when you set the Strip Type using a SmartName.
b) Choose the Delta E Formula to use when verifying your strip.
Difference Between Colors: Delta E
on page 15 for more information about Delta E and color differences.
c) To set the color deviation tolerances to use when verifying your strip, click Edit... near
Tolerances.
The verification will pass if the color differences are within the tolerances, or fail if they are bigger.
You can fill in:
General
Tolerances
The Delta E tolerances for the color patches and the paper white.
The Maximum for 95% of all patches tolerance excludes the worst 5% patches from the calculation.
59
4
Pack Proof
Primary Colors
Tolerances
Hue Tolerances
The
Delta E tolerances for the CMYK patches only.
Tone Tolerance
Chromaticness
Tolerance
The Delta H tolerances for the CMYK, CMYKRGB and
Gray patches.
Delta H is the difference in hue between two colors.
The generally accepted Delta H tolerances are a maximum of 1.5 for gray areas, and of 2.5 for primary colors.
The Delta T tolerance for the CMYK patches.
Delta T is the colorimetric dot gain for primary colors.
The general Delta T tolerance is a -5% to +5% tone value difference.
The Delta CH tolerance for the color patches.
Delta CH is the difference in saturation between two colors.
Difference Between Colors: Delta E
Difference Between Colors: Other
on page 16 for more information.
d) If you are using an inline measuring device (like an Epson SpectroProofer or an HP
DesignJet Zx100), you can choose to print a verification report.
In Print Inline Report, select either:
• Never to never print any report,
• Always to print a report whether the verification succeeds or fails,
• When verification passes to only print a report when the verification succeeds.
Once you have proofed your file and verified it in Esko Verification, the report will show information about the proof and verification (the printer used, the date and time, the verification strip used, the tolerances and whether they were met...).
For more information about how to verify your proof's colors using Esko Verification, please see the
Esko Verification documentation
.
4.9 Summary
This shows a summary of all the settings you defined in the ticket.
• To show the settings from a tab, click + (on PC) or (on Mac) beside the tab name in the right pane.
Click
Expand All to show the settings from all tabs.
• To hide the settings from a tab, click - (on PC) or (on Mac) beside the tab name in the right pane.
60
Click Collapse All to hide the settings from all tabs.
Pack Proof
4
61
Lataa
Julkinen linkki päivitetty
Chattisi julkinen linkki on päivitetty. You may view and manage your chat links after registration here.
Dokumentin julkinen linkki
Mainos
