Xerox 6180N DocuSP Common Controller System Guide - Page 134

Job RIP hints, Variable data

Page 134 highlights

Hints and Tips Job RIP hints If using the default media/color settings that are pre-loaded on the controller, the DocuSP process built in color space transformations to accelerate RIP performance. If you do any of the following, the color space transformation probably takes more time and the RIP is slower: • Define own media • Include input or output ICC color profiles in the PDL file • Change any of the system color settings (that is, saturation, lightness, color adjustments for C,M,Y or K, emulation mode, etc.) NOTE: In general, RGB and LAB color space transformations are slower than CMYK transformations. If the input images of a job can be created in CMYK color space, then the DocuSP are able to process the job more efficiently. Variable data Variable data job construction is also an important driver of RIP performance. Jobs that are constructed with a single underlay or background plane and a small number of variable text or image overlays run very efficiently. If the same job is constructed with the underlay constructed from several distinct objects which the DocuSP is asked to compose on the fly, then the job is not able to take advantage of the DocuSP variable data performance enhancement. In that case, the job may RIP significantly slower than the more efficiently constructed job. For cases where the background/underlay of the variable data job is composed of 2 or 3 relatively static objects, it is suggested to have the application create each static combination of objects as a different underlay. This is more efficient than having the DocuSP perform the composition. When creating variable objects to be overlaid on fixed underlays or backgrounds, it is also important to ensure that the objects are properly cropped or bounded and at the lowest acceptable resolution. The DocuSP can compose 2 variable data objects of 2 inches by 2 inches and 300 dots/ inch resolution about 10-20 times faster than it could if the same objects were 600 dpi and 8.5x11 inches. 9-6 System Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140

Hints and Tips
9-6
System Guide
Job RIP hints
If using the default media/color settings that are pre-loaded
on the controller, the DocuSP process built in color space
transformations to accelerate RIP performance. If you do any
of the following, the color space transformation probably
takes more time and the RIP is slower:
Define own media
Include input or output ICC color profiles in the PDL file
Change any of the system color settings (that is,
saturation, lightness, color adjustments for C,M,Y or K,
emulation mode, etc.)
NOTE:
In general, RGB and LAB color space
transformations are slower than CMYK transformations. If the
input images of a job can be created in CMYK color space,
then the DocuSP are able to process the job more efficiently.
Variable data
Variable data job construction is also an important driver of
RIP performance. Jobs that are constructed with a single
underlay or background plane and a small number of variable
text or image overlays run very efficiently. If the same job is
constructed with the underlay constructed from several
distinct objects which the DocuSP is asked to compose on
the fly, then the job is not able to take advantage of the
DocuSP variable data performance enhancement. In that
case, the job may RIP significantly slower than the more
efficiently constructed job.
For cases where the background/underlay of the variable
data job is composed of 2 or 3 relatively static objects, it is
suggested to have the application create each static
combination of objects as a different underlay. This is more
efficient than having the DocuSP perform the composition.
When creating variable objects to be overlaid on fixed
underlays or backgrounds, it is also important to ensure that
the objects are properly cropped or bounded and at the
lowest acceptable resolution. The DocuSP can compose 2
variable data objects of 2 inches by 2 inches and 300 dots/
inch resolution about 10-20 times faster than it could if the
same objects were 600 dpi and 8.5x11 inches.