Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: Starting from the beginning...

2009-03-09 by robert49brake

--- In QuadtoneRIP@yahoogroups.com, "michaeldsji" <michaeld1001@...> wrote:

> 
> It's time to use those Relative Density numbers, and this is where it gets dicey. Page 4 of the 2.5 Calibration Guide starts talking about Dot Gain Compensation Calibration. I don't see any connection of this to the determination of the relative densities so I saveit for later and decide to move on to the "Getting Started with QuadToneRIP 2.4" Guide. 
> 
> I make a copy of the UCmk-EpsEnhMatte-Warm.txt file in the 9880-UC profiles folder. Open it in TextEdit and start hacking away. I'll slow down here because this is where my questions will really begin:
> 
> 1) Am I on the right track to make an adjusted profile for printing on Epson Enhanced Matte paper on the 9880 printer?
> 
> 2) Assuming I'm on the right track, I changed this part of the profile text file from this:

This is where I am a little confused.  You have printed on EEM successfully using the pre-existing profiles?  And now you want to profile your machine so that you have a custom profile for EEM on your machine?  If this is the case,  simply take the existing profile that you have printed with, erase the linearization line and all that follows.  Then print out a 21 stepwedge, read that wedge and redo the LINEARIZATION= line using your numbers from your 21 stepwedge.  That will accommodate any dot gain difference between your machine and the machine that the profile was made on.

I am not familiar with the large format printers so bear with me here.  If you were able to install the existing profiles, print successfully with the existing profile and they show up under QTR without any problem, then it may not be necessary to change the 4880 to 9880 etc.

Hope this helps, Robert

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.