[filmscanners] Re: Vuescan problem

[John Matturri]

 I completely missed your kind offer - thanks.  And thanks to everyone
 who responded.  I got zero response form comp.periphs.scanners, and
 surprisingly, no response from an e-mail to Ed. But I'm sure he's
 swamped.   So you guys are it!


Ed's replies tend not to be immediate so you may still hear from him. A
couple of days ago I got a note to check out a revision after sending
out a log file more than a week ago.

John M.




Unsubscribe by mail to [EMAIL PROTECTED], with 'unsubscribe filmscanners'
or 'unsubscribe filmscanners_digest' (as appropriate) in the message title or body

[filmscanners] Re: vuescan problem

[Eric]

John:

Ever since I started to scan color negatives with vuescan
(on SS4000) I periodically get scans that differ greatly
from the preview. Usually with a much narrower range of
values and odd casts, often a bright, almost solarized blue
cast in white highlights and more recently an overall green
cast. This makes batch scanning impossible because somewhere
in the strip the scans eventually start having these
properties.

I've encountered similar weirdness with Vuescan (don't remember the version
number I'm on, but it's about 2 months old.)  Usually only happens when
batch scanning.  Sometimes with BW, sometimes with color.  Instead of
getting a weird cast, I get an image that's totally unrecognizeable.  Looks
like the memory has been corrupted.  I actually saw this doing a single scan
for the time ever.  I was scanning all the negatives on a particular strip,
but scanning one at a time.  I ejected the film carrier, and did a new
preview and a new scan, and all was well.

I'm using the SS4000, too, on WinNT with 256 meg of memory.  I rarely scan
all the negatives in a single strip, so it's not a huge deal to me.  I'm
guessing that memory is being corrupted somewhere.  But ejecting the carrier
and re-inserting it helps.


Eric


Unsubscribe by mail to [EMAIL PROTECTED], with 'unsubscribe filmscanners'
or 'unsubscribe filmscanners_digest' (as appropriate) in the message title or body

[filmscanners] Re: vuescan problem

[John Matturri]

PC, Win98 original edition, 128MB Ram, latest Vuescan, it occurs usually after a 
number,
though not a definite number, of scans.

The memory theory is quite attractive for me given that in two weeks or so I'll be 
getting
delivery on a new computer with 1.5GB of RAM. This happens on relatively small (20MB) 
files
but I don't release memory after every scan so I guess that could be an issue. But if 
it's
apt to be a computer problem not a software problem at others are having I guess it's 
best
just to hang in for a couple of weeks.

Thomas B. Maugham wrote:

 John:

 You haven't provided a great deal of information so it's hard to diagnose.
 Are you using a Mac or a PC? What version of the operating system are you
 using? How much memory do you have? How large is the swap file on the disk?
 What version of VueScan are you using? How often does this occur (i.e. once
 in a strip of 6 negs), when does it occur (i.e. the fifth neg in the strip),
 etc.

 On the surface it sounds to me like a memory problem in that you may not
 have enough memory to store all the scanned images and when it tries to
 write or read the information to or from the swap file on the disk it fails.

 I offer this as I use VueScan for both negs and slides and haven't seen this
 but I have 256mb of memory and a huge swap file on my disk so that may be
 the solution.

 Tom

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of John Matturri
 Sent: Friday, May 17, 2002 2:25 PM
 To: [EMAIL PROTECTED]
 Subject: [filmscanners] vuescan problem

 Ever since I started to scan color negatives with vuescan
 (on SS4000) I periodically get scans that differ greatly
 from the preview. Usually with a much narrower range of
 values and odd casts, often a bright, almost solarized blue
 cast in white highlights and more recently an overall green
 cast. This makes batch scanning impossible because somewhere
 in the strip the scans eventually start having these
 properties. The only way to get rid of this behavior is to
 close down the program and rescan. I've raised the problem
 with Ed once or twice over the past few years but never got
 a solution. Except for these cases I like the scans I am
 getting so I put up with this but it is frustrating and
 time-wasting.

 Anyone else have this problem, or even better, have a
 solution to it.

 --
 John Matturri
 words and images: http://home.earthlink.net/~jmatturr/

 
 
 Unsubscribe by mail to [EMAIL PROTECTED], with 'unsubscribe
 filmscanners'
 or 'unsubscribe filmscanners_digest' (as appropriate) in the message title
 or body


--
John Matturri
words and images: http://home.earthlink.net/~jmatturr/



Unsubscribe by mail to [EMAIL PROTECTED], with 'unsubscribe filmscanners'
or 'unsubscribe filmscanners_digest' (as appropriate) in the message title or body