Yahoo Groups archive

Digital BW, The Print

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

Message

Re: Which printer for B&W

2012-09-09 by lurique2003

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, Paul Roark <roark.paul@...> wrote:
>
> lurique2003 <lluisrq2009@...> wrote:
> 
> > **
> >
> >
> > ... I want do the best as possible B&W, without cast greenish/pinky or
> > magenta.
> >
> What is "best" depends on the goals.  In terms of lightfastness, 100%
> carbon is the best.  Since it can also be the cheapest, it ought to be at
> least considered.  The inkset I use for fine art is Eboni-6.  See
> http://www.paulroark.com/BW-Info/Eboni-6.pdf.   My general approach is
> outlined at my general B&W information page at
> http://www.paulroark.com/BW-Info/ .
> 
> I do think an Epson printer supported by QTR <
> http://www.quadtonerip.com/html/QTRoverview.html> adds a dimension of
> flexibility and control that otherwise might be lost.  Epson printers also
> have more third party ink options available.
> 
> Some Canon models are supported by a B&W rip made by Bowhaus --
> http://www.bowhaus.com/index.php4 .  I have not used their current
> software, so I can't comment on it.
> 
> Paul
> www.PaulRoark.com
> 
> 
> [Non-text portions of this message have been removed]


Paul, 

Thank you very much for your response and all the information, I'm sorry for my ignorance,  carbon are the pigmented inks used in Epson R3000 or Pixma 9500? .

I have to learn a lot of things, what do you say about the Eboni inks is very interesting, also about the possibilities to use different inks in Epson, I think my decision will be for this one, as a most popular printer.

I realize we was already in contact throught the Leica Users Group, my Gallery : < http://gallery.leica-users.org/v/luisrq/
>, I've already saw your B&W pictures, they are excellent!

Thank you very much!

All the Best!
Lluis

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.