ILyons <[EMAIL PROTECTED]> wrote:
> Its the same darned scanner. I use the SAME scanner on PC and Mac platform
I
> use the SAME scanner with NikonScan, SilverFast and VueScan. The ONLY time
> jaggies EVER occur is with NikonScan when CMS is ON.
Ian, I've had jaggies with CMS off. It's not purely related to the CMS.
Hell, I've even had jaggies with earlier versions of Vuescan - which has no
CMS.
> Think about this! If my scanner works without a problem in EVERY
compatible
> scanner package and platform EXCEPT Nikon Scan with CMS ON then how can
this
> be a resonance problem ??
As I mentioned - using the CMS probably adds CPU overhead in processing the
data. That causes pauses in the scan cycle. It may also be that Nikonscan
sends different commands bedpending on whether CMS is enabled or not. I
don't know - that's one for Ed.
> If so then why does a change in scsi timing cure
> the problem, switching of the CMS cure the problem, but faster processor
and
> more (buckets more) doesn't. The scanner starting and stopping as it scans
> has damn all to do with the jaggies if it did then the results out of
> SilverFast with ICE on would be absolutely dire, since it scans it at
snails
> pace and stops and starts even more frequently than NikonScan.
Ian, I can see you're upset about this, but I think you're letting your
anger get in the way of logical analysis. I have, as I mentioned, had
jaggies with CMS on *and* off. And with older versions of vuescan. I've
also experienced the problem much less when my hard drive was able to have
DMA enabled and wasn't stealing 60% or more of the CPU cycles writing data.
If the problem was only to do with Nikon CMS, it would NEVER have occurred
with Vuescan.
I have a 533MHz processor waiting to be plugged in, as well as a UDMA100
card. If I can get the CPU upgraded and DMA enabled again, I'll try
Nikonscan and see if its behaviour has changed. Until then, I have no data
from personal experience to work with other than to say that jaggies
occurred less after I went from a P90 with 64MB RAM to a Celeron 366 with
96MB RAM.
Try scanning a small selection of a problem slide with Nikonscan and CMS.
When I did this using a slide that had *always* produced jaggies, they went
away. The fact that the selection was small enough that hard drive
buffering and CPU overhead were far less of a problem was evidence enough
for me that there's more factors involved.
I'd be interested to know if the problem would ever occur if I was using
SCSI hard drives rather than IDE.
Rob
====================================================================
The filmscanners mailing list is hosted by http://www.halftone.co.uk
To resign, <mailto:[EMAIL PROTECTED]> with UNSUBSCRIBE FILMSCANNERS in the
title, or UNSUBSCRIBE FILMSCANNERS_DIGEST if you are reading the Digest.
