Well, when I went off on my trip at the beginning of the week I fully
expected to return and find a string of obscenities in your response and
I am pleased to read that Australia's entry for Usenet Kook of the
Millennium didn't disappoint. You even managed to ignore the answers to
your specific questions while trying to redefine your question, just as
expected. And you have also added some easily proven lies to add to
your discredit.
The person who asked the question, ****wit.
Which you answered long before the current discussion, both Nikon's and
Vuescan - it is not IN question!
Nobody now gives a damn what you use. Nobody is in any way attempting
to make you "make me change from using vuescan". This IS the current
question:
Really? So, which SPECIFIC advice do you
consider I have no knowledge of, ****wit?
To begin with, the first one which Rafe responded to, in your post of
6th July where you stated "I prefer to use vuescan, the monitoring and
fine tuning can be done from a MUCH larger preview and that makes a huge
difference: the very small preview in the Nikon software is almost
useless." And subsequently refined, after Rafe pointed out your error,
with "nope. not in this last version."
And for once,
ANSWER THE ****ING QUESTION!
The question WAS ANSWERED, quite specifically by both Rafe and myself.
There is no restriction to a small preview window in this or ANY
PREVIOUS version of NS.
You then CHANGED YOUR QUESTION, in your reply, with "I don't mean resize
a screen, I mean set the resolution of the preview." Again, both Rafe
and I have answered your question, simply resizing the preview and
pressing the "preview" control initiates a rescan of the image at the
preview size and the screen resolution. The combination of these two,
and the crop area of the image being previewed determine the preview
resolution. They are inter-related, as you clearly know since you
write:
Listen, ****wit: the two are completely and totally
inter-related. If you had READ ALL replies,
you'd have found out that I mentioned vuescan can
set ANY resolution for previews. Something that
sorry-arsed product of yours never did and
STILL can't do!
As previously pointed out to you, it isn't MY product, although you are
clearly incapable of reading that through your red mist.
However, now you want a SPECIFIC resolution. Am irrelevant question
since Vuescan doesn't do that either. Vuescan offers a drop down list
of available scanner resolutions which can be selected for the preview.
That warm feeling you get by selecting the "custom" option and typing in
a SPECIFIC resolution just means you have pissed yourself, because that
is INTERPOLATED from the predefined resolutions native to the scanner.
Quite simply, you can't scan at 1200ppi (YOUR figure!) with a 4000ppi
scanner without interpolating the result, since each 1200ppi output
pixel pitch is 3.333' larger than the native scanner pixel pitch.
Strange that the birdbrain of Oz didn't know that, it might have
prevented you from adding additional LIES in your reply, addressed
below.
No it most definitely does not do that!
Resizing the preview does NOT change
the resolution to the "resolution required" setting,
you miserable ignorant twit.
Yes it does, with EXACTLY the same end result as Vuescan does, although
the method of achieving it is different. You are clearly too hard of
thinking to press the "preview" button!
It MIGHT change it to a new value ONCE
a window size THRESHOLD that is known only to
Nikon is met.
So, now you admit it DOES change resolution. Read back through the
thread and you'll find that I told you so, some time ago. And it isn't
a threshold known only to Nikon, the threshold is pretty obvious to
anyone using the application, but its selection is transparent to the
user.
Until then, it stays at EXACTLY the same
resolution.
No it doesn't. It SCANS at the same resolution, as does Vuescan, and
then interpolates DOWN if necessary to the REQUIRED PREVIEW resolution -
just as VS does! The only time it interpolates UP is if the set preview
window and the scan area result in a scan resolution which exceeds the
native resolution of the scanner - just the same as VS does.
In VS you can determine the OUTPUT resolution of the preview
specifically directly, in NS it is computed automatically based on your
screen resolution, the area of film being previewed and the size of that
preview. In both cases, unless the output is an INTEGER DIVISION of the
native resolution of the scanner, the preview image is interpolated.
The different input methodology relates to the origin of the two
applications, VS beginning as a command line application which didn't
even support a preview window until V3, while NS has operated with a
fully scalable preview window since it was first shipped with Nikon
scanners.
And if you happen to have a monitor
that does not meet that threshold, you're stuck up
the proverbial with enlarged jagged low res images
which, as I said, are NEXT TO USELESS.
The only occasion where NS results in an enlarged low res preview image
is when the user is too intellectually challenged to press the "Preview"
button! Changing the image size, or the crop size, or the screen
resolution ALL change the input parameters for the preview display,
which is ALWAYS made at a native scanner resolution HIGHER than the
screen resolution for the previewed image where possible.
Compare that to a specific entry in vuescan that will
set a preview to ANY resolution the scanner supports,
REGARDLESS of the size of window you have for
that preview!
So? It is simply a DIFFERENT input method - the end result is exactly
the same!
Damn, you can even set it to the final
scan rez, if you so wish! Although only someone as
stupid as you would do that, of course.
Only someone as stupid as you would suggest that, since there are many
occasions where a preview at the full resolution is required, although
the limitations of VS in this respect may have prevented you from ever
considering it as desirable!
A heavy cropped area for example, NEEDS to be scanned at the full
resolution of the scanner to preview that area as large as desired. NS
scans ONLY the selected preview area at the full resolution, hence
reducing the time of the preview. VS would scan the entire image area
at full resolution.
You can then scroll within that window to see any
portion that doesn't fit in your screen.
Now, which product produces the goods when it comes
to resolution and size of previews?
NS does - in fact, it does exactly what you think you are getting from
VS!
Don't bother: you've shown already to be too stupid and
biased to even understand the question, let alone produce
an answer.
Au contraire, I have answered each and every question you have asked and
most variations of them you have postulated.
NS is NOT limited to a small preview window, as you claimed.
NS does NOT enlarge the old preview to obtain a new preview resolution,
as you claimed.
VS does NOT permit ANY SPECIFIC preview scan resolution to be
implemented, as you claimed.
These ARE the real facts, whether you understand them or not!
