Yahoo Groups archive

Digital BW, The Print

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

Message

Problem Printing Black in Corner With QTR

2006-06-17 by michaelrosensf

Sometimes I like to burn edges and corners gradually to black. I've always had a problem 
doing that with QTR and my 2200. The problem I'm showing here looks like my 2200 
stops laying down black ink when it gets to the corner at the right side of the printer. (I'm 
using High Speed = "better", not "faster".

I've scanned some test strips and put the result  on my web site demonstrating the 
problem - and "solution" - at http://www.shaynew.com/temp/cornerproblem.jpg.  I've 
used a Photoshop adjustment curve to exaggerate the differences somewhat.

The top strip is a print from QTR, 2.4.1. I used Roy's QTR Gray Lab space and printed with 
Let Photoshop Determine Colors, QTR-Gray Matte Paper, Perceptual, Black Point 
Compensation = ON (although I've seen the problem with other settings). Print Resolution 
= 1440 super and High Speed = "better". The left corner of the strip, which came out of 
the right side of the printer, shows the problem; the corner should be at least as black as 
the area next to it. The right, which also goes towards black, is fine (but if you look very 
closely, you'll some banding).

The next strip down is the same strip flipped horizontally (Flip Canvas Horizontally). What 
was the left corner, now on the right, is fine (except for some banding). What was the right 
corner, now on the left, shows the same problem!

Is there something wrong with my 2200, that it has a problem printing black at its right 
side? No. The bottom strip was made with one of the Roark curves and the Epson driver. 
Everything is fine! And no banding.

I printed on EEM, using the curves that came from Roy's installation, at 25/75 cool/warm.

Anybody see anything like this? I'm happy to email a file to someone to print on her 2200 
printer.

Michael

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.