User's Manual

Negative
impacts on
throughput
There are several things that affect the performance of the system and RIP speed
when processing print jobs. The following is a list of common situations that
negatively can impact throughput.
• The nature of printing is that the complexity of images is non-deterministic until
those images are being processed so that rated speed of the engine is not
guaranteed during RIP. Note that when printing multiple sets of a document,
Nuvera retains all images after RIP for all subsequent sets therefore any
performance penalty encountered will only be experienced during the first set
Note: that the default print resolution is 1200 dpi. 600 dpi printing may be
adequate for your needs so you can try setting that resolution to improve RIP
performance of complex 1200 dpi jobs. 1200 dpi results in 4 times the internal
image data of a comparable 600 dpi image that has to be transferred through the
system. When the print resolution is changed from 1200 to 600 dpi, the stroke
thickening value may also need to be changed from 1 to 0 to avoid excessive line
thickening.
• It is common to embed logos and watermarks in submitted print files. These are
typically bitmap images that when embedded in a print stream (such as PostScript)
can take a long time to process. Note also that resolution selections (e.g. 600 dpi
vs. 1200 dpi) can have a significant further impact to processing of these types of
embedded images. Consider the design of documents and impacts to printing
speed in such cases. There are methods available, through PostScript for
example, to cache these embedded images, process them once, and retain them
as a resource for application on each page without having to render and scale
them for each page. Refer to your PostScript reference manuals and DocuSP
reference manuals for information about caching.
• Submission of multiple TIFF images simultaneously is a common application.
There are several batch printing tools available on the market that enable this and
most require the selection of a print driver for the target printer that these images
files are submitted through. In these cases the TIFF files are converted to a Printer
Description Language (PDL, such as PostScript) by the batch tool by using the
printer driver and then submitted to the printer, which in turn RIP that PDL and re-
render the TIFF bitmap images back into bitmaps. This is an inefficient process
and can significantly slow the machine down. Nuvera includes a native TIFF
interpreter and it can process TIFF files sent to it directly. Some of the batch tools
on the market support a native TIFF submission capability. It may be referred to as
a bypass mode or something similar. If such a capability is available the Nuvera's
performance can be significantly improved by taking advantage of that. (Note that
the TIFF interpreter does not automatically determine the embedded image size
and apply it to an appropriate paper size. You can accomplish though by using
printer and queue defaults programming)
Tab behaviors
for MFF
systems
On systems with an MFF, tab jobs are delivered to the finisher face up in N to 1 order.
All sheets in tab jobs are inverted in the paper path prior to entering the finisher. As
such, the following must be noted:
• Tabs need to be loaded in the feeder tray in N to 1 order (commonly referred
to as reverse ordered tabs)
• If drilled paper is being used in the job, the drilled paper for the main body of
the job must be rotated in the tray such that the holes are on the leading edge
of the paper (to the left), opposite of what the tray labels indicate.
• If pre-printed stock is included in a tab job, the pre-printed stock must be
rotated 180 degrees in the feeder tray, opposite of what the tray labels
indicate.
Additional information for running tab jobs appears in the Operating Feature Hints &
Tips section of this document.
6