Yahoo Groups archive

Digital BW, The Print

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

Thread

Weird results with new UT curves

Weird results with new UT curves

2003-07-03 by Charles Bandes

Hi guys - I guess this is a question for Paul.

I have a 1280 set up with UT ink (using the Photo Black)

I just tried some prints using the new curves and lustre paper.

My settings:

Color Space: Adobe RGB
Res: 1440
Curve: UT80-N
No Color Adjustment
Photo Paper setting

The print was bizarre - pure toner in some areas, pure "yellow" (warm grey) ink in 
other areas, highly posterized. I am getting perfect nozzle checks, no banding. I'm 
clearly doing something wrong, and I know the curves were designed for EAM, but 
they shouldn't be _this_ far off for lustre stock should they?

RE: [Digital BW] Weird results with new UT curves

2003-07-03 by Paul Roark

Charles,


>... 1280 ... UT ink (using the Photo Black) ... lustre paper.
>Adobe RGB... 1440... UT80-N...No Color Adjustment...Photo Paper setting

Those setting are right.  I have not tried luster paper in the 1280 with the
UT80-N curve, but it should be close, based at least on my experience with
the 1160 and UT inks.

>The print was bizarre - pure toner in some areas, pure "yellow"
>(warm grey) ink in other areas, highly posterized. ...

Assuming the image was converted to RGB before printing, the next thing I'd
check is the ink positions.  Print the Purge6 pattern and be sure the toners
are in the magenta and light magenta positions.  The yellow is the lightest
gray, then the light cyan, with the cyan the darkest gray.

Paul
http://www.PaulRoark.com

Re: [Digital BW] Weird results with new UT curves

2003-07-03 by Charles Bandes

Sorry for the initial panic, that first print was an anomaly, I've since made a couple of 
fine prints with those curves, I think that first one maybe the "no color adjustment" 
setting came unstuck or something. Sure looked odd! :)

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.