Yahoo Groups archive

Digital BW, The Print

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

Message

RE: [Digital BW] NanoChrome QTR Printing

2006-01-21 by John Moody

I get that Dmax with UT7 and dotless highlights.  I’m struggling to
appreciate what exactly the Wow factor is with these inks for BW.  Help me
out.

Best regards,
John Moody

-----Original Message-----
From: DigitalBlackandWhiteThePrint@yahoogroups.com
[mailto:DigitalBlackandWhiteThePrint@yahoogroups.com]On Behalf Of Shilesh
Jani
Sent: Saturday, January 21, 2006 1:31 AM
To: DigitalBlackandWhiteThePrint@yahoogroups.com
Subject: [Digital BW] NanoChrome QTR Printing

Hello All,

This is not about whether these inks are dye, pigment, infused, or
not. I am intersted in printing b/w on rag and sometimes RC papers
using a single color inkset. I currently use a 4000 with OEM UC inks
for b/w (90%) and color (10%) prints. My reasons for exploring
NanoChromes (1) I just like to play with inks, (2) get better Dmax on
matte papers, and (3) be rid of the pesky gloss differential/bronzing
on RC papers.

QTR is an awesome tool - thank you Roy Harrington!

The challenge posed by the NanoChrome inks is the relatively
cool/blue tone of the grey (LK) ink. My experiments are conducted on
an R220 printer. I filled the LK ink in the redundant C position.

In QTR ink configuration, I have been able to neutralize to a great
extent this problem. For EPSG paper the settings that work are:
Default limit = 80%, NO K boost
LK Density = 30
Y Copy Curve from LK, limit = 6%
LC Copy Curve from LK, limit = 2%
LM Copy Curve from LK, limit = 20%

After linerarization, the prints on EPSG, EPG, and Kirkland papers
are, well, stunning! My prefered paper is EPSG. Dmax is in the 2.4
range.

The fade resistance of these remain unknown, so I am waiting a bit
more before loading these inks onto the 4000.

Regards.

Shilesh





[Non-text portions of this message have been removed]

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.