Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] C84/C86 & EZB&W.

2004-11-06 by Lee Hiers

On 6 Nov 2004 at 4:17, Lynn wrote:

> To Lee:  in this part of your message (see quote below), I got 
> confused. What is different about the inks you're using compared to the 
> EZ-Warm set the MIS sells ?

I'm using a regular EZ set, but in the Yellow position, I'm using an 
EZ-W "yellow" cart to get a tone somewhere between the EZ and EZ-W 
sets.  If you haven't read Paul's notes on the EZ inks, go to 
http://tinyurl.com/4mny8 which is where I got that idea:

"Of course, the neat trick of putting a warm cart in the Y spot for 
slightly warm and M spot for medium warm tones is a neat trick that 
should be promoted."

> To All: The only thing I wasn't sure of with either EZ set was whether 
> that second ink is pure carbon pigment like the black ink in the set.

Per Paul's reply to my post, the EZ-W is all carbon.  I believe the 
regular EZ ink is carbon plus small amounts of dye to cool the tone.  


> The C84 or C86 with EZ-warm carbon inks is one of the things I'm 
> planning to buy for dedicated B&W on watercolor type paper. I'm still 
> not settled on a color printer yet. Small though it is (up to 8.5x11 - 
> I can't find anything equivalent to it for b&w  elsewhere - I wish the 
> manufacturers would release these various excellent small printers in 
> larger format very soon.

I wouldn't count on it, but it would be neat if there were a larger-
format printer of similar quality that only used 4 inks.  The name 
"EZ" for these inks is appropriate.  I think it gives me less to 
worry about as I'm learning the whole digital thing!  I'll probably 
end up getting the 1280 or 2200 anyway so I can do BO and color with 
the same printer.  

Have fun!

Lee


-- 
Lee Hiers, AA4GA
Cornelia, Georgia

"Have Dobro Will Travel"

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.