Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: Help setting up QTR on 2200

2004-07-20 by ccolbertbw

> The blacks are very weak (1.31)
> 

I get up to about 1.65 above paper on photo rag with Eboni.

> I am trying to follow the documentation to do a calibration but it 
> seems to have several inconsistencies:
> 
> 1) The documentation says to use the pattern test page "inkpattern.psd" 
> but there is no such file included in the installer. The documentation 
> says that the file is a cmyk file. I found a file called 
> inkseparation.psd and inkseparation.tif but these are both RGB files.
> 
The file is under CurveDesign/Images.  It is a CMYK file when you open it.
An older version of QTR used an RGB file. You can't use that on Panther.

Be sure you have the latest version beta9 I think, and only that loaded.

If you can't find it I will email it to you. Contact me off list.

> I tried to print them anyway but the prints were missing lots of 
> patches and contained no text.
> 
> I just downloaded the old beta 8 installer and sure enough the file is 
> there, I will try it with that.

That file is not compatible.  Also be sure that you have the Calibration=YES
and that you choose Quadtone RIP Calibration under Quadtone Rip
Settings under Printer Features when you print this file. The colors
on the file are not what is important here, each bit means something 
different to the QTR driver when printing in calibration mode.



Costa

> 2) What is meant by the line " QuadTone RIP Curves is whatever curve 
> set you want to split up into separate inks?"
> 
> Any help getting through this would be GREATLY appreciated. My 1160 
> with Piezo is not working and I keep getting the blue selenium problem.
> 
> I am on a MAJOR deadline to get some prints out the door for a customer 
> by Friday.
> 
> Thanks in advance.
> 
> James Haney

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.