Digital BW, The Print

Hello

I've been following the discussion on the topic and wondered how choice of
working space affects the issues?

I use an FS4000 to get 16 bit data to start with. On opening any file with
PS6 I'm faced with several options depending on what spaces I'm using or
want to assign and use. I have been assigning generic grey and then
converting to my default working space of Grey Gamma 2.2  I picked the GG2.2
space because I thought it would convert more accurately to AdobeRGB when it
came to printing, since AdobeRGB is also a 2.2 gamma space.

However I've not been able to come up with good enough reasons to actually
justify these choices to someone else and they feel a bit arbitrary to me.

The only times I've noticed (on the monitor) problems with splotchy shadows
has been after seriously non-linear transformations, which made me wonder
about what effects different working spaces had since conversions between
them are non-linear actions

I would appreciate anyone's comments


bye for now   

Keith Cooper

Keith,

it would be important  _not_  to have to convert when bringing a scan into PS. 
For that to happen, your output profile in your scanning software has to match 
your favorite PS settings. Or, if you have "ideal" workspaces in PS, do it the 
other way around and match your scanner setup to them. 

Getting 16bit data is a good thing if your scanner software is limited and you 
have to accept "raw" scans. Otherwise it's a waste of bandwidth (if you can get 
8bits that you have control over during the scanning process).

Antonis



--- In DigitalBlackandWhiteThePrint@y..., Keith Cooper <yahoogroups@n...> 
wrote:
> Hello
> 
> I've been following the discussion on the topic and wondered how choice of
> working space affects the issues?
> 
> I use an FS4000 to get 16 bit data to start with. On opening any file with
> PS6 I'm faced with several options depending on what spaces I'm using or
> want to assign and use. I have been assigning generic grey and then
> converting to my default working space of Grey Gamma 2.2  I picked the 
GG2.2
> space because I thought it would convert more accurately to AdobeRGB 
when it
> came to printing, since AdobeRGB is also a 2.2 gamma space.
> 
> However I've not been able to come up with good enough reasons to 
actually

> justify these choices to someone else and they feel a bit arbitrary to me.
> 
> The only times I've noticed (on the monitor) problems with splotchy shadows
> has been after seriously non-linear transformations, which made me wonder
> about what effects different working spaces had since conversions between
> them are non-linear actions
> 
> I would appreciate anyone's comments
> 
> 
> bye for now   
> 
> Keith Cooper