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 |
Prinergy 1.0; Prinergy 1.1; Prinergy Connect 2.0 | |
Platform |
Server: Dell or Dat General all; Client: PC or Macintosh |
|
Operating system |
Server: Windows NT or 2000; Client: Windows or Macintosh |
|
|
|
||
Error |
Optimizer: Found ColorSpaceArray color space. Image: XObject-Image on page 1, separation Black, contains non-DeviceGray color space; PDF file: T:\Jobs\63917_ColorSpaceArrayError\System\SubPages\p001_level2.pdf. |
|
|
|
||
Symptoms |
When refining separated PDF pages that contain RGB images in Prinergy, the refiner fails the job and reports an error similar to the following: Optimizer: Found ColorSpaceArray color space. Image: XObject-Image on page 1, separation Black, contains non-DeviceGray color space; PDF file: T:\Jobs\63917_ColorSpaceArrayError\System\SubPages\p001_level2.pdf. |
|
|
|
||
Cause |
Prinergy supports separated PDF with CMYK images, or composite PDF with RGB images (not separated PDF with RGB images). The application that is generating the separated PS isn't separating some of the components of the page, and is leaving non-gray components in the separated page. | |
|
|
||
Solution |
A. Recreate the input files in one of the supported formats. B. Or, you can set up a Refine process plan to convert all input to grayscale. Because the separated pages are already separated (grayscale), the Color Converter will only affect the non-gray problematic page elements. Note: If the page contains CMYK data in your separated page, you will need the Advanced Color Management option to convert the CMYK to grayscale. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
color, optimizer, PDF |
|
|
|
||
Technical contact(s) |
James Bredenhof |
|
Submitted by |
||
Date submitted |
||