the speed of a Nikon Coolscan 500 ED

  • Thread starter Thread starter Sam Carleton
  • Start date Start date
SNIP
I recently contacted Nikon Tech (via email) about "Analog Gain" and asked
if the scanner varied the exposure time and/or the light intensity. They
responded back that the Nikon LS-40 scanner varies the intensity of the
LED's. I tried to verify this with my scanner by timing scans with no gain
and with max gain; the scan times were the same. I would guess that the
newer Nikon scanners behave similarly.

Since I don't have access to such a scanner (I do have an older LS2000 which
varies time, just like my other 2 scanners), I'll take your word for it, but
I am also sceptical about it. LEDs change spectral output at different
in/output levels. That would not only change color characteristics, but
probably also change lifespan. Maybe others can verify, maybe on that
scanner model it changes the amplification in the ADC, possibly a first in
industry (not good for quality), so unlikely.

Bart
 
Jean <[email protected]> said:
I recently contacted Nikon Tech (via email) about "Analog Gain" and asked
if the scanner varied the exposure time and/or the light intensity. They
responded back that the Nikon LS-40 scanner varies the intensity of the
LED's.

They lied - whether through ignorance or deception cannot be
ascertained, but they lied!
I tried to verify this with my scanner by timing scans with no gain
and with max gain; the scan times were the same.

Is the LS40 bus limited in any case? Try it again with the full range
of gain (as below).
I would guess that the
newer Nikon scanners behave similarly.

Then you would guess wrong! ;-)

The following times were measured using a Nikon LS-4000 (half the speed
of the device that is the subject of this thread) with IEEE-1394
interface, 14bpc, ICE, autoexposure and post processing all off, using a
3.2GHz P4 with 1GB of RAM:
Gain Settings
Master RGB(all same) Total Gain (EV) Time
+2 +2 +4 159.2sec
+2 +1 +3 87.5sec
+1 +2 +3 87.6sec
+2 0 +2 52.1sec
+1 +1 +2 52.0sec
0 +2 +2 52.1sec
+2 -1 +1 36.6sec
+1 0 +1 36.8sec
0 +1 +1 36.8sec
0 0 0 34.8sec
-1 0 -1 34.5sec
0 -1 -1 34.5sec
-2 0 -2 34.3sec
-1 -1 -2 34.3sec
0 -2 -2 34.3sec
-2 -1 -3 34.3sec
-1 -2 -3 34.3sec
-2 -2 -3 34.3sec

All timed using the same crop from the same slide (not moved in the
scanner).

It is clear from this that the time to traverse the slide, reading the
CCD out three times at each position, is approximately 34.3sec and this
can only be reduced by changing the crop. Increasing the "analogue
gain" however, definitely does increase the exposure time - as expected.
It is exceedingly difficult and costly to design a control circuit for
an LED which adjusts the luminance linearly, as is required to be a
precise function of the user controls provided in Nikonscan. Further,
as Bart mentions, changing the drive characteristics of the LED in order
to implement such a brightness change also changes the emission
wavelength and thus the colour balance. I cannot believe that Nikon
implemented a far more complex system in the lower cost LS-40 whilst
retaining the tried and tested method of exposure control in the
LS-4000.

So, whoever you got that piece of information from at Nikon was simply
selling pork pies to quickly get the monkey off their back, improve
their resolved problem rate and move onto the next mug that had
submitted a non-critical query that could simply be lied out of, leaving
you none the wiser. ;-)
 
|
| | SNIP
| > I recently contacted Nikon Tech (via email) about "Analog Gain" and
asked
| > if the scanner varied the exposure time and/or the light intensity.
They
| > responded back that the Nikon LS-40 scanner varies the intensity of the
| > LED's. I tried to verify this with my scanner by timing scans with no
gain
| > and with max gain; the scan times were the same. I would guess that the
| > newer Nikon scanners behave similarly.
|
| Since I don't have access to such a scanner (I do have an older LS2000
which
| varies time, just like my other 2 scanners), I'll take your word for it,
but
| I am also sceptical about it. LEDs change spectral output at different
| in/output levels. That would not only change color characteristics, but
| probably also change lifespan. Maybe others can verify, maybe on that
| scanner model it changes the amplification in the ADC, possibly a first
in
| industry (not good for quality), so unlikely.
|
| Bart
|

I was/am skeptical also, since there is a blurb on the Nikon site saying
that the LS2000 varies exposure time for "analog gain". But the Nikon guy
who responded to my request for info was very definite about it. Maybe the
ability to increase LED intensity explains the fact that the LS40 onward
have no problem with dense Kodachrome slides...

Jean
 
Don said:
Kennedy was of the same opinion (that stepper motor activity is an
indication of bus load) until I ran a few tests. Here's my original
reply:

-- cut start ---



I don't think you can rely on this method. What if the scanner itself
can't keep up and "stops and thinks" before sending data? For example:

When I run a scan without ICE the stepper motor purrs along
uninterrupted. However, when I do turn ICE on, there are numerous and
long stops.

Even allowing for the scanner to send the IR channel data (which I
don't think is the case) the time it takes to complete an ICE scan
(about 3 mins) is not commensurate with non-ICE scan time (about 1
min). That's an increase of 300% for, nominally, 33% more data.
Therefore, it's the scanner itself that "stops and thinks" before
sending data or, the scanner software on the PC side tells it to cease
until the software digests the data it has already received.
And at the time I did point out that the assumption you make is somewhat
unlikely given the alternative issues, however....

....what is this super intelligent, scanner that "thinks", let alone
knows enough to stop other tasks before it does so? It's clearly male,
since it can only do one thing at a time and thinking takes priority -
good job they don't breed! ;-)

Whilst I agree that the listening test is not a definitive test of bus
saturation, it is a test that something has become a bottleneck in the
system and, assuming adequate processor power and memory, the bus is the
obvious candidate. In the case of USB1.1, it is a pretty poor processor
that cannot keep pace with the bus.

You are assuming that the bottleneck is the processing ability of the
scanner, a rather dumb piece of hardware which operates automatically,
consistently and synchronously, albeit under software control. It is
much more likely that the saturation that your test highlighted is
actually saturation of the computer CPU which functions sequentially
rather than synchronously. Consequently the increased processing load
of ICE reduces the ability of the CPU to process the data and thus clear
the USB input buffer, rather than the scanner stopping to do something
it is incapable of.

Next you'll be telling us that your washing machine solved Einstein's
Grand Theory of Unification before entering its high speed spin cycle.
;-)
 
Is the LS40 bus limited in any case? Try it again with the full range
of gain (as below).

The LS40 is supposed to have a USB interface. At about 1MByte/s a
8-bit/ch scan (with ICE) should take about 45 seconds. It is possible
that a change in exposure time cannot be detected this way.

I think that LS40 has a 12-bit A/D converter. Maybe boosting the gain
works on an LS40. If the sensor technology is good enough for 14-bits
in the LS-4000 (and the cells might be bigger due to the lower resolution),
it is possible that the analog noise is far below the LSB noise of the
A/D converter.
 
SNIP
I was/am skeptical also, since there is a blurb on the Nikon site saying
that the LS2000 varies exposure time for "analog gain". But the Nikon guy
who responded to my request for info was very definite about it.

I am also a bit sceptical about most first-line helpdesk people ;-)
Maybe the ability to increase LED intensity explains the fact that
the LS40 onward have no problem with dense Kodachrome slides...

AFAIK the LS-40 is the smaller brother of the LS-4000. The latter scanner
also uses time for 'analog gain', if I'm not mistaken. I'll have to
double-check with a friend's LS-4000, I guess.
The LS-50 and 5000 are newer models, but AFAIK they use a (slightly)
different color LEDs, them being less critical with the Kodachrome dye-set.
The future will tell.

Bart
 
Just turn on the Task Manager if you are running XP or 2000.
It clearly shows the CPU time. With ICE turned on there are two scans
and on my machine it takes twice as long.

Also, The CPU is running 100%! That in and by itself eliminates all
other points as bottlenecks on this particular system which at 100% is
"CPU bound". This means the scanner and USB buss are getting the data
to the processor as fast, or faster than it can handle.

It is also safe to assume that running a 2.8 GHz processor equivalent
that slower machines are going to be CPU bound as well "Unless they
have insufficient memory and/or a slower data transfer (USB-1).

Unless you are running a slow machine a scan and ICE "with no other
functions turned on". should take *about* 40 seconds, or twice as
long as a scan only. "In general" I have not found it necessary to
even turn on the post processing functions. They work well for faded,
off color, and overly dense, or thin slides or negatives, but have not
otherwise been necessary..

Turning on "post processing" can *easily* take the time per image from
40 seconds to 3 minutes. Don't even turn on "post processing". I've
found that it takes extra time even if ROC DEE and GEM are set to 0.
And at the time I did point out that the assumption you make is somewhat
unlikely given the alternative issues, however....

I think some important information is missing here.

I may be making some improper conclusions, but in my system I do not
see this sort of numbers.
It "sounds to me" like there is a good deal of page file swapping
going on. At least that is the way mine acted prior to adding more
memory.

I can now run multiple applications, but it is very easy even with one
meg of RAM to end up with page file swapping when using one or several
of those apps when the scanner is running. Once the page file
swapping starts, you have to wait until the system has cleaned up all
the files involved or it will just continue swapping even if you are
not using the other apps. This sometimes can take 5 to 10 minutes on
my system.
...what is this super intelligent, scanner that "thinks", let alone
knows enough to stop other tasks before it does so? It's clearly male,
since it can only do one thing at a time and thinking takes priority -
good job they don't breed! ;-)

The scanner does very little thinking. It only does what the soft
ware tells it to do with a couple of simple exceptions. Although... I
do have to admit that mine sometimes forgets what it was doing which
usually hangs the whole system. Actually I think it and the software
forget to talk to each other when that happens.
Whilst I agree that the listening test is not a definitive test of bus
saturation, it is a test that something has become a bottleneck in the
system and, assuming adequate processor power and memory, the bus is the

Considering the processor power I have available and my system is CPU
bound I don't think it is a safe assumption. The data still gets
transferred even if the CPU can't keep up. You can see that in the
memory use.
obvious candidate. In the case of USB1.1, it is a pretty poor processor
that cannot keep pace with the bus.

It depends on what the processor is doing with the data. For simple
transfers I'd agree. For linear processing as well even though the
processor has some overhead involved with the data transfer, but if it
were doing something like Fourier transforms (which I certainly hope
it's not) then a simple serial buss would have no trouble keeping up.

In my case I'm feeding the CPU bound processor via USB-2.
You are assuming that the bottleneck is the processing ability of the
scanner, a rather dumb piece of hardware which operates automatically,
consistently and synchronously, albeit under software control. It is

The scanner is rated at 20 seconds for a straight scan and a bit over
40 seconds for a scan with ICE. I would think that anything beyond
that would have to lie elsewhere such as processor, external data
transfer buss, Front Side Buss (FSB), Memory (quantity and speed
including CAS setting)

much more likely that the saturation that your test highlighted is
actually saturation of the computer CPU which functions sequentially
rather than synchronously.
Yup!

Consequently the increased processing load
of ICE reduces the ability of the CPU to process the data and thus clear

Which is not a problem except for insufficient memory available.
It appears to add very little in the way of processing as the scan
takes 20 seconds as does the IR pre scan and the overall processing
takes about 40 seconds.
the USB input buffer, rather than the scanner stopping to do something
it is incapable of.

But ICE should not add that much of a load. (In mine it adds 20
seconds) The scan takes the same time as a regular scan, but the data
is simpler. It is my understanding that it is a complete monochrome
scan in the IR region.
"My guess" is that the software sets the background to 0 and then
figures the value of the imperfections based on that. During the
processing of the scanned image the two are basically fitted together
and the data from the IR scan is algebraically added to the final scan
which in effect cancels out the data from any defects that show up in
the IR scan. This too is done with the CPU and not in the scanner.

BTW, I just ran all the analog gains up to max (2) and re scanned 4
negatives. The time including ICE was just under 1 minute each.
Adding the gain added just under 20 seconds average to each scan.
Thing is I can't tell if that time is in the processing, or from the
scanner. I haven't timed how long the stepper motor has been
running.I could turn on "post processing" and do it again, but I'd guarantee
the times will be 2 to 3 minutes with the analog gains set to normal
(0) This is with no page file swapping. With half a gig of RAM it
seems to take forever and the drive light is on constantly.
Next you'll be telling us that your washing machine solved Einstein's
Grand Theory of Unification before entering its high speed spin cycle.
;-)

I'll take one of those to replace my computer. Then it can do the
work while it's doing the wash. <:-))

Roger Halstead (K8RI & ARRL life member)
(N833R, S# CD-2 Worlds oldest Debonair)
www.rogerhalstead.com
 
Don said:
ICE processing takes place within the scanner itself.

No, it doesn't. It happens in a library on the host computer.

The only thing happening in the scanner is acquiring the
infrared channel.

Regards,
Ed Hamrick
 
Jean said:
I recently contacted Nikon Tech (via email) about "Analog Gain" and asked
if the scanner varied the exposure time and/or the light intensity. They
responded back that the Nikon LS-40 scanner varies the intensity of the
LED's. I tried to verify this with my scanner by timing scans with no gain
and with max gain; the scan times were the same. I would guess that the
newer Nikon scanners behave similarly.

No, the scan times vary with "Analog gain". You need to do the
test again, but using VueScan, since VueScan drives the scanner
at the maximum possible speed, buffering in memory. The reason
you're seeing no difference is that NikonScan's speed has
a bottleneck of the CPU speed, not the scanner speed, because it
does the ICE algorithm at the same time as acquiring the data.

You should know better than to try to get an accurate answer
from a hardware repair organization. They're only trained in
cleaning scanners and replacing field replacable units. They
know little about how the scanners actually work.

Regards,
Ed Hamrick

P.S. I know that VueScan uses exactly the same fields to vary "Analog gain",
but VueScan's option is "Input|RGB exposure". I've traced the actual
commands sent to the scanner by NikonScan when you vary "Analog gain",
and have done timing to verify this.
 
How do you know so certain?

Because it's an *indirect* method with far too many intermediary
variables. That makes it unreliable.

You'd have to run DOS, turn off caching (including processor cache),
turn off interrupts, etc, etc, etc, to *maybe* have a reliable
correlation between scanner motor activity and bus load. And even then
you'd probably be blindsided by some spurious event you haven't
thought of...

It may be (is!) theoretically possible, but for all practical purposes
you can't rely on listening to the scanner motor alone as indication
of bus load.
You might underestimate the reverse engineering that was undertaken to
understand the data stream coming from the scanner, notably by Ed Hamrick.

I don't see how that plays a part here? Besides, he's been
contradictory and proven wrong before. Has he actually made a
correlation between stepper motor activity and bus load?

Besides, all he does is probably just turn on diagnostic mode in order
to get the data which is not normally available.

There is a reason why this is called "diagnostic" and, indeed, when I
was testing VueScan it screwed up my internal scanner settings every
time. The only reliable reset was turning the scanner off and on
again, which I ended up doing each time I closed VueScan.
Exposure time (inappropriately called gain) can be increased, which has an
audible effect (and it can be timed) because of the increased exposure time
per pixel(line). All very predictable and repeatable. It doesn't change with
image content either, also indicating no internal processing on the many
megapixels (even the smallest processing difference multiplied by the number
of pixels would be noticeable). No lateral thinking, just deduction.

Unfortunately, wrong deduction. Varying Analog Gain (AG) is yet
another of those variables I'm talking about.

Longer AG, more time for data to be sent; shorter AG, less time for
data to be sent. Agreed?

Therefore, short AG may overload the bus, while long AG may not...

Like I said, listening to the scanner motor is not a reliable way of
determining bus load.
If neither the computer, nor the interface show increased activity
approaching or in excess of their processing capabilities, but the scanner
(intermittently) slows down, then the scanner is doing something else than
recording and trying to send. It doesn't seem too difficult, or am I
overlooking something?

Yes, the overall complexity. Like I said, it's an indirect method with
far too many intermediary variables for a reliable correlation.

Don.
 
So, whoever you got that piece of information from at Nikon was simply
selling pork pies to quickly get the monkey off their back, improve
their resolved problem rate and move onto the next mug that had
submitted a non-critical query that could simply be lied out of, leaving
you none the wiser. ;-)

You're just being too kind, as usual... ;o)

I'm yet to see an even remotely relevant reply from the Nikon's
so-called "support" (critical or not) and stopped asking them long
ago...

Welcome back, BTW! :o)

Don.
 
...what is this super intelligent, scanner that "thinks", let alone
knows enough to stop other tasks before it does so? It's clearly male,
since it can only do one thing at a time and thinking takes priority -
good job they don't breed! ;-)

Oh, but they do! And do so by parthenogenesis! I have 3 at last count,
the infamous LS-30 and two flatbeds...

As to thinking... My (film) scanner is often moody and does exactly
the opposite of what I ask! That appears as a strong indication of the
female gender. She can almost be described as a "Permanently Moody
Scanner" or PMS for short. ;o)
Whilst I agree that the listening test is not a definitive test of bus
saturation, it is a test that something has become a bottleneck in the
system
....

That's all I'm saying. While the bus may be one of the top candidates
you can't tell for sure.

So a blanket statement to "listen to the stepper motor" without
caveats is misleading because that's not a reliable standalone
indicator.
Next you'll be telling us that your washing machine solved Einstein's
Grand Theory of Unification before entering its high speed spin cycle.
;-)

Ooh, dangerous territory... To extend the anthropomorphic metaphor:
You don't want to pick a fight with her especially not during the high
speed spin cycle... ;o)

Don.
 
Just turn on the Task Manager if you are running XP or 2000.
It clearly shows the CPU time. With ICE turned on there are two scans
and on my machine it takes twice as long.

Also, The CPU is running 100%! That in and by itself eliminates all
other points as bottlenecks on this particular system which at 100% is
"CPU bound". This means the scanner and USB buss are getting the data
to the processor as fast, or faster than it can handle.

The CPU obviously appears to be the bottleneck in this case which
would eliminate the bus as the culprit.

It's yet another example of where just listening to the scanner
stepper motor does not directly correspond to bus load.

Don.
 
No, it doesn't. It happens in a library on the host computer.

I'll take your word for it... And yet another thing to blame Nikon's
so-called "support" for.

Either way, it doesn't change the original statement: Listening to the
scanner motor is not a reliable indication of bus load.

Don.
 
I'll take your word for it... And yet another thing to blame Nikon's
so-called "support" for.

Either way, it doesn't change the original statement: Listening to the
scanner motor is not a reliable indication of bus load.

Which brings up the question: Does the LS 5000 ED contain a buffer
like many printers? If so, what size? It must, or there would have
to be some method of keeping the data acquisition at, or below that of
the data transfer. If it doesn't, then I'd think they would have to
control the scan rate.

IF the CPU is the bottle neck as it is in mine, that has little if no
effect on the transfer rate as the data is buffered in RAM. (IF there
is sufficient ram). With insufficient RAM it will page file swap and
buffer to the disk, or swap something out of RAM to make room so the
data can still be buffered in RAM. "I would guess" it would be the
latter except in extreme cases which would actually be a combination
of the two resulting in intolerably slow operation.

Another thought comes to mind. That is the actual RAM. I believe I
read the RAM is 333 Mhz which would put the FSB at what? Half that?
What are the CAS and RAS settings? In particular the CAS setting. It
could be 2, 2.5, or 3. It's unlikely to be lower than 2. The CAS
setting which depends on the RAM capability can have a major impact on
speed. Also *all* RAM modules should be identical for best operation.

Roger Halstead (K8RI & ARRL life member)
(N833R, S# CD-2 Worlds oldest Debonair)
www.rogerhalstead.com
 
No, the scan times vary with "Analog gain". You need to do the
test again, but using VueScan, since VueScan drives the scanner
at the maximum possible speed, buffering in memory. The reason
you're seeing no difference is that NikonScan's speed has
a bottleneck of the CPU speed, not the scanner speed, because it
does the ICE algorithm at the same time as acquiring the data.

You should know better than to try to get an accurate answer
from a hardware repair organization. They're only trained in
cleaning scanners and replacing field replacable units. They
know little about how the scanners actually work.

I think you may still be giving them too much credit.
I purchased a D-70 03/23/04. The flash broke with in a week ( got
knocked over while setting on a couple of books about 6 inches off the
"carpeted" floor) and was sent in on 03/31/04. Today was 05/19/04
with no quote, or aknowledgement. The dealer had to call to actually
find they had received the camera.

I think today 05/20/04 may be a good day to call the Michigan Consumer
Services agency and just turn it over to them. Nikon has had that
camera about 50 days and I had it one week. It's a fantastic camera,
but their service "sucks" is about as mild as I can put it.

Roger Halstead (K8RI & ARRL life member)
(N833R, S# CD-2 Worlds oldest Debonair)
www.rogerhalstead.com
 
I recently contacted Nikon Tech (via email) about "Analog Gain" and
asked if the scanner varied the exposure time and/or the light
intensity. They responded back that the Nikon LS-40 scanner varies the
intensity of the LED's. I tried to verify this with my scanner by
timing scans with no gain and with max gain; the scan times were the
same. I would guess that the newer Nikon scanners behave similarly.

Jean,

I read a review that stated that the analog gain really control the
brightness of the light source. Thou the name does not say that
exactly, the analog part does imply it.

Sam
 
As a comparison:

Home brew Athlon 2.8 Gig, 1 Gig RAM @ 333 MHz and doing the R/W to a
200 Gig HD.

I thought I had posted a reply here about what the problem turned out to
be. It was the connection to the computer. When I checked the Windows
Device Manager, I saw that the drivers where no installed for my
motherboard's USB drivers. I updated them and all is not well!

Sam
 
Sam Carleton said:
I read a review that stated that the analog gain really control the
brightness of the light source. Thou the name does not say that
exactly, the analog part does imply it.

Yes, it implies this. However, don't believe everything you read - it
actually controls the CCD exposure time, and it's easy to verify this
with real testing.

Regards,
Ed Hamrick
 
Back
Top