Yahoo Groups archive

Digital BW, The Print

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

Message

RE: [Digital BW] UT1 again, or move to UT2

2004-02-04 by Paul Roark

Jerry,


>... 1280 ...
>...stay with the original UT1 or move on to the new UT2 inks.   
 
>... I still prefer to do most of my work on a paper like EEM, but
>occasionally it seems appropriate to use a glossy or pearl surface paper.
>Would it be worth my time and money to invest in a second black (PK?) to
>allow me to use the glossy or pearl surface paper?  


There is nothing wrong with the original UT inks (UT1).  I am going to keep
them in my 7500.

UT2 does give 1280/90 (and soon 2200 etc.) owners some worthwhile features.
These are the added features that cause me to put UT2 with Eboni in my 1280
(and future inksets will build on UT2).  

UT2 gives me sepia tone.  For reproducing & restoring old photos, this is
very nice.  Sepia tone prints also do better in mixed media competitions. 

UT2 gives me better RC performance.  UT1 had light inks that were needed for
the old quads.  UT2 goes to denser (on average) inks and holds down the
liquid that can flood RC papers, causing spots in the darker midtones.  It
also corrects the shadow tones of many RC papers.

UT2 gives me glossy and matte printing without having to change black inks.
Photo K still has about a 5% dmax advantage over the "Eboni-glossy" UT2
curves.  Also PK would allow printing on glossy without curves.  The UT2
"Eboni-glossy" method requires RGB conversion and curves.

UT2 gives me the ability to print without any image editor and still have
some control over tone/hue.  Page layout, including some genealogy
publishing programs will benefit from this.  (Competition and lowering
customer support costs is also a nice benefit.)

Hope this helps you make a decision.

Paul
www.PaulRoark.com 

For UT2 information, curves, and settings see:
http://home1.gte.net/res09aij/

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.