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-22 by Shilesh Jani

Carl,

Thank you for your observations. I am getting a new 2400 shipped to 
me and I am going to try the NanoChrome K ink with UT-FS inks for b/w 
printing on Hahnemuhle papers. I plan on keeping the OEM LM and LC 
for toning purposes.

Shilesh

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, Carl Schofield 
<scho@m...> wrote:
>
> Shilesh,
> 
> Dither still looks good on most papers.  Epson Premium Semimatte 
gave  
> me some problems with bad bronzing.  Tried using QTR for that 
paper  
> so I could reduce ink limit, but had to go all the way down to 
limit  
> 30 to get rid of bronzing and then took a big dmax hit because of 
the  
> low limit.  Dither seemed coarser on semimatte also (this is a 
very  
> smooth surface so it shows imperfections more readily).  I've only  
> had the Nanochrome K loaded for a couple of days but no clogging  
> problems so far.
> 
> Carl
> 
> On Jan 21, 2006, at 1:56 PM, Shilesh Jani wrote:
> 
> > Carl,
> >
> > Yup, the K ink is cold. That dooes not bother me in QTR printing.
> >
> > When you printed BO with these inks on your 4000, what is your
> > opinion of the dot structure (dither)? Is it as smooth as the OEM 
PK?
> > I belive the 4000 has one of the smoothest structure, much better 
in
> > BO than 2200, 1280, etc. I have a suspicion that is why the Dmax 
is
> > lower on the 4000. The R220 is rather a coarse machine for BO and
> > also for QTR with the inkset up I have used.
> >
> > I am not quite ready to put these inks (or even just the K) on my
> > 4000. When you loaded the K on your 4000, did you find issues with
> > clogs due to interactions with the PiezoTone inks?
> >
> > Regards.
> >
> > Shilesh
> >
> > --- In DigitalBlackandWhiteThePrint@yahoogroups.com, Carl 
Schofield
> > <scho@m...> wrote:
> >>
> >> Shilesh,
> >>
> >> You probably noticed that the K ink is also an icy cold blue.  I
> >> tried using it for BO printing in the PK slot of my 4000 (other
> > slots
> >> are using piezotones right now) and got some very nice looking BO
> >> prints on Hahnemule Photo Rag Satin (dmax 1.93) with no bronzing
> > or
> >> GD, but the icy blue hue is just too much for me.  If this cold
> > hue
> >> of the black inks can be effectively neutralized in QTR then I 
may
> >> switch over to the full inkset.
> >>
> >> Carl
> >>
> >> On Jan 21, 2006, at 1:31 AM, Shilesh Jani wrote:
> >>
> >>> 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
>

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.