Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] Re: "1400 NC2" inkset approach

2009-05-27 by Ernst Dinkla

pr_roark schreef:
> To update this approach, I've found that I simply don't need any more than the HP PK for glossy printing for what I do.  The 1400 with HP PK in black only mode, with QTR, is just fine quality and tone wise, and BO keeps the artifacts under control better. For the glossy brochures I don't need 100% carbon.
> 
> However, my serious prints remain 100% carbon (Eboni) on matte paper.
> 
> So, I've gone to 2-Eboni-MK, 2-Eb2%, and 2-HP-PK in the 1400.  The only inks I need to buy and keep for this 1400 setup are the high density, relatively economical (more image area per dollar) MK and PK inks.  2% Eboni can be purchased (Eboni-6 Y position), but I mix C6b base for mine.  Carts need to be changed less and it's easier -- only 3 inks.
> 
> Very simply profiles and the QTR sliders seem to be all I need with this setup -- almost too easy to be any fun.  It actually leaves some time for photography.
> 
> (Epson, I'm still waiting for my 24" 1.5 pl printer.)
> 
> Paul
> www.PaulRoark.com 

Paul,

The Eboni 2%, what spot would it take in a quad setup ?

I'm interested in a similar A4 B&W printer, in the EU it will be the 
R285 with 1.5 pl but using HP Vivera MK + PK + LGrey ? inks in it.
The same way you mention. Choices for Vivera grey ink are just two. QTR 
probably doesn't have a driver for it but there might be a US A4 driver 
equivalent that copes.

The printer is at 80 Euro, feeding it with leftover ink of the Z models 
must be possible, though they drain the carts down to a few ML.

-- 
Met vriendelijke groeten,   Ernst


New: Dinkla Canvas Wrap Actions

|      Dinkla Grafische Techniek      |
|         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.