Yahoo Groups archive

Digital BW, The Print

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

Message

RE: [Digital BW] 2200 death and non-OEM

2007-10-27 by David Whistance

John

Although it is indeed very good I don't think that QTR with OEM inks comes
anywhere near the Cone K7 inks in terms of tonal graduation or smoothness
both of which are more important to me than outright Dmax.

David Whistance

  -----Original Message-----
  From: DigitalBlackandWhiteThePrint@yahoogroups.com
[mailto:DigitalBlackandWhiteThePrint@yahoogroups.com]On Behalf Of john kelly
  Sent: 27 October 2007 14:45
  To: DigitalBlackandWhiteThePrint@yahoogroups.com
  Subject: [Digital BW] 2200 death and non-OEM


  One lesson we might draw from the years of weeping
  here about clogged 2200 is to avoid 3rd party ink in
  2200.

  Easily 90% of the tears involve 3rd party inks.

  (someone happy with non-OEM usually jumps in to blame
  users rather than ink, but I generously attribute
  their reports of success to luck).

  Another observation is that reports of clogging seem
  to be increasing. Perhaps more people are using 3rd
  party inks, or perhaps 2200's are dying of old age.

  Having seen lots of examples of MIS/Piezo/OEM, QTR
  with OEM looks as good as alternatives anyway. MIS and
  Piezotone may produce faintly measurably better blacks
  on some papers, but OEM still reportedly does better
  on others, and the papers are changing.

  Some measurement reports seem dubious, some measuring
  folks seem constantly to be changing papers ( their
  love may be tinkering more than photography, and this
  is a printing Group, not a photo group after all).

  My own reluctant decision is to give my mortally
  clogged non-OEM 2200 a viking funeral and to continue
  to love my OEM 2200 until something better than 2400
  comes along (it sounds like 1800 is an Edsel).



  


[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.