Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: Still Banding, no fatal error

2006-04-26 by Mason_Reid

I dropped the ink limit down max (-50).  I increased the gamma a bit 
to try to keep the midtones a little darker, based on some tests I 
had made.  I've just started monkeying around with the ink limit and 
gammas, so I may have it all wrong.  I spent most of Saturday trying 
to make my own curve, and got pretty frustrated (tried to modify a H 
Photo Rag curve off a website), and gave up after seeing that 1440 
gave me a closer print to the monitor.  Then when printing bigger 
prints I find that the 1440 gave me banding.  Lots of ink, lots of 
paper, lots of frustration.  But at least now I have a decent large 
print, and a slightly better understanding.  I'll continue to work 
on the curve.  If anyone has a modified curve for 2880 and HPR or 
EEM, I'd be grateful.  All the stock curves in QTR print really dark 
for me (2200).

Thanks for the help.


--- In QuadtoneRIP@yahoogroups.com, Howard Shaw <glassman@...> wrote:
>
> Mason_Reid wrote:
> > The banding is about 1/2 inch, regularly spaced, and pretty 
subtle.
> > They occur primarily on the first half of the print in (blue)sky
> > areas. I changed to 2880, dropped the ink limit, raised the 
gamma,
> > and I got a good print.  2880 prints are considerably darker than
> > 1440.  And the banding is only noticeable on larger (9x19in) 
prints,
> > which is what I'm selling.  Smaller proofs don't show the 
banding.
> > 
> > Thanks.
> > 
> More ink is deposited at 2880dpi so you'll need to reduce the ink 
limit 
> by 40-50%. You shouldn't need to change the gamma. Preferably you 
should 
> make new curves.
> 
> Does the banding actually disappear at 2880dpi? I had a similar 
problem 
> but with horizontal banding and never managed to fix it so now I 
> restrict myself to 2880dpi.
> 
> Howard
>

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.