Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] Vertical banding with QTR 2

2003-11-02 by Roy Harrington

As Carl mentioned 1440x720 Highest Quality is the resolution that has
been most tested and calibrated.   So I'd recommend that.   
I really don't know the cause of the strange banding that your example shows.
Its possible that some of the driver dot size tuning will fix it but I'm not
sure.  

Roy

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, Carl Schofield <scho@m...> 
wrote:
> I just recalled some problems we had with curve breaks in the shadow 
> areas, before the 2200 dot size weightings were adjusted, and that may 
> be the source of your problem in this particular image.  I believe that 
> Roy is planning to release an update that may correct this problem.
> 
> Carl
> 
> On Saturday, November 1, 2003, at 10:01  PM, candlefarmer wrote:
> 
> > I've recently started experimenting with the Harrington Quadtone RIP 
> > v2. I'm using the
> > latest beta on an Epson 2200 with the standard Epson inks. Generally 
> > the results are
> > outstanding but I continue to have one show-stopper problem: vertical 
> > banding in
> > dark areas of the print. This seems to be specific to the QTR RIP - 
> > the same image
> > printed using the epson driver shows no such banding.
> >
> > It seems to be independent of resolution. I typically use 720x720 but 
> > see it in higher
> > resolutions also.
> >
> > I originally thought that the banding was due to excessive ink in dark 
> > areas. I tried
> > lowering the ink limit but the banding remains.
> >
> > I've posted an example here:
> >
> > http://home.comcast.net/~baur/banding.html
> >
> > Is this something others have seen? Any help in taming this would be 
> > appreciated. (I'm
> > trying to get a couple of things printed for a show and this is 
> > driving me batty.)

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.