Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] Epson 9500 sold - 9000 as alternative?

2008-07-01 by Tyler Boley

My understanding was that the 9000 should have slightly better image quality than the 
9500... at any rate, a 4k+ inkset would do quite nicely in a 9000, I've seen many 
wonderful quad prints by excellent workers made this way. A 6k inkset would, of course, 
be optimal in terms of more photographic output from that model, and would certainly 
give outstanding results.
Just my opinion, but if one is happy with the hue provided by an available inkset, the 
variable hue options are over rated. Many great darkroom workers found something they 
liked and printed to that same look for decades. Personally, for my work, I love to do 
subtle hue tweaks to my images, but often have second thoughts seeing more and more 7 
and 7k output these days, particularly on different papers.
Tyler

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Joost Horsten" <j.h.j.h@...> 
wrote:
>
> Hi all,
> 
> Encouraged by your feedback I went out to buy the Epson 9500. But 
> alas... it was already sold :-(
> 
> I've been looking further around and spotted a 9600 (no doubt a very 
> good printer, but they ask too much). I found a 9000 as well. All 
> comments given on the maintenance need on the 9500 apply here as well 
> of course. So I am rather cautious...
> 
> But apart from that, is this "antique" type of printer (6 inks, fixed 
> 10 pl droplets) able to create high quality B&W prints? I expect that 
> a 4K+ inkset is a no-go for this printer. But would a 
> Carbon/Eboni/Cone-6 give top-notch results? I am willing to give up 
> the toning/glossy capabilities of 4K+, but I am not pepared to settle 
> with substandard print quality. Then I'd rather look around further 
> for another 9500 or a cheaper 9600. 
> 
> Joost
>

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.