Yahoo Groups archive

QTR-Quadtone RIP

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

Message

RE: [QuadtoneRIP] Help Changing Ink Limits for Profile

2007-01-16 by Tom Moore

John

There are two ways you can go about doing what you want. You can adjust the
1440 curve. To do that I would start by reducing all the limits by 85% and
then further adjusting the black boost for highest dmax without bleeding.
Then you would have to re-linearize. It's true that the Cone supplied curves
are different from those that can be produced by QTR. At least with QTR
derived curves you have the ability to make changes to correct problems like
the one you're encountering. 

Another approach would be to use the existing 2880 curve and reducing the
QTR Ink Limit Adjustment (in the print window) until the bleeding is
eliminated. Assuming the resulting dmax is still acceptable, you could then
re-linearize for that ink limit by creating an ICC file using
QTR_Create_ICC.

Good luck.

Tom Moore

> -----Original Message-----
> From: QuadtoneRIP@yahoogroups.com [mailto:QuadtoneRIP@yahoogroups.com] On
> Behalf Of John Hollenberg
> Sent: Monday, January 15, 2007 7:53 PM
> To: QuadtoneRIP@yahoogroups.com
> Subject: [QuadtoneRIP] Help Changing Ink Limits for Profile
> 
> I have a simple problem:  I was getting ink bleeding with Cone
> supplied quad file for HPR and NK7 inks on my 2200.  So, I took the
> qidf file that is supplied with QTR for HPR 1440 and went to
> relinearize it for 2880.  Unfortunately, it turns out the 2880 puts
> down more ink so that the patch with the lowest L* is actually the 90
> patch rather than the 100.  The qidf file came with ink limit of 75
> and black boost of 95.  Is there a simple guestimate of what I should
> change with the ink limit in order to avoid the overinking?  My own
> guess is to take 90% of the 95 black boost limit (=85.5) and set that
> as the black boost.  Is that a good guess

...
>

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.