Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] When is DMax not Dmax?

2012-11-18 by Paul

Thanks to both of you, Ernest and Eric,

Eric, what you say makes perfect sense, Dmax is Dmax. Let me amplify my question a bit more:

I'm interested in shadow detail of my final print, that is, in the print I want Dmax in some of the shadow but some detail in parts of the shadow. This would correspond to lighter areas of the negative, right? But scanner specs don't show that, they show Dmax in the negative. Like you say, Dmax is Dmax. And so the scanner specs give me information on how my highlights might look like in the print - and of course I'd like some detail there too, I don't want them blown out. But it looks like typical scanner specs can't help me with detail in the print's shadow areas.

I think I've got a handle on this. I suppose if I'm interested in detail in the thin AND dense parts of the negative I could deal with this in my scanner software. Am presently on a learning curve with VueScan.

Thanks again,

Paul


--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "E.Neilsen" <e.neilsen2@...> wrote:
>
> Paul. The Dmax is Dmax.; the maximum density of dark (densest) area.  It
> does not matter whether it is a positive or negative, the real material has
> an area that is the darkest. Whether it prints as a positive or a negative
> is up to the user later.  The scanner doesn't know and the software doesn't
> know until you tell it.  But Range is an important aspect. However, with
> multiple scanning being possible it does still have relevance.  If your
> scanner can't see it, it doesn't exist. = areas with no detail. 
>  
> Eric Neilsen
> Eric Neilsen Photography
> 4101 Commerce Street, Suite 9
> Dallas, TX 75226
>  
> www.ericneilsenphotography.com
> skype me with ejprinter
> Let's Talk Photography

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.