Yahoo Groups archive

QTR-Quadtone RIP

Index last updated: 2026-04-28 23:12 UTC

Message

RE: [QuadtoneRIP] Epson 2200

2007-07-27 by Ken Barrett

Hi Tom,
I have just started printing B&W on the 2200.  I have
tried a variety of settings, etc.  I have downloaded
the various paper profiles and yet I'm getting a color
cast on all B&W-some more than others.  I DO NOT have
any RIP software.  Everything I got came with the
Epson printer.

Perhaps I should ask the question: What steps are
needed to get good B&W with the 2200 without
purchasing software that cost $400-$500?
Thanks for your help, Ken



--- Tom Moore <rtmlists8888@...> wrote:

> Ken
> 
> You state that your print engine is CS3. Just to
> make things clear to all,
> please confirm that you are printing through
> QuadtoneRIP. This is a
> QuadtoneRIP list, afterall, so one would assume
> that's the case. If that is
> the case and you are using Epson UC ink, give us an
> example of a curve and
> paper combination that you have tried that gives the
> colour cast. How severe
> is the colour cast.
> 
> Many people (myself included) have used QTR with
> Epson ink with "reasonable"
> results. People who do move to other reduced gamut
> inks do so as much for
> their archival properties as for esthetic reasons. 
> 
> Tom Moore
> 
> > -----Original Message-----
> > From: QuadtoneRIP@yahoogroups.com
> [mailto:QuadtoneRIP@yahoogroups.com] On
> > Behalf Of Ken Barrett
> > Sent: Thursday, July 26, 2007 5:47 PM
> > To: QuadtoneRIP@yahoogroups.com
> > Subject: Re: [QuadtoneRIP] Epson 2200
> > 
> > Hey Ralph,
> > I use CS3 and the ink is the regular Genuine Epson
> Ink
> > for Epson Stylus Photo 2200 341, 347, 342, etc.
> > Ken
> > 
>  
> 
> 



       
____________________________________________________________________________________Ready for the edge of your seat? 
Check out tonight's top picks on Yahoo! TV. 
http://tv.yahoo.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.