Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: [QuadtoneRIP] Re: 2880 vs 1440

2010-03-31 by Michael King

Roy,

Should we expect the 2880dpi mode to also invoke more smaller dot usage?
Hence maybe an advantage to 3MK users?

Also the R1800, 1900 and 1400 have a superfine mode 5760dpi mode.
Can we activate that through QTR?

Txs,

Mike

On 30 March 2010 21:55, Roy Harrington <roy@...> wrote:

>
>
> The different dpi's should use about the same amount of ink for the
> same print density.
> Yes, you probably need different ink limits for the different dpi's
> but once you get it
> so the same density print comes out the ink usage should be very close.
>
> The main cost to 2880dpi is just the extra time to print.
>
> Roy
>
>
> On Tue, Mar 30, 2010 at 9:41 AM, dj_joy_uk <yahoo@...<yahoo%40joy.org.uk>>
> wrote:
> > --- In QuadtoneRIP@yahoogroups.com <QuadtoneRIP%40yahoogroups.com>,
> Michael King <drmrking@...> wrote:
> >>
> >> I am using 2880 and only 2880. Why use anything else :)
> >
> > I never really use it as it's usually a waste of ink, the differences are
> imperceptible on most papers.
> >
> > When I was profiling Epson Exhibition Fibre/Traditional Photo Paper on my
> 7880 I tried an ink limit test on both 1440 and 2880.
> >
> > Naturally the 2880 saturated well before the 1440, the ink limit on
> 1440dpi was 85% and on 2880dpi it was 70%.
> >
> > When I subsequently printed out the calibration strip again with the
> respective ink limits set, the DMAX at 100% on both 1440dpi and 2880dpi was
> absolutely identical.
> >
> > So if there is a benefit in printing 2880dpi, it's not DMAX. There may
> feasibly be some difference in smoothness, but I've not compared, I may do
> some testing out of curiosity.
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>
>  
>


[Non-text portions of this message have been removed]

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.