Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] Re: Piezotone clipping?

2002-08-08 by Martin Wesley

----- Original Message -----
From: "Mitch Alland" <malland@...>
To: <DigitalBlackandWhiteThePrint@yahoogroups.com>
Sent: Wednesday, August 07, 2002 5:02 PM
Subject: [Digital BW] Re: Piezotone clipping?


> For: Martin Wesley" <mwesley250@...>
>
> >In response to Michael's post, there are now 6 ink set available for the
> >Piezo driver. My experience is that they all do not match up exactly the
> >same way even with the same driver...The difference is enough though that
a file
> >optimized with one ink set may need some tweaking if you switch
> >to another ink set.
>
> This seems to indicate that new profiles are called for. Or, in creating a
new file, is it sufficient to adjust the dot gain curves to improve the
preview?
>
Mitch,

That would probably be the best approach. Do a custom dot gain curve for
each ink and paper combination. Since ConeTech is going to offer three
different ink hues I suspect that not all profiles are going to be equal
with each ink set. Ideally ConeTech would have separate profiles for each
ink/paper combination but I don't know what their plans might be in this
regard. Hopefully we will see a Piezo upgrade in the not too distant future.

I feel that the profiles are quite usable with the PiezoTones as they are
with range with the papers I have tried. LPM, EAM, Photo Rag, Museo, German
Etching and William Turner. I am doing work prints on EAM and final prints
on Photo Rag at the moment. In the darkroom it is always a tricky (or
impossible) job to go back and make another print to match an earlier print
using a new batch of paper. Changes in sensitivity and contrast are just a
way of life. In comparison, the differences I am seeing with the inks seem
pretty mild.

Martin Wesley

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.