Page tree
Skip to end of metadata
Go to start of metadata

This process template section determines the output resolution and how the system handles spot colors during final output.


Select the job ticket processor (JTP) to use for rendering.
Note: You set up JTPs using Prinergy Administrator.

Device Resolutions

This list is available when an output device format is selected in the Output To list.
Select a resolution for the selected device in the list.

Resolution X

Available when the Device Resolutions box is unavailable.
Type a resolution value.

Resolution Y

Available when the Device Resolutions box is unavailable and mixed resolution values are allowed for the output format selected in the Output To list.
Type a resolution value.

Color Model

Select the process color model to use for output.
The list of values varies, depending on the output format selected in the Output To list.


To set the number of shades of gray to output, select 1 for screened data or 256 for continuous tone data. When 1 is selected, the Calibration & Screening section of the refine process template is available for input.
The list of values varies, depending on the output format selected in the Output To list and the color model selected in the Color Model list.

Do Separations

Available when the output format selected in the Output To list supports separated output and DeviceCMYK is selected in the Color Model options.
Select if you want Prinergy to output separations. Clear this check box if you want Prinergy to output a single composite file.

Always Use Color Combiner to Convert Spots

This check box is not available when an Expose JTP (GDAPI) is selected in the Output To list.
If the input files contain overprinted spot colors, the Color Combiner, which is a plugin to the renderer, combines the layers and outputs the overprinted colors correctly.

When this check box is cleared, the renderer handles the conversion of spot colors to process colors if the following conditions exist:

    • Input files are composite.
    • All spot colors are set to opaque in the color database (if a spot color is not in the color database, opaque is assumed.)

If the above conditions are not met, the Color Combiner will be used, even if the Always Use Color Combiner to Convert Spots check box is cleared.

It is recommended to always select this check box.

This check box appears in both the Render section and the ColorConvert section. Changing it in one place changes it in the other.

See About Color Combiner.


Select this check box to enable anti-aliasing, and then in the at Ratio list, specify a ratio for anti-aliasing.
Anti-aliasing is a technique of improving the appearance of output by minimizing the "stair step" effect on rasterized output. It does so by rendering to a higher resolution than the intended output, and then downsampling to the intended output. This generates "averaged" pixels which softens the "stair step" effect on low-resolution output. The ratio value for anti-aliasing refers to the factor used to determine the intermediate resolution. A higher ratio results in higher quality, but can have an effect on output speed. For example, if the output is a 300 DPI 8-bit TIFF, and the anti-alias ratio is 4, Prinergy will render an intermediate output at 1200 DPI (4 x 300 DPI), and then downsample to the user-requested 300 DPI. Anti-aliasing is only available for 8-bit (256 shade) output.

Fail if font problems detected

Select this check box to fail the output process if a file has missing fonts.
Note: This option is not available for vector outputs (PDF, PS2, PS3, EPS, DCS Vector, PDF/X-1a, PDF/X-3, CT/LW, and DELTA).

Ignore Embedded Fonts in Marks Files

Select this check box if you want Prinergy to ignore embedded fonts in a marks file and to look for the fonts in the system fonts folder.
Important: You must install the fonts in %ServerName%\%AraxiHome%\AdobeExtreme\bin\fonts, or the output will fail.

Convert Text to Paths

This check box converts fonts to outlines before a file is RIPed. 
This option was added in Prinergy 3.0 when the CPSI 3016 RIP was included with Prinergy. This option helped situations where the 3016 RIP failed to process the fonts on certain jobs.
This option has limited usefulness now, but is included as a potential workaround in rare cases where fonts are not rendered correctly by the RIP. It is not recommended that you enable this on on a permanent basis. When using this option for specific jobs, it is recommended that you ensure that both proofs and plates are output with this option.

Note that when you select the Convert Text to Paths check box, you will have text appear fatter on low-resolution proof output. You can overcome this appearance problem by either:

    • Rendering to a higher resolution, if rendering to 1-bit output, such as Virtual Proofing System
    • Using anti-aliasing, if rendering to contone output

      Note: This check box is only available for raster output formats (.VPS, .TIFF, and so on).

Restrict output of layers/versions with errors

This check box applies to Layered PDF Versioning. Select this check box to print the selected layers/versions but not the error layers/versions. For information, see the Versioning chapter in this guide.

Complex job mode (use with caution)

Select this check box to process complex jobs that would otherwise fail during the RIP process, such as map jobs or PDF files with very high resolution bitmaps. This option should not be used for normal jobs that can be RIPed successfully without it, because RIPing with this option may take longer to process. RIPing complex jobs with this option may take many hours to process although the jobs will succeed in outputting. 


    • This option requires Windows 2008 with the recommended amount of RAM.
    • This option only works with Adobe PDF Print Engine output.
    • This option has had limited testing, so caution is urged when using it.

Non-fatal PDF error handling

Select one of the following options:

    • Ignore all errors—to ignore all non-fatal error messages
    • Ignore negative dash phase errors—to ignore only errors related to lines that contain negative dash values.
      Note: PDF and PS specifications consider negative dash values as illegal. These errors are typically non-fatal and should not cause a problem when they are suppressed.
    • Ignore invalid font data errors (use with caution)—to ignore only errors related to invalid font data.
    • Detect all errors—to detect and fail output on all errors (this is the default setting). 

Note: Regarding the font related error handling. APPE 3.x has become stricter with fonts that have invalid data, but the error can be suppressed with the Ignore invalid font data errors setting. This setting should be used with caution, because there may be cases where the invalid font data will cause rendering problems (such as font missing on output). If you decide to use this option, check your output carefully. Anecdotal evidence shows it is typically safe to ignore the invalid font errors.

When using the Detect all errors setting, as of Prinergy 8.0 the actual font name is printed in the processing history message, but note the following limitations around the messaging:

    • If you output one page that has multiple invalid fonts, the RIP will only report the first font encountered and terminate.
    • If you output multiple pages (each containing unique invalid font data), only the font from the first page the RIP processes will be reported in history and all pages will fail output.
    • If you impose multiple pages (each containing unique invalid font data) and output, only the first page's invalid font data will be reported. If you submit two imposition surfaces at once (that each contain invalid fonts), both will be reported in history (but again only the first page on each surface that is encountered).
    • In Prinergy 7.5 you would observe a vague error message if the negative dash phase or invalid font errors were detected:
      DiagView: ACR ERROR: 26, Error interpreting PDF
      Workshop: An error occurred while attempting to process a job.

 Tip: To find each unique offending font you could outline each font and try to output again, until all invalid font data is resolved. Alternatively, set the output process template to ignore invalid font data, and scrutinize your proofs.

  • No labels