Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: [QuadtoneRIP] Re: Eboni 6 in a 2400

2013-03-27 by Paul Roark

Parker Smith <parkersmithphoto@...> wrote:

> **
>
>
>
> ... I did print it out without the Lin #s, read with the spectro, plugged
> in the resulting #s into the linearization panel, and then printed out a
> new chart which looked like it might still have some gradient issues.
>
> Can I read the new numbers and then replace the existing numbers?
>
No, it needs the numbers that are produced by the profile with the
linearization boxes empty.

If there is a problem it's usually due to a pre-linearization curve that
has a sharp turn in it.  I always graph the pre-linearization Lab L values
in Excel to see if the curve is reasonably smooth, even if not linear.  If
I see a sharp kink, I try to remedy it by changing some of the numbers on
the Ink Setup page or, better, taking manual control of part of the profile.

I'm not sure how you have the system set up, but what I do sometimes is
have 2 channels or partitions of the carbon ink.  Then with the one of them
I turn it into a set of manually drawn curves.  This is much easier that
you'd think.  You simply increase the ink limits of the channel you want to
draw to 100%, hit "show curve," and do a screen grab of those curves.
 Print the  graph, and enter the coordinates into the Point List for the
curve you want to take manual.  The ink limits will be what you had in the
original curve, at least initially.

Once you have one (and only one) of the channels manual, you can alter the
points to correct for the glitch in the overall curve.

In general, that pre-linearization curve should be relatively smooth.
 Don't Expect miracles from a smoothing algorithm that only has 21 of 256
input points.

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.