Yahoo Groups archive

Digital BW, The Print

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

Message

Re: MIS K4 all colors – Epson K3 Microencapsulation – present workableness of MI

2005-12-12 by Bob Michaels

Peter: my excellent experience with the MIS PRO matches yours. I use
it in a 1280. That's why I was hoping the MIS PRO and the K4 were the
same. Unfortunately, MIS says the MIS PRO is not usable in a 2400. 

Anyone got a report on how the K4 does?

Bob Michaels

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "bwbonkers"
<PeterDLevis@a...> wrote:
>
> Jerry
> 
> I cannot answers your question with regards the K4 inks but I did
recently do a 
> comparison with MIS Pro vs Epson ink in a 2100.  My friends 2100 had
MIS Pro ink and 
> mine Epson ink. I  made profiles for Olmec Satin with my EyeOne
using the same settings 
> for each setup. We then printer the same test chart from each
printer. Looking at the test 
> print side by side it was hard to see much difference. The MIS print
looked to us just as 
> good as the Epson print. We were both very impressed by the MIS
print. We also both 
> thought that the MIS print exhibited less metamerism than the Epson
print. Apart from 
> making a custom profile there was no hassle in using the MIS ink. 
> 
> One of the reasons for doing the test is that I upgraded my printer
recently to the 2400 
> and like yourself I'm interested in the K4 inks. The result of our
simple test has given me 
> confidence to try the K4 inks when I have used up my stock of Epson ink.
> 
> Just for interest we also printed the same test print on my 2400
with K3 Epson inks. The 
> 2400 print was the clear winner. The print showed slightly more
detail and saturation but 
> the real difference was that there was no metamerism. It showed
quite clearly why the 
> 2400 is so good at BW compared to the 2100. 
> 
> Hope this helps.
> 
> Regards Peter.
>

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.