Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] Questions about Using Color Settings and Workspace Profiles for Grayscale Printing

2006-02-26 by Steve Kale

The QTR Create ICC profiles only have one intent,  This intent is
effectively media white relative colorimetric with black point compensation.
So all the measured data is scaled in XYZ_Y for media white point and then a
scaling is also done for black point compensation at the black end.  Roy
could likely add more.


> From: Olivier <odesmais@...>
> Reply-To: <DigitalBlackandWhiteThePrint@yahoogroups.com>
> Date: Sun, 26 Feb 2006 09:55:51 -0000
> To: <DigitalBlackandWhiteThePrint@yahoogroups.com>
> Subject: Re: [Digital BW] Questions about Using Color Settings and Workspace
> Profiles for Grayscale Printing
> 
> Can someone further elaborate on the choice of selecting Perceptive
> vs Relative in Create-ICC.
> 
> I would tend to believe that with Relative the Grey Scale would
> eventually not be evenly distributed since compression vs clipping
> would not occur, but there's confusion for me here...and a lot !
> 
> Thanks
> 
> Olivier
> 
> 
> We
>> want to manage luminance/density but leave the colour alone.  In
> other words
>> we want to use colour management technology to manage the inevitable
>> compression of luminance from a perfect scenario (the file) to an
> imperfect
>> scenario of ink black and paper white.  But we'd also like full
> colour soft
>> proofing and not just a soft proof of this luminance management.
> Roy's QTR
>> Create ICC is used to write an ICC profile (not really to official
> specs)
>> which only has luminance management in the outbound leg but full
> colour
>> information in the inbound soft proofing leg.  In essence we get
> the best of
>> both worlds.  We can use a more B&W oriented driver (eg Adv B&W) or
> RIP but
>> still use colour management for luminance compression and soft
> proofing.
>>

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.