Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] Materials Ord ering for Paul Roark ’s Glossy C arbon Variable Tone Black and White Inkset for Epson Printers

2016-06-08 by Paul Roark

The color inks that go into MIS's UT14 make a light blue toner that is essentially the same as the Canon based toner I prefer due to its superior lightfastness. The UT14 "blue" blend diluted 30% UT blue (not sold separately) and 70% amber base is all there is to it. MIS is sending me a blend of the current inks (still the original IS pigments, we';re told) to test. Assuming they check out, MIS should have a more affordable light blue, carbon toner soon.

I have never actually fade tested the MIS blue blend v. the Canon blend. I have relied on http://www.aardenburg-imaging.com/ testing, which consistently shows OEM color pigments performing better. MIS's major problem with its color set was similar to Epson's -- a weak yellow. With respect to the others, my old tests of the MIS neutralized carbon inks v. Piezo's versions showed them to be essentially equal. So, based on those tests, I'd assume an MIS light blue toner in and Eboni or glossy carbon variable tone inkset would be about the same as the Piezo B&W inks of the same shade. For most B&W printing, that has worked out fine for many people. For those who want to challenge silver print stability, stay with the Canon color pigment based toner.

Paul

On Wed, Jun 8, 2016 at 2:53 AM, homershannon@... [DigitalBlackandWhiteThePrint] <DigitalBlackandWhiteThePrint@yahoogroups.com> wrote:

Inkjetcarts part numbers 106 RKB-120 and 106 RKC-120. These are both 120ml bottles "OEM matched pigment refill ink". It is safe to assume this is not Canon ink but a knockoff of unknown quality, but I can't see purchasing two huge cartridges of expensive Canon ink just to trial this formula.


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.