![]()
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy Connect 2.0 ; Prinergy Direct 2.0 ; Prinergy Access 2.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
In very rare intermittent occurances, there have been cases where an image (photograph) in a PDF becomes corrputed when downsampled. This corruption almost appears to be "static". It might occur on only one image on the PDF. If the PDF is separated, it might only occur on one image of one separation of the PDF. Refining the input PDF a second time (not re-refine of the already-processed page) will make the problem disappear. It does not occur on PostScript. NOTE: this problem is visible in proofs. However, in the case of separated input, this problem can be difficult to see (especially if the corruption occurs on the Yellow separation). |
|
|
|
||
Cause |
In Prinergy 2.0.7, this issue is introduced under very rare circumstances and is difficult to reproduce. It is related to: - input PDF that has images which are a high enough resolution that they require downsampling - multiple Normalizers on the same Prinergy server - high-load situations |
|
|
|
||
Solution |
If you are encountering this problem, you can use any one of the following solutions: 1. Upgrade to Prinergy 2.1 (this issue is not present in Prinergy 2.1). 2. Turn off all Downsampling options in the Optimizer (note that this will result in larger PDFs and possibly slower processing). 3. Split the Normalizer pool (for example, put Normalizer1 on Server1, and Normalizer2 on Server2). Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
normalizer, optimizer, PDF |
|
|
|
||
Technical contact(s) |
James Bredenhof |
|
Submitted by |
James Bredenhof |
|
Date submitted |
30 Dec 2002 |
|