Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] Blending BW and color in a single print

2006-03-09 by Olivier

Fist sorry for the double posting : I'd better stop coffe, I'm 
shaking !!!

Yes BO was understood as referring to K only. I'd agree on a RIP 
using all Ks available. But if one does not plan toning don't you 
think there could be an issue with the neutrality of the greyscale 
depending on Ks "natural" tone variations ? Ideally, one would choose 
to disregard colors so that only carbon pigments are used to secure a 
(unique) tone stability over time.

The second option is also one I was contemplating : generate a BW 
profiled with QTR NB part and mixing with the RVB part color-managed
(via document duplication that are converted according to the RVB-NB 
nature of the document, then paste in a single one not color managed 
at the PS level and send to the printer icm off) : the issue remains 
that colors will be called for in the BW part by the driver.

The whole issue would be to "switch off" color inks and don't use 
them when BW is detected in the file, while full 8col would be at use 
for RVB part.

Am I talking non-sense ?

Olivier

> My message may not be clear enough. The BO option is the usual 
> output for greyscale images in RIPs. I'm advocating an extra 
> choice in the use of Kkk inks instead (+ toning for 
> neutrality, sepia, cool). That would allow good B&W printing 
> in a RIP + the combination of good B&W printing and color 
> printing. Another possibility would be to direct greyscale to 
> an RGB flow as well but give it another profile/paper setting 
> treatment with total black generation from 100-0% and the 
> profile more directed to neutrality.
> 
> Ernst
> 
>                     --
>            Ernst Dinkla
> 
> 
> www.pigment-print.com
> (         unvollendet         )
>

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.