Yahoo Groups archive

Digital BW, The Print

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

Message

Re: using PFP to create QTR profile data

2007-06-07 by Roy Harrington

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "David Keenan" <ausdlk@...> 
wrote:
>
> >just print the target, use the measure tool of PFP, check the box "QTR
> >Format Ovewrite" and read the patches.
> 
> Thanks. The process seems simple enough.
> 
> But since ABW is not a ICC based process, I would assume that the QTR ICC
> has no bearing on the actual printing of the print.
> 
> If that is the case, then the QTR ICC process really just results in a
> method to soft proof within PS.
> 
> Is the summary correct? If it is, why specify the ICC profile at all when
> printing?
> 
> I must be missing something. Basically, other than the soft proof, what's
> the point of a QTR ICC (or any ICC) when printing in ABW mode?
> 
> Dave.
> 
> -- 
> Portfolio: www.david-keenan.com/portfolio
> Web Site: www.david-keenan.com
> 2007 PAW: www.david-keenan.com/paw
> 

Dave,

ABW is only non-ICC based in that Epson does not provide any ICC profiles.
ABW is just a print driver -- you can profile it and be ICC based or just print to it
non-ICC based and get what you get. 

Printing to ABW goes through all the same code so it's perfectly reasonable to
profile it and print with the profiles.   QTR-Create-ICC does exactly that -- it
profiles the ABW driver and allows the color management system convert from 
whatever embedded profile is in the source to the output profile.

Since the output to the screen is ALWAYS profiled -- you can't disable it -- the
logical thing is to print profiled as well.   It's the only way to get screen-to-print
consistently matching.

The softproofing capability basically provides a way to see the reduced dMax by
using Simulate Ink Black and a way to see the tone/hue of the print (like warm or sepia).

Roy

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.