|
Configuring the Delta RIP
|
|
|
|
Lucid's products and Heidelberg's Delta RIP technology |
Lucid's products are designed to enchance the productivity
of Heidelberg's Delta RIP technology.
Most of Lucid Dream's flow products start by reading
the “Delta Document”, which is the “job.ddc” file. This
file contains references to all other elements. For
TIFF/ITflow in every case and for PDFxMakerLite, PDFxMakerPro
and DCSflow when the “create image” option
is turned on, the software uses the Image Mask “DO”
file to create the CT or Image Layer from the high resolution
data of the “DG” file.
Click
here to see how Lucid's products use the information
on DeltaList files.
|
Configuring the Delta RIP
|
In the simplest setup the Delta Print Manager is run
and an Export Directory is made from the Create Printer
option. In the setup window a directory is selected
for the Exporting of the full color Delta jobs.
The Export Format is set to a sub-directory with multiple
files. The option "Execute the following batch file
after exporting" is checked. Then the BATCH file for
one of the Lucid applications is selected from its original
install directory. (There is an example BATCH file in
the installer of every application).
|
Configuring the product for automatic use
|
Each Lucid's product if fairly simple to configure
for automatic use. Just configure the Delta RIP as described
earlier, selecting the product's batch file. Start the
product manually, configure it (how - you can find in
the technical guide for an each product), then quit.
The product will be restarted whenever it's needed.
The majority of flow products will normally place automatic
output in the destination folder selected from the product's
window. To change this, you can modify the produtc's
batch file. Find the command line and add a "-o" and
the output pathname.
The majority of flow products include a simple job ticket mechanism. This allows for
different job settings to be used for different Delta RIPs and Queues. When setting
up a custom batch file for power workflow, each batch file can point to it's own
"Job Ticket" or setting file. To add a Job Ticket, you should find a command line
in the product's batch file and add a "-j" and the full name of the XML file, which
contains job ticket commands. All Lucid products provide the options to save their
settings in the corresponding Job Tickets. You have to start the application, set
necessary parameters and press the "Job Ticket.." button in the dialog window
to save them.
If you want to place a log file about the results of
the product's work, you shoud add a
"-l" and the pathname,
where a log file will be placed.
Thus, the command line from the product's batch file
will look like that:
TIFFITflow -i %1 -o C:\LucidOutput -j C:\JobTicket\proof.txt -l C:\LucidOutput
|
|
|
|
top