Yahoo Groups archive

Digital BW, The Print

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

Message

Re: Carbon-6, 2200, & C88+

2008-04-28 by Mark McCarvill

Thanks, Paul. I was looking at the 3-11-08 version of the PDF, which
doesn't mention LK. I should have checked for a later version!

Mark 

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "pr_roark"
<pr_roark@...> wrote:
>
> Hi Mark,
>  
> > You mention using LK as part of your Carbon-6 setup here, 
> > but I didn't see LK mentioned in your Carbon-6 PDF. 
> 
> At page 3 of http://www.paulroark.com/BW-Info/Ink-Mixing.pdf in the 
> Mixing Ratios section I note that the M position ink (16.7% Eboni) is 
> also used for the LK position.  I probably ought to make it more 
> clear.  
> 
> > On a related note, I was wondering why only 6 position in Carbon-6.
> > Would adding a 7th position not make any practical difference on a
> > 7-position printer like a 7600? 
> 
> At least if one is using the Epson driver, the k2 printers clearly 
> must have all 7 positions appropriately filled.  The 16.7% M position 
> ink is the appropriate density to work well with the Epson driver.  I 
> don't think yet another density would have any impact on smoothness.  
> 
> For simplicity, I've limited my write-ups to one set of dilutions -- 
> the same for the Epson driver and QTR.  That way one can try each 
> workflow and see what works best.  I, in fact, find myself using the 
> Epson driver with an ICC made with Create ICC-RGB.  But, if one wants 
> to use QTR exclusively, there is obviously more flexibility as to 
> what the LK position is used for.
> 
> > I was curious whether diluting Y 1 to 1 with base would 
> > make prints any smoother - and using this dilution as #7.
> 
> I don't think you'd see any difference even with a loupe.  The 2.1% Y 
> mix in a modern printer is extremely smooth.  Then again, give it a 
> try and let us know.  If you're using QTR or other rip, it's easy 
> enough to try it.
> 
> 
> Paul  
> www.PaulRoark.com
>

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.