Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
||
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
CEPSLink files are up to twice as slow to process as normal fat PostScript from Quark. (ExportPS pages, which are another type of CEPS pages exported to PostScript by Scitex, can also be problematic.) |
|
|
|
||
Cause |
With Copydot and CEPSLink pages, it is time-consuming to generate thumbnails. Thumbnail generation requires rendering the pages and rendering Copydot or CEPSLink pages is slow, even at low-res. (Conversely, 'real' PDF is normally fast to render at low-res). | |
|
|
||
Solution |
Turn on ZIP compression in the Refine/Normalizer process plans. CEPSLink files include a large CT file that generally covers the entire page, even if the viewable portion of the CT only covers a small part of the page. So the uncompressed CT is often about 35MB per 4-color page. With ZIP compression this will probably shrink by four times. (Note that ZIP only helps CEPSLink, not other raster pages such as Copydot. ZIP reduces file sizes so it will speed things up a bit, but CEPSLink is still slower than PDF.) As well, consider turning off thumbnails for jobs that have a significant amount of Copydot or CEPSLink content. Creating thumbnails takes almost as long as proofing these pages, and proofing times are relatively long for these type of pages, for example, 1.5 minute/page for CEPSLink and 2 minute/page for Copydot. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
CEPSLink, Copydot |
|
|
|
||
Technical contact(s) |
James Bredenhof |
|
Submitted by |
||
Date submitted |
||