Yahoo Groups archive

Digital BW, The Print

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

Message

Re: QTRIP Calibrating Ink Density w/PS

2004-02-06 by Kees Brandenburg

Tim,

When I started with QTR I did not have a densitometer too. I had great
results with my old Umax powerlook II scanner and Vuescan. Nice about
Vuescan <http://www.hamrick.com> is that it can be used for density
readings. It uses the raw output of the CCD for that. Optical density
readings are measured as log (max_colour from CCD/raw_colour from CCD.

These density readings can be accessed in Vuescan when moving the
pointer over the scanned image while holding ctrl.

When I remeasured inkseparation points with my second hand XRite the
fell on exactly the same spots. Linearisation worked fine too.

Hope this helps






> QTRIP Calibrating Density with Photoshop
> 
> As I do not own nor have access to a densitometer, I am trying to 
> perform the Ink Density calibration for QTRIP v2.0 beta8 using 
> Photoshop 7 and my old Epson Perfection 1200 scanner. This is for an 
> Epson 1270 using MIS VM inks with Ebony black.
> 
> After doing the Hardware Ink Limitation Calibration(which I settled 
> on 90), I printed out the QuadtoneRIP Ink Pattern Page in Calibration 
> mode (with BOOST_K disabled). I then scanned the resulting image into 
> PS using Silverfast Ai 6. I disabled all calibration and color 
> correction in Silverfast and scanned in RGB mode converting to 
> grayscale in PS.
> 
> The problem is that my 100 Black is only 85%in PS (38 RGB). I assume 
> that I should be getting a reading of 100% or something close to it. 
> Although I can correct this in Silverfast or PS I would think that 
> this would defeat the whole purpose of the calibration process.
> 
> What have I done wrong and how can I correct this ?
> 
> Any and all help would be greatly appreciated.
> 
> Thanks
> Tim Goodwin
> 
> [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.