Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] MIS Ultratones for the 2200: questions

2003-07-31 by Shilesh Jani

I have seen Daniel's evolving use of the 2100 (2200) printer, and I 
must say he has pioneered the best use of these printers for b/w.  I 
have seen some good prints on 2200s and OEM inks with a number of 
RIPs, but Daniel's method is the best I have seen so far.  There is 
no metamerism because no color inks are used (well other than the 
tonal modification of UT or VM).  He also uses diluted ink for the 
light gray position, so there is no longer an issue with highlight 
dots.  If I has a 2200 printer, his is the method I would choose.  
But I am waiting for UT-FS inks before I go the 2200 way.  I 
understand the 2200 is much faster than the 1280, hence my interest.

Regards.

Shilesh

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Daniel Staver" 
<daniel@p...> wrote:
> > Thanks!  Care to comment (anyone) on the print quality for 
(untoned) 
> > grayscale images using the MIS Ultratones v. using ImagePrint?  I 
> > believe you mentioned in an earlier post that MIS improves upon 
> > ImagePrints lack of shadow detail in dark tones.  Any other areas 
> > where it exceeds ImagePrint?
> 
> You get dotless highlights and better detail in the shadows 
(providing
> you are using the correct workflow). Honestly I think prints from
> Imageprint are really good, I'm not certain everyone would find the
> difference worthwhile.
> 
> You would probably do well to have a look at some prints made with 
the
> workflows you are considering before you make a change. And, since 
you
> already have Imageprint, I think I would wait a little bit and see 
how
> things play out with the empty cartridges, rips, inks and workflows 
that
> are coming for the 2200 in the following months.
> 
> --
> Daniel Staver
> http://daniel.staver.no

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.