|
|
|
|
|
Lucid: In general how is your TIFF/IT production
progressing - do you work with Job Tickets and multiple
queues for different settings?
User: Not bad. We produce quite a bit of TIFF/IT
files, and from day one have set up TIFF/IT flow in
"server mode" with full job ticketing and multiple job
queues. As you can imagine, we really depend on your
software.
|
|
Lucid: Please give me your thoughts on these
issues.
User: Please note that we are currently running
TIFF/IT flow 4.1.1.2c, so we are currently not benefiting
from the last 3 issues we've reported and you've fixed
(high res inter-image edge, proper handling of 1-bit
tiffs, and LW file getting blown out). I would like
to know ASAP if we are supposed to have "No Extra Transparency"
on or off so we can stabilize our tiff/it workflow.
As far as simplifying the UI, it really doesn't affect
us either way, as we're doing everything with job tickets.
I suppose it helps to have the control in the UI if
an issue comes up and the fix does not involve rewriting
and redistributing code. Maybe more switches can be
thrown into the advanced settings section to hide them?
|
Lucid: "Extra Transparency" is a feature in TIFF/ITflow
that can be used in those circumstances where LW production
is required and clients will not accept HC files. Customer
artwork is complex and very likely to exceed the 256
color LW palette. Extra Transparency will carefully
analyze the Delta data and move some tints colors safely
into the CT layer to eliminate palette overflow. The
UI option No Extra Transparency turns this feature off.
Inter-Image edge is a very new feature that when enabled
uses a feature in the Delta List format to determine
the edges between individual pictures as they are represented
in the Image layer of the Delta List data. Where two
or more images share the same boundary, TIFF/ITflow
will place the high res boundary pixels into the HC
file to maintain fine image clipping.
Keep page size in FP is used to make sure the element
size in the
FP >file is the same as or greater than the actual Delta
job. This will
prevent >some systems from rounding down and clipping
part of the page.
Keep page size means that the final page size declared
in FP file, will be
exactly the same as the original page size; however
checking this option may
result in different resolutions on X and Y axes of the
output page.
Unchecking this option will force the same resolution
of both axes, but the
resultant page size may differ from the original page
size, however, it will
be greater or same.
So if the TIFFIT consumer doesn't require accurate X
and Y resolution
equivalence, this option is recommended to be tured
on.
|
|
User: With regards to High res in CT, it's definitely
an undesirable feature for a couple of reasons:
1) There is no benefit. There are many high res elements
on the CT layer that are "choked" so that the anti-aliasing
will not protrude outside of the same element on the
LW.
2) At least one major publication does not want high
res in CT for CT-LW registration issues.
3) If #1 was resolved, we still cannot ever use the
CT file alone for proofing purposes. We may miss a problem
(ie corruption) with the LW file if we do this.
This problem is specific to Delta TIFF/ITflow (in other
words, it is not a TIFF/IT-p1 issue), correct?
Lucid: The main issues are addressed in the software.
The only possible issue with "CT-LW registration" is
addressed in the "integer relationship" check box on
the resolution tab of TIFF/ITflow. You should put in
a CT value at or just below 300 and then check that
box. With this there is no way for there to be a registration
problem. Its not like the CT is on one plate and the
LW on another, they are digitally combined for printing!
In addition, placing the high resolution data in CT
layer may allow to
reduce the LW palette size, when used together with
the extra transparency
enabled. Moreover, even if the overflow occurs, the
knocked out high
resolution areas will still look reasonable, without
significant distortion
that appears when the high resolution data is not present
in CT.
The only situation when the high resolution data might
be taken
out of the CT layer is when one wants to open CT and
see the images only.
User: The printer at the major publication did
not have a problem with TIFF/IT files from us, however
they did have a registration problem from *someone's*
file and I do not know the circumstances of that problem
(ie if the CT and LW res were in a integer relationship).
Because of this they prohibited high res data in the
CT from everyone. We were lucky in that we could send
them HC. I just wanted to make sure that taking the
high res out of the CT for a LW/CT TIFF/IT file was
NOT possible in a delta/ TIFF/IT file flow setup because
it simply does not benefit our workflow.
Misregistered CT/LW is not the only problem as in cases
where type drops out of the LW file, it is harder to
detect in the proof because a low quality version is
in it's place, instead of the type being dropped out
altogether. If the file was proofed on a non-halftone
dot proofer, this may go undetected all the way to the
pub's printer. A good thing, however, is that we haven't
seen LW type dropping out lately.
|
|
|
|
|
|
top