That is just a rather convoluted and insincere way of agreeing that
Vuescan does give pretty good scans straight out of the box without user
fiddling and adjustment.
No, it's not. It's a proof that *any* scanning software (I'm aware of)
can achieve comparable results (certainly beyond any difference such a
casual user can spot) when using the above, simple procedure, thereby
eliminating the key "feature" or advantage of point-and-shoot software
(ease of use).
It's just as easy to set a gray point in NikonScan as it is in
VueScan. Much easier, actually, because in NikonScan it's right there
in front of the user, unlike the "secret VueScan handshake" (right
click).
Actually that is not the case. For a significant number of users there
seems to be great problems getting anything that is acceptable from
Nikonscan without a deal of faffing around, even just to get a raw scan
that they have no skill to be able top process in Photoshop to achieve
as good a result as Vuescan and Silverfast get straight out of the box.
Not if one follows the same procedure in NikonScan: click on the gray
color sampler, click on a neutral area on the Preview, hit scan. That
gets comparable results to the same procedure in VueScan, for example.
Ooh handbags at dawn, Don - bitch, bitch. ;-)
But I thought you agreed? ;-)
I had my handbag on the ready, hoping for a Monty Python style
recreation of the battle of Hastings (I think it was...) by that
Woman's Auxiliary Club or whatever... (how's that for vague?).
As a Python connoisseur I'm sure you know the skit I'm referring to
and will be able to fill in the blanks...
And that is exactly the point - for many users that point-and-shoot
option *is* the best they can get because they don't need to understand
and implement the processes to get anything as good, let alone better,
themselves.
Right, in relative terms, but not in absolute terms. And, as I
outlined above, if that's all they want to do (sacrifice quality for
convenience) they can do that with any scanning software I'm aware of.
I don't disagree, but your response was inaccurate too. There are cases
when scanner adjustment is necessary to get an improved raw scan.
You know that... I know that... Most people in this newsgroup know
that... But he doesn't seem to know even the most elementary basics.
If we start telling him that auto-exposure is not always 100% accurate
and that he needs to adjust Analog Gain, his head will explode...
So, baby steps... First, let him get to grips with the most elementary
basics.
Besides, we also have to consider order of magnitude here. The
difference between Auto-Exposure and Analog Gain fine tuning is far,
far less than the difference (massive corruption, actually) he will do
messing around with curves in scanner software. This nuance is bound
to get lost on someone who thinks that when you scan raw you "lose a
lot of quality". Not just "lose quality" mind, but "lose a *lot* of
quality"!
You
also assume that the processing abilities of Photoshop are some sort of
pinnacle every other package should aspire to.
No, this is not about Photoshop but about the fact that when using
scanner tools one is working off of a tiny Preview. Neither Photoshop
nor any other image editing software could do substantially better
when forced to work through such a "keyhole". With scanner software's
very limited tool chest, one is also missing a substantial number of
essential tools, such as numerical displays (mean, median) etc.
Your remark is just as open to criticism as his was - though
you prefer not to see it that way.
Indeed it is. But you are now talking about fine shades and nuances
which you and I agree on, but are way over his head, and will only
confuse him.
For many, user friendliness *IS* superior output, and whether that comes
from the hardware or software is irrelvant, we all judge on the end
result. Whilst it is perfectly true that in skilled hands your workflow
will result in a superior end product, that is not the case for the
unskilled.
And we are not going to help them by giving them the impression that
the *relative* improvement they experience (comparing their results
with and without point-and-shoot) compares even close in *absolute*
terms with the results of someone who knows what they're doing.
Just to get completely off topic, its a fair bet that as an American you
drive a car with an automatic transmission - why?
Let me stop you right there... Two wrong assumptions:
1. I'm not an American, I'm Canadian, eh? ;-)
2. I don't even have a driver's license. I ride a (push) bike! Yes, in
the snow too... We Canadians are a hardy bunch! ;-)
Now, you were saying... ;-)
But seriously, I get your gist but I don't think this particular
example really addresses the point. You will still cover the mileage
either way. An automatic may be more convenient but the *absolute*
"quality" (in this case actually quantity) of mileage is still the
same whether you drive an automatic or not.
When someone uses point-and-shoot in our context they do get the same
convenience as the driver using automatic but - unlike driving - they
don't cover the same mileage or, in our context, get the same quality
as someone who knows what they're doing.
Toby was wrong in his claims, but you were also wrong in your claim that
best was exactly the opposite of the process he claimed to be best, as
well as assuming that your workflow is not without its limitations
itself.
The problem with that is that you are putting my workflow through much
more scrutiny which you are not applying to his "workflow".
Yes, I may need to fine tune using Analog Gain, but so may he,
although he's not even aware of it! Indeed, the likelihood that he
will need (major) fine tuning is much higher!
Nevertheless, I'm giving him the benefit of the doubt and, since we
have this potential need for fine tuning on both sides of the equation
we can strike it from both sides of the equation, and that's what I
did.
After that - when we remove this fine tuning requirement - what we are
then left with is that his statement is exactly the opposite of truth.
But he is not talking about "getting the most out of the hardware", he
is talking about getting the best result from the *combination* of
hardware, software and the skill available to bring the two together to
achieve the optimum result.
Yes, he is talking about getting the most out of hardware (by
referring to raw) even if he doesn't know it. And that's exactly my
point! We have to make it clear to him what the implications of such a
statement are - and do that on the very basic, elementary level -
before we even have a hope of teaching him the rest. Assuming he even
wants to learn...
Judging by his absence, his head probably already exploded as we argue
how many angels can dance on the head of a pin... ;-)
Its also a very different one from the global setting that the later
scanners use to achieve a much more tightly controlled result, which is
why Nikon would not even begin to try to help you. In particular, that
blue LED your LS-50 is a significant improvement over the one in the
LS30. In short, the hardware wasn't up to the job you wanted to the
software to achieve.
That's not really correct. I have to preface, though, by saying I
don't have the time to test this to my satisfaction. One day...
But at least on the surface (comparing histograms) "LD-50" ;-)
Kodachrome setting does not produce significantly different results
(regarding Kodachrome compensation, of course) from the LS-30 once I
apply the Kodachrome correction I came up with empirically. Actually
they are surprisingly close! I say "surprisingly" because I didn't use
*any* tools, not even an IT8 target with the LS-30, but presumably my
sample was large enough to get a good enough approximation.
The only difference I see is actually in the *red* channel. It appears
that the red dynamic range of the LS-50 seems somewhat wider than that
of the LS-30 after I apply the correction. However, I am comparing a
2700 scan with a 4000 scan, plus, LS-50 is 14-bit so all that combined
may account for the difference in the red channel histogram width.
But, like I said back then, it's not so much the abundance of blue
(which is what everybody notices first, me included) but the absence
of red which seems to be the main problem! On reflection, that makes
perfect sense! One can always compress "too much" dynamic range (as in
blue) but you can't conjure missing dynamic range (as in red) so it
reasons that the absence of red would be much more detrimental.
Don.