Yahoo Groups archive

QTR-Quadtone RIP

Index last updated: 2026-04-28 23:12 UTC

Message

Re: QTRICC-RGB vs QTRICC

2012-12-05 by remononaz1

Paul:

I gave this a shot as soon as I got home. Having read your instruction several times, I was quite confident of the process and it proceeded very quickly. 

However, the results are not good. There are no surface artifacts, indicating that the blue curve is still holding down the Eboni ink, but the tones are too dark. I'm reading 72 at 50 and 85 at 65. 

Any ideas why the .icc created would yield such dark levels? When I print the curve with printer controls, G2.2, no icc, 50 reads 48 and 85 reads 82. Overall with that ramp I'm off 0 to 3 but it is linear. 

Homer Shannon

--- In QuadtoneRIP@yahoogroups.com, Paul Roark <roark.paul@...> wrote:
>
> remononaz1 <homershannon@...> wrote:
> 
> > **
> >
> >
> > ...
> > Once the RGB-ICC is generated do you apply a curve to the image and then
> > print with the ICC or just take the un-altered B&W image and print it with
> > the ICC?
> >
> >
> The ICC both applies the curves you've embedded as well as the
> linearization curve.  So, you just print with a GS image file.  I recommend
> 16 bit Tiff.  The image, as I understand the process, goes into the ICC as
> 16 bit (if RGB it's apparently converted to GS and then, presumably,
> re-converted back to RGB), the curves within the ICC are applied in high
> bit mode, and the output is 24 bit RGB to the Epson driver.  As long as the
> PS curve you've embedded has it's R, G, and B curves as distinct,
> non-identical curves, the original 16 bit image data, I would think, is
> fairly well preserved in the final 24 bit pipeline.
> 
> (Of course, the printer dithering probably wipes out quite a bit of
> information, but at least you know you're going to that stage with as much
> as possible.)
> 
> Paul
> www.PaulRoark.com
> 
> 
> [Non-text portions of this message have been removed]
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.