QTR-Quadtone RIP

--- In QuadtoneRIP@yahoogroups.com, "Tyler Boley" <tyler@t...> wrote:
> --- In QuadtoneRIP@yahoogroups.com, "ccolbertbw" <ccolbert@u...> wrote:
> ...
> > For some reason the PKN on Luster paper builds up density in a very
> > nonlinear manner. The density curve is very steep, then flattens 
> > out. But you don't want to ignore that top part of the curve by setting
> > an early ink limit because it means the difference between a dmax of 
> > 2.0  vs 2.3.
> 
> Costa, I haven't had time to finish my testing, but I have learned a
> few things so far. You are right about the aparent lack of sense using
> ink limits to initially bring things in line, therefore losing dmax.
> But, it's the way QTR seems to work best, and Roy designed in K boost,
> which allows you to bring all the way back to native unlimited output
> in that ink (if needed), so you can "unlimit" there. For straight
> quads, there is way too much ink going down to get effective
> partitioning unlimited.
> 
> Until I learn otherwise, it seems the best route is to bring things
> well into line with limits, gamma, highlight, and shadow controls,
> then bring dmax in with K boost (and maybe a bit of overlap), and
> linearize.
> 
> Tyler

Tyler,
   As the controls exist now, I agree completely with your assessment.
My  comments were mainly looking forward towards ways of making
the last bit of fine tuning less fiddly.  The boost does offer a pretty 
good fix for the dmax. It is easy to get a  99-100%  black with good
dmax. For me, it is more difficult to get  a smooth well-linearized 
transition from 95  or so up to that final dmax.  I have made many
curves that looked great except for weirdness in the deep shadows
that result in  black blobs where the density abruptly jumps to the
final dmax. I haven't found this jump easy to fix with either the
shadow controls or the final linearization. 

I absolutely love QTR. It works in a logical, coherent, direct manner. 
There are few surprises, because you can predict what it will do. It 
also ends up with a table (the profiles) that you can print out yourself 
and see what is happening.  Having all the source code, you can see 
what is going on. Its simple and direct.

I just find it a bit frustrating that the last little bit of fine tuning is
fiddly and would like to figure out a way to make it less so.

best,
Costa