The two colour conventions, reading a die-line PDF, checking the blocks and exporting the DC job XML.
Overview
A customer sends a die-line PDF: the finished shape drawn as colored rules over the artwork. Someone then has
to work out what the machine is being asked to do and build the job by hand, measuring positions off the page.
The Die Line Reader does that reading for you — drop the PDF in, check what it found, and export the DC job XML.
The two color conventions
There are two conventions in circulation and they contradict each other, so the reader has to know which one a
file follows. It works this out on its own; the Color convention box shows what it decided and
lets you overrule it.
Customer die line — what a print buyer's designer draws:
Drawn as
Read as
On the machine
■ Red or magenta
Cut / slit
The boundaries of the finished pieces. Lines down the sheet are slits, lines across it are cuts.
■ Blue or cyan, dashed
Perforation
A perforation across or down a piece, with the tool you choose.
■ Green, dashed
Crease
A crease across the sheet.
Duplo DC template — the templates Duplo supplies, named like
648-B2-604/TableTent_12x18_2up:
Drawn as
Read as
On the machine
■ Cyan, solid
Cut / slit
Drawn as a closed rectangle around each finished block.
■ Cyan, dashed
Perforation / score / slice
Pick the tool per line — Perf, Micro, Slice-Score or Score.
■ Magenta, dash-dot
Crease
A crease across the sheet, at the depth you set.
Red means opposite things in the two. A customer's red line is the cut; Duplo's magenta
dash-dot line is the crease. Color alone cannot tell them apart, so the reader looks at which family carries the
solid lines: a designer draws the cut solid in red, whereas a Duplo template draws the block solid in
cyan and its crease dashed. If a file is unusual, set the convention by hand.
The colors do not have to be exact — and that matters more than it sounds. A designer
drawing "red" cut lines in Illustrator normally ends up with CMYK 0/100/0/0, which is really magenta, and Duplo's
own template draws its crease as CMYK 0/90/85/0, which is a vermilion. Both get called magenta by the people
using them. "Blue" perforations come out as CMYK 100/0/0/0, which is cyan. Matching on exact color values would
reject nearly every real file, so the reader works on hue family: scarlet through magenta is one family, cyan
through blue another, green a third. Black, gray and pale tints in the artwork are ignored.
Reading a die
The Die Line Reader with a 4-up table-tent die loaded. The die lines are drawn back over the artwork on the left — red for cut/slit, dashed cyan for perforation — while the right column tallies what was found, holds the job details, and lists every rule with its direction, length, position and type.
Drop the PDF on the window. Page 1 is read. The die lines are drawn back over the artwork in the
panel so you can see at a glance that what was found matches what was drawn.
Check the tally. Cut, perf and crease counts, the sheet size, and how many finished pieces came out
of it — for example 12 × 18 in · 4-up (2 × 2) at 5.000 × 7.750 in.
Look down the line list. Every die line is listed with its color swatch, direction, position and
length. A dashed rule drawn as dozens of separate strokes is rejoined first, so one perforation appears as one
line and not as thirty.
Correct anything that is wrong. Change a line's type if the customer used a color loosely, pick a
different tool for a perforation, or untick a rule that is really part of the artwork. The preview, the piece
grid and the XML all update as you do.
Set the job details. Job name and number, the machine, and the lead edge — the edge that feeds in
first. If the die was drawn for the press rather than the cutter, turn it here instead of redrawing the file. Default perf tool sets the tool any perforation gets unless you change that line individually, and Crease depth sets the depth written into the XML — 1 — normal by default.
Export.Save DC job XML… writes the file, defaulting to the same export folder the Imposer
uses. Drop it in the PC Controller's Import XML folder.
Setting your own colors
The two conventions above cover most files, but plenty of shops draw their dies their own way. The
⚙ Settings button sets the rules: one row each for Cut / slit,
Perforation and Crease, and for each a color family and whether it counts when drawn solid,
dashed, or either.
Open a file first. The dialog lists the colors actually drawn in it — Cyan / blue solid ·
12, Red / magenta dashed · 6 and so on. Click one to assign it. That is far quicker, and far
harder to get wrong, than picking from the lists blind.
Or set the rows by hand. Color families are Red / magenta, Cyan / blue, Green and Yellow / orange,
plus Any color and Not used. Line style is solid only, dashed only, or either.
Name it and save. It joins the convention list at the top of the panel and is there next time. Saved
set-ups live on this machine, and the suite’s scheduled backup carries them.
The dialog warns when two rows clash. If a cut and a perforation are both set to cyan solid
there is no way to tell them apart, and if one row takes a color “solid or dashed” while another
takes the same color “dashed only”, the more specific rule wins. Both are flagged as you edit rather
than left to surprise you at the machine.
Faint lines at the bottom of the dialog sets how washed out a color may be before it is treated
as artwork instead of a die line. The default keeps pale tint boxes out of the way. Lower it only if a die drawn
in a tint is coming up empty.
How the finished pieces are worked out
A DC controller does not think in cut lines, it thinks in blocks. Where the cut lines close into rectangles the
reader uses those directly — which is exactly what a Duplo template gives you, since it draws each finished
block as a rectangle. That is the accurate answer and it is tried first.
When the cuts do not close — a die of bare slits and cuts running off the sheet — it falls back to reading the
bands they divide the sheet into, and decides which are product by width: an outer band with the sheet edge on
one side and a cut on the other is trim, and trim is always narrower than the pieces it is trimmed from. A sheet
with a single cut down the middle and pieces running to the edges gives two equal bands, neither narrow, so both
are kept — the right answer for that layout.
The panel says which method was used, and the block outlines are drawn on the preview, so you can see what it
decided before you export rather than at the machine.
The XML it writes
The same DuploDCJobTemplate the Imposer exports, so a file from here imports into the PC Controller
— and back into ImposeIQ — exactly like one produced by the rest of the suite. One CutBlock per
finished piece, in points, origin bottom-left.
Perforations are written relative to the piece they cross rather than to the sheet, which is how the controller
addresses them: it repeats a single entry onto every matching block. Four identical perforations across a 2 × 2
layout therefore collapse to two entries, not eight — one per position on the piece.
Creases down the sheet — the Crease element carries a Y position and nothing
else, so it can only describe a crease running across the sheet. A crease drawn down the sheet is the slitter
module's score wheel on the machine, and the schema expresses that as a perforation with the Score tool, so that
is what it is exported as.
What a DC cannot cut
Only straight lines square to the sheet. Any die line that is diagonal or curved is counted and reported in the
panel rather than quietly left out of the export — if a shape needs a rotary die, you want to find that out
while you are still looking at the file.
Perforations and creases that fall outside every finished piece are reported the same way. They are usually in
the trim, but occasionally they mean the piece grid came out wrong, which is worth a second look.