N
nikita
Viken,
good work!!
The green tint can very much be something you're seeing from a
slightly off greyballance in the separate channeladjustments in Adobe
Gamma. Doing this adjustments a few times after each other will reveal
to you that it's impossible to get it back to the same spot each time
by eyeballing. That's why wer're going for instrumented calibration.
Even if scannerRGB seems OK it could look bad when on a correct
monitorcalibration, if the one you made is slightly off. We're dealing
with noncontrollble variables here....so anything is possible.
The greenish tint can also be that the "scannerprofile" which is used
for the conversion within the scannersoftware on the fly from
Scannerprofile to AdobeRGB would be a little off for your scanner as
it is a generic one. As you said, try to make a conversion in the
imageeditingprogram from the scannerprofile to Adobe RGB and then
compare with the rest. Does that also create a similar green tint?
Then you know that the conversion in the scannersoftware is doing a
good job. If differences, try different renderings in Photoshop and
see if you can replicate the green tint even in Photoshop, see below.
The most straight forward way is of course to scan directly into Adobe
RGB from the scannerdriver. These offs you see can be a diff in the
profile as I said and then the flow is good in itself. If any profile,
source or destination, is not accurate the offs should be fixed with a
better profile if possible.
The fact that the pure ScannerRGB into the Imageeditingprogram lacks a
little punch and that might be because off a larger scannerspace is
put right into the smaller Adobe RGB without a conversion into it. The
same effect as putting an Adobe RGB into the web. Try more
testpictures and see if it looks good allover in any scan.
When you're talking about if it would be better using the Scannerspace
I don't know if you mean editing in it and keep the pictures in it.
No, the scannerspace is not greyballanced and is not perceptual
uniform and will give diffrent effects depending on what is edited in
the space. Always convert to a Workingspace before editing. Thats a
general rule within colormanagment.
The skintones may be calmer without that high saturation when using
scannerRGB.
But that is very easy to fix with Hue/saturation if Adobe RGB feels
better allover. Go for the redchannel and reduce saturation and
perhaps move reds towards yellow slightly. Of course that depends on
what you have kick with from the beginning.
If the green tint is the only "bad" sideffect from using Adobe RGB
from the Scannersoftware I would try to find a simple correction with
the tools in the scannersoftware and save a "preset" if possible.
always load that prsete and the tuning is there. With an
profileeditingprogram it would be simple to hammer that into a new
profile too. Go for the allover feeling and find a way that needs as
simple adjustment as possible. Getting everything spot on with a
straight scan takes a customprofile. It would cost the price of an IT8
and downloading the free Little CMS profiler. But I think you can find
a tuning within the scannerprogram that will give you what you want.
We have to live with adjustments when not using customprofiles. Even
Vuescan needs adjustments, belive it or not.
Do you see any diffrences between Photoshop and paintshop regarding
these tests? If you chose to convert from Scannerprofile to Adobe RGB
in Photoshop by using the Image>mode>Convert to profile, try both
Relative Colormetric and Perceptual rendering and see what happens.
Sometimes a general workflow with correct profileset up is easier to
get back to when changing scanners or flow later on, than depending on
homemade "on/off CMS" here and there. Even if it takes some easy made
tweakings it may pay off in the long run. It's extremely frustating
when trying to get back to a homemade flow with new tools that refuses
to behave like the old stuff.....simply chaos and no fixed references
to lean back on.
Again, damn good work Viken. Be happy that your offs are so small
without a customprofile. You'll get there.
nikita
PS
remeber the difference between ASSIGNING and CONVERTING. You're not
converting just because you switch cms on/off with Adobe RGB or s-RGB.
That would be ASSIGNING. That just change the view in an
colormanagment aware application like Photoshop. You have to CONVERT
from a SOURCEprofile to a DESTINATIONprofile. Then the colors will
change in both CMS aware apps and nonaware apps like a web browser.
good work!!
The green tint can very much be something you're seeing from a
slightly off greyballance in the separate channeladjustments in Adobe
Gamma. Doing this adjustments a few times after each other will reveal
to you that it's impossible to get it back to the same spot each time
by eyeballing. That's why wer're going for instrumented calibration.
Even if scannerRGB seems OK it could look bad when on a correct
monitorcalibration, if the one you made is slightly off. We're dealing
with noncontrollble variables here....so anything is possible.
The greenish tint can also be that the "scannerprofile" which is used
for the conversion within the scannersoftware on the fly from
Scannerprofile to AdobeRGB would be a little off for your scanner as
it is a generic one. As you said, try to make a conversion in the
imageeditingprogram from the scannerprofile to Adobe RGB and then
compare with the rest. Does that also create a similar green tint?
Then you know that the conversion in the scannersoftware is doing a
good job. If differences, try different renderings in Photoshop and
see if you can replicate the green tint even in Photoshop, see below.
The most straight forward way is of course to scan directly into Adobe
RGB from the scannerdriver. These offs you see can be a diff in the
profile as I said and then the flow is good in itself. If any profile,
source or destination, is not accurate the offs should be fixed with a
better profile if possible.
The fact that the pure ScannerRGB into the Imageeditingprogram lacks a
little punch and that might be because off a larger scannerspace is
put right into the smaller Adobe RGB without a conversion into it. The
same effect as putting an Adobe RGB into the web. Try more
testpictures and see if it looks good allover in any scan.
When you're talking about if it would be better using the Scannerspace
I don't know if you mean editing in it and keep the pictures in it.
No, the scannerspace is not greyballanced and is not perceptual
uniform and will give diffrent effects depending on what is edited in
the space. Always convert to a Workingspace before editing. Thats a
general rule within colormanagment.
The skintones may be calmer without that high saturation when using
scannerRGB.
But that is very easy to fix with Hue/saturation if Adobe RGB feels
better allover. Go for the redchannel and reduce saturation and
perhaps move reds towards yellow slightly. Of course that depends on
what you have kick with from the beginning.
If the green tint is the only "bad" sideffect from using Adobe RGB
from the Scannersoftware I would try to find a simple correction with
the tools in the scannersoftware and save a "preset" if possible.
always load that prsete and the tuning is there. With an
profileeditingprogram it would be simple to hammer that into a new
profile too. Go for the allover feeling and find a way that needs as
simple adjustment as possible. Getting everything spot on with a
straight scan takes a customprofile. It would cost the price of an IT8
and downloading the free Little CMS profiler. But I think you can find
a tuning within the scannerprogram that will give you what you want.
We have to live with adjustments when not using customprofiles. Even
Vuescan needs adjustments, belive it or not.
Do you see any diffrences between Photoshop and paintshop regarding
these tests? If you chose to convert from Scannerprofile to Adobe RGB
in Photoshop by using the Image>mode>Convert to profile, try both
Relative Colormetric and Perceptual rendering and see what happens.
Sometimes a general workflow with correct profileset up is easier to
get back to when changing scanners or flow later on, than depending on
homemade "on/off CMS" here and there. Even if it takes some easy made
tweakings it may pay off in the long run. It's extremely frustating
when trying to get back to a homemade flow with new tools that refuses
to behave like the old stuff.....simply chaos and no fixed references
to lean back on.
Again, damn good work Viken. Be happy that your offs are so small
without a customprofile. You'll get there.
nikita
PS
remeber the difference between ASSIGNING and CONVERTING. You're not
converting just because you switch cms on/off with Adobe RGB or s-RGB.
That would be ASSIGNING. That just change the view in an
colormanagment aware application like Photoshop. You have to CONVERT
from a SOURCEprofile to a DESTINATIONprofile. Then the colors will
change in both CMS aware apps and nonaware apps like a web browser.