Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] Re: Cooled C6 on matte and warmed HP PK C6 on glossy (with DMax 2.86)

2010-02-11 by Michael King

So I've lost track of this thread a little, but just to be clear on HPPK
dmax -
on Glossy HPPK dmax is spectacular with 5% Glop overcoat I get below L*=2 on
Epson Trad and IGFS.
BUT if you increase Glop much over 5%, dmax starts to reduce dramatically
and ultimately you can see a white haze on the shadows.

Also Joost MIS PK as you know is warm, HPPK is neutralish. They are very
different beasts.
You could cool down MIS PK with Cyan but that Cyan would be you achilles
heel in terms of fading.

Mike


On matte HPPK is about 50% density of Eboni.

Mike

On 11 February 2010 10:57, horstenj <j.h.j.h@...> wrote:

>
>
>
>
> --- In DigitalBlackandWhiteThePrint@yahoogroups.com<DigitalBlackandWhiteThePrint%40yahoogroups.com>,
> "santonov2you" <drumscanner@...> wrote:
>
> > From the other side, I think that UT7 C adds a lot to this DMax that I am
> getting, my printer produces lousy DMax with undiluted HKPK.
>
> The open, but highly relevant, question for me is if the lousy Dmax comes
> from the microbanding you mentioned or that this happens because the HP PK
> is just not designed for use in an Epson. Does anyone else have experience?
>
> Actually, originally I was considering to use MIS PK iso undiluted HP PK
> for cost reasons: I still have MIS PK in stock and in the HP 70 cartridges
> HP PK was more expensive. I dropped that idea as in HP 91 cartridges HP PK
> is much cheaper. But your experience could bring that idea back on the
> table.
>
> I only just subcribed to the Aardenburg database, so have not yet had to
> opportunity to delve in the data: Is MIS PK worse than HP PK in terms of
> longevity?
>
> Joost
>
>  
>


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