Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: [QuadtoneRIP] Re: banding and dithering with QTR and UT14 Epson 1500 (1430)

2013-02-01 by Paul Roark

Ross, <ross.jarvis@...> wrote:

> **
>
>
> I have now used the cool and warm curves mixed and am getting much better
> wedges. I've compared these to a print via the Epson driver and they are
> way smoother. 2880 resolution uni-directional definitely gives the best
> result. ...
>
To see how adding yet another neutral ink would look, try setting up the Y
position (your second LC) as follows:  Have the Y curve copied from the LC
curve; use an ink limit on LC and Y that is half of the current LC ink
limit.

Basically, the more inks we have firing at a time (within reason) the less
likely we'll have visible microbanding.

One issue for moving to a replacement for the glop (UT14 Y) is whether a
lighter ink has any value in the 1430 and similar 1.5 pl printers.  I,
personally, doubt a lighter ink is needed for the highlights and, further,
feel that having another ink firing in the midtones to fight microbanding
there would be more valuable.  That is part of what I'll be looking at.

Note that with multiple same-density inks, one gets smoother highlights by
starting one ink at a time.  That was what was behind the 1800 3MK curves
and their staggered starting points. The same type of approach helped the
"EZ" types of setups that have 3 identical "color" inks in them that start
at the same time with the Epson driver if a curve is not used (embedded in
an ICC) that staggers the starting points.  Unfortunately, QTR had no
automatic way to do this, as far as I know.  So it takes some manually
drawn curves.  The use of the sliders and separate profiles for the
different LK density inks might be close.  I'll have to check that out also.

Paul
www.PaulRoark.com


[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.