Yahoo Groups archive

QTR-Quadtone RIP

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

Thread

Linearization Tab in QTRgui

Linearization Tab in QTRgui

2007-03-01 by donbga

Can someone explain the differences in the Linearization Tab found in 
the current version of QTRgui, 2.5.0.9 vs, the one that is shown in the 
QTR User Guide?

The current version has 60 input fields while the one shown in the user 
guide displays 21 fields.

Can I surmise that ther is a 60 step digital step tablet that should be 
used instead of the 21 step digital step tablet?

Thanks,

Don Bryant

Re: Linearization Tab in QTRgui

2007-03-01 by Jeff Randall

Your "should be used" should read "can be used".  You can input any 
number of values up to 60.  21 values work for most folks.  I find 
using 51 values (using the 51 step wedge included in the QTR 
installation) sometimes gives me a smoother ramp, but I always start 
with 21.  YMMV



--- In QuadtoneRIP@yahoogroups.com, "donbga" <dsbryant@...> wrote:
>
> Can someone explain the differences in the Linearization Tab found 
in 
> the current version of QTRgui, 2.5.0.9 vs, the one that is shown 
in the 
> QTR User Guide?
> 
> The current version has 60 input fields while the one shown in the 
user 
> guide displays 21 fields.
> 
> Can I surmise that ther is a 60 step digital step tablet that 
should be 
Show quoted textHide quoted text
> used instead of the 21 step digital step tablet?
> 
> Thanks,
> 
> Don Bryant
>

Re: Linearization Tab in QTRgui

2007-03-02 by donbga

Jeff,

>
> Your "should be used" should read "can be used".  You can input any 
> number of values up to 60.  21 values work for most folks.  I find 
> using 51 values (using the 51 step wedge included in the QTR 
> installation) sometimes gives me a smoother ramp, but I always start 
> with 21.  YMMV
> 

Thanks for the info. I suspected something like that but really wasn't 
sure.

Best,

Don Bryant

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.