D
Don
Well, it could be that you are assuming things - like "the language
barrier" that doesn't exist. Although I have a European name, I grew
up from infancy in a English speaking country, and English is the only
language I know.
Fair enough. Point taken.
However - with that in mind - your statement was, then, very inexact
implying that a subjective feeling was objective fact ("I get better
quality").
I attributed that inexactness to the "language barrier" but if it
doesn't exists, then...
You also seem to assume that I'm settling for "quick
and dirty" results. As my end result of most of my scans is an A3
sized print, I'm very critical of any flaw in the images produced.
....you have to define "better quality". What does that mean in this
context? Just saying that you like it better is not an objective fact,
it's a subjective feeling.
The tests wouldn't be valid if I wasn't.
I think there still may be a misunderstanding...
*Any* setting you use in VueScan outside of a raw scan *is* image
editing!
And even if you scan raw there is still an obscure VueScan "condition"
where some of the other settings will still be applied i.e., it's not
a raw scan. Even the author himself was unaware of this until it was
pointed out to him by a user, after which the author acknowledged it.
So, instead of going through all permutations, that's why I ask what
kind of *specific* testing you have done. In other words, we need the
facts before we can objectively evaluate both your testing methodology
and your results.
So your facts are messages from other posters? Out of curiosity, have
you done any empirical testing yourself? For each of the bugs or
faults reported by testers?
When, for example, a number of people keep reporting the same bug over
an extended period of time, I think it's safe to say it's a bug (e.g.
Minolta streaking).
When, for example, someone reports a problem and other VueScan users
reply that it's a known problem which has been around for a while, I
think it's safe to say it's a bug (e.g. Preview different from scan).
Etc... etc...
And, yes, I have tested VueScan extensively about 18 months ago. So, I
do have first hand knowledge as well. Some of my findings were
arrogantly dismissed by the author with "you don't need that", others
totally ignored.
He then publicly challenged me ("in order to get to the bottom of it")
to provide examples - which I have, uploading images for over a week.
After all that (when his challenge backfired and having painted
himself in a corner) he got abusive and refused to provide the setting
he claimed would solve the problem.
Another thing you may not know... Are you aware that early versions of
VueScan didn't even have a Preview window? When people asked for it,
the author's condescending response was - I think you can guess by now
- "you don't need that"... :-/
Saying "there have been reported problems in many aspects of the
software" and saying "it is bug-ridden and unreliable" have very
different contextual meanings in the strength of the negativity
communicated and the attitude of the writer, particularly in a medium
where non-verbal nuances are absent. If you don't want "such
inaccurate and subjective misinterpretation" of your comments, then I'd
suggest you think carefully about how you phrase what you say, and your
objectivity may be more obvious.
It's a two way street... If the reader is predicated to mistrust the
writer then, regardless of what the writer says, they will immediately
assume the worst. And that's exactly what the very few, but
"vociferous", VueScan users here do. If they only read the messages
calmly, and then objectively checked the facts, they would realize
that everything contained within is factual.
Instead, they even totally ignore the fact that I may recommend
VueScan to users who are after a quick-and-dirty scan, even going as
far as to provide the link! And that's in spite of all the abuse and a
torrent of obscenities from the author. I wonder, how many of them
would do the same in similar circumstances?
So, even though it may not sound palatable to them, saying that
VueScan is bug-ridden and unreliable is factually and demonstrably
correct.
Don.