Yahoo Groups archive

Digital BW, The Print

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

Message

Re: Epson 960

2003-04-19 by Steven Karafyllakis

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "tonybun2001" 
<tonybun2001@y...> wrote:
> Hi Everyone.
> 
> I am brand new to this board.
> 
> I am thinking of purchasing the 960 printer.  Are there any 
workflows 
> for this printer?  Is this a good printer for BW photography 
printing 
> or is there a better one?

Hi Tony;


I think a lot of people are curious about that printer, but so far 
no one on this list has admitted (or had the nerve)to trying it. It 
has a 2 picoliter drop size, half that of a 1280, and recent posts 
suggest that the newest high-load pigment inks (which we all want to 
use because they have better fade-resistance) are at the ragged edge 
of what will pass through the (1280) nozzles. I would love to be 
proven wrong, but my gut feeling is that the 960 won't handle the 
black pigment ink. It might handle a hybrid like Generations 4, but 
the dye content of that ink compromises the lifespan of the print a 
bit. Also, there are no workflows for that printer, you'd be on your 
own. 

Most folks on this list are using: (in sort-of reverse chronological 
order):
A) 2200/2100  B) 1280/1270/1200/1160 C)890, 870, 940
and the occasional 7x/9x wide format machine. 
Interestingly, with the right workflow, the 4-ink machines are as 
good if not better at this than the six inkers, so if you want a new 
machine, the C-82 might turn out to be a viable candidate. Since it 
is arleady set up for pigments, it will probably do the job. It is 
still a bit early for even that one, I don't think you can get empty 
carts or prefilled with B&W inks, though you should check with MIS 
(www.inksupply.com) on that. 

Welcome to the list, and best success with your efforts.

Steve Karafyllakis

http://www.stevekphoto.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.