Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: Invalid Linearize curve message

2007-10-13 by Louis Dina

Thanks, Jim, but I don't think that is the problem.  I have other 
files that linearized just fine, and they list the L* data in 
descending order exactly as presented below.  

I did just upgrade to QTR 2.5.2.1, so maybe this is a bug?  It's 
probably something I am doing.  Perhaps the two or three darkest 
patches are too close together.  I did notice that the QTR-Linearize-
Data version is 2.5.2.0.

Lou 

--- In QuadtoneRIP@yahoogroups.com, "Jim Thyer" <jimth@...> wrote:
>
> Hi Diana,
> 
> Remembering when I did my linearization the numbers were in 
ascending order, so try reversing them.
> 
> Jim Thyer
> 
>   ----- Original Message ----- 
>   From: Louis Dina 
>   To: QuadtoneRIP@yahoogroups.com 
>   Sent: Saturday, October 13, 2007 3:37 PM
>   Subject: [QuadtoneRIP] Invalid Linearize curve message
> 
> 
>   I am using QTR 2.5.2.1 on a Windows XP machine. I keep getting an 
>   error message when trying to linearize that reads:
> 
>   "Invalid linearize curve -- not constantly increaseing. Curve 
>   Creation failed."
> 
>   I export data to a tab delimited text format and drag it onto the 
QTR-
>   Linearize-Data.exe file and I get a nice smooth ramp without any 
>   reversals reversals in the density or luminance data. Then I copy 
>   the "linearize" data line in the bottom of the generated text 
file 
>   and paste it into the Linearization window of the curve creation 
>   module. The original data looks fine to me. 
> 
>   What the heck am I doing wrong? Below is the linearize data for 
this 
>   file:
> 
>   QTR-Linearize-Data version 2.5.2.0
> 
>   LINEARIZE="95.63 93.09 88.98 85.03 81.23 76.85 71.99 68.03 63.64 
58.9 
>   53.9 49.73 44.41 39.95 34.64 28.78 22.71 15.46 10.57 6.85 6.39"
> 
>   Thanks, Lou Dina
> 
> 
> 
>    
> 
> [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.