Yahoo Groups archive

Digital BW, The Print

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

Message

Re: "Carbon-6" Ink Mixing

2008-03-13 by pr_roark

> Are you using Photoshop or QTR with your 7600 / Carbon-6 setup?


I'd like to hear how the alternatives work in the 7600 also.

I'm using the Epson driver in my test 220, but I use an ICC made with
Create ICC-RGB and a Photoshop curve that is similar to (in fact, now
exactly the same as) the one I made for the Eboni-6 beta inkset and
downloadable from http://www.paulroark.com/BW-Info/Eboni-6-profiles.zip
<http://www.paulroark.com/BW-Info/Eboni-6-profiles.zip>

The curve that is in the ICC partitions the inks -- Y used exclusively
in the highlights, then the M channel starts and finally the C channel
starts.  It's perfectly smooth.  While a k2 printer can also get away
with a simpler no-curve Create ICC linearization, the same curve seems
to work for virtually all (matte) papers.  So, using the curve is no
more work.  I'll make a curve specifically for Carbon-6 at some point,
but for now the Eboni-6 curve works fine.

I like the Create ICC-RGB workflow not only due to its ease, speed, and
"color management" matching of the print to the monitor (relative
densities only with the existing curve -- more later), but also because
it gives a high bit pipeline all the way to the printer.  I edit in 16
bit grayscale, and the PS CM engine used in the Print Preview, which I
believe is 16 bit, outputs a 24 bit signal to the printer, overcoming
the usual 8 bit constriction there.  While I understand that this is
probably overkill, it makes me feel good that, if my understanding is
correct, I'm probably not losing any information in the pipeline.

Being a Windows user, I also very much appreciate being able to print my
draft images right from PS.

Paul

www.PaulRoark.com <http://www.PaulRoark.com>









[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.