Yahoo Groups archive

Digital BW, The Print

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

Thread

2400 MK v. PK chips

2400 MK v. PK chips

2006-05-25 by Paul Roark

I find the having the full paper type list available even when Eboni (or
other MK) is installed is helpful.  As such, I currently have a Photo black
chip on my Eboni 2400 cart.  Has anyone found any reason why this is not a
good idea?  From what I can tell the EEM and other profiles work the same.

 

This same issue would apply to all k3 printers.  The expanded paper type
list appears to be useful.

 

Additionally, do newer 2400 printers show the "Ultra Premium Glossy Paper"
media type?  It's not on my 2400 list.

 

Paul

www.PaulRoark.com <http://www.paulroark.com/>  

 



[Non-text portions of this message have been removed]

Re: 2400 MK v. PK chips

2006-05-28 by koloshor

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Paul Roark"
<paul.roark@...> wrote:
>
> I find the having the full paper type list available even when Eboni (or
> other MK) is installed is helpful.  As such, I currently have a
Photo black
> chip on my Eboni 2400 cart.  Has anyone found any reason why this is
not a
> good idea?  From what I can tell the EEM and other profiles work the
same.

Check more carefully. They didn't on the 2200. The Matte Black
profiles should be quite different. The driver tables for "ICM" and
"no profile" are quite different for MK and PK. MK has more "hook" ( a
faster rise to high ink loads at high densities) in the dark colors,
as well as a different black generation strategy (goes to color inks
at a lower density)

FWIW, I'm getting closer to cracking the Epson driver curve tables ;)

> This same issue would apply to all k3 printers.  The expanded paper type
> list appears to be useful.

I agree. As well as the ability to go to borderless printing when
using matte inks, which is forbidden if the printer actually thinks
you have matte inks installed.

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.