filmscanners:Vuescan bugs
On my SS 4000, Win98SE version 7.33 worked fine. Using version 7.35 with b&w Tmax film the following happens: 1) Scan takes 15 minutes instead of about 3 minutes. 2) The image opens up in photoshop upside down and too light, with a histogram that spans only about half the range. I selected "flip" in device tab. Whether I use Adobe RGB or sRGB it still happens. 3) When I try to record a log file to send to Ed, it has a file size of 11.8 mb!! 4) I see from the viewscan site, he no longer answers e-mails for tech support!!! Is this really so? Then why is the log file option box still available? What happened between version 7.33 (worked fine) and version 7.35 and why doesn't Ed support the product anymore? In the past he has been eager to fix problems when we reported bugs to him. Very puzzled, - Jim Hayes
Re: filmscanners:Vuescan bugs
Hi Jim, I had a 'bug' with 7.3.5 with slides scanned on FS4000. The scan was very long. I got a muddy brown picture (flipped) when viewed in Photoshop. The histogram spanned only the center portion of the display. The cure was simple. I just rebooted the computer! John. jimhayes wrote: > > On my SS 4000, Win98SE version 7.33 worked fine. Using version 7.35 with b&w > Tmax film the following happens: > > 1) Scan takes 15 minutes instead of about 3 minutes. > 2) The image opens up in photoshop upside down and too light, with a histogram > that spans only about half the range. I selected "flip" in device tab. Whether > I use Adobe RGB or sRGB it still happens. > 3) When I try to record a log file to send to Ed, it has a file size of 11.8 > mb!! > 4) I see from the viewscan site, he no longer answers e-mails for tech > support!!! Is this really so? Then why is the log file option box still > available? > > What happened between version 7.33 (worked fine) and version 7.35 and why > doesn't Ed support the product anymore? In the past he has been eager to fix > problems when we reported bugs to him. > > Very puzzled, > - > Jim Hayes
Re: filmscanners:Vuescan bugs
correction: that was version7.2.8 that I last tried it and it worked. jimhayes wrote: > On my SS 4000, Win98SE version 7.33 worked fine. Using version 7.35 with b&w > Tmax film the following happens: > > 1) Scan takes 15 minutes instead of about 3 minutes. > 2) The image opens up in photoshop upside down and too light, with a histogram > that spans only about half the range. I selected "flip" in device tab. Whether > I use Adobe RGB or sRGB it still happens. > 3) When I try to record a log file to send to Ed, it has a file size of 11.8 > mb!! > 4) I see from the viewscan site, he no longer answers e-mails for tech > support!!! Is this really so? Then why is the log file option box still > available? > > What happened between version 7.33 (worked fine) and version 7.35 and why > doesn't Ed support the product anymore? In the past he has been eager to fix > problems when we reported bugs to him. > > Very puzzled, > - > Jim Hayes -- Jim Hayes Digital Surrealism Images at http://www.jymis.com/~jimhayes
Re: filmscanners:Vuescan 'bugs'
Can't help with your problem, but I have to make comment (as president of the Ed Appreciation Society!) >4) I see from the viewscan site, he no longer answers e-mails for tech >support!!! Is this really so? Then why is the log file option box still >available? Given Ed is a one man show (or so I understand it) and his product supports a multitude of scanners on 3 operating systems, with a variety of connection methods...and then given the number of weird configurations we all have, is this unreasonable? Heavens, I can't cope with the technical support on *my* system alone, and I'm not exactly illiterate.. :-\ >What happened between version 7.33 (worked fine) and version 7.35 and why >doesn't Ed support the product anymore? In the past he has been eager to fix >problems when we reported bugs to him. And up until yesterday he still was... :-) I think he is simply asking folk not to email him as soon as something goes wrong - just by reading this list it is obvious that there all sorts of problems getting a system running sweetly, many of which are *not* Ed's responsibility. Ed seems to me to be VERY responsive whenever there is a major issue, or a problem that affects more than one user. If you are having a problem that is Vuescan's fault, there's a good chance others on this list will quickly back you up, and I'm sure Ed will sort it. In the meantime, drop back to the version you were happy with... mark t
Re: filmscanners:Vuescan bugs
In a message dated 12/17/2001 8:30:36 PM EST, [EMAIL PROTECTED] writes: > On my SS 4000, Win98SE version 7.33 worked fine. Using version 7.35 with b&w > Tmax film the following happens: > > 1) Scan takes 15 minutes instead of about 3 minutes. Is the film being physically scanned more than once? Are you getting a message about insufficient virtual memory? > 4) I see from the viewscan site, he no longer answers e-mails for tech > support!!! Is this really so? Then why is the log file option box still > available? I answer 100 e-mails every day. However, 90% of the e-mails I used to get could be answered by someone spending two minutes reading the release notes or searching using groups.google.com. Now that it isn't as simple to send me e-mail, I get a higher percentage of e-mail about actual problems. Regards, Ed Hamrick
Re: filmscanners:Vuescan 'bugs'
"Mark T." wrote: > Can't help with your problem, but I have to make comment (as president of I too am appreciative of Ed, since an early version 5 worked much better than Insight 3.5 on the SS 4000 for B&w about October of 1999. > > > > >4) I see from the viewscan site, he no longer answers e-mails for tech > >support!!! Is this really so? Then why is the log file option box still > >available? > > Given Ed is a one man show (or so I understand it) and his product supports > a multitude of scanners on 3 operating systems, with a variety of > connection methods...and then given the number of weird configurations we > all have, is this unreasonable? I simply want to know when this break occured, as I have long enjoyed e-mail tech support which I have used maybe 10 times in over two years. It's like living in a house for two years, then suddenly walking in to find all the furniture moved around. As features were added, I was willing to pay more than $40, or even an annual fee, though I don't have lots of money lying around, for what I get including the once standard e-mail support. And I feel that my question of why still having an log option is a valid one. My other thought on this is that about three times in the evolution of vuescan, serious bugs were introduced for the SS 4000...once it affected only a small number of people (scanning b&w say, I don't really remember). Not many other people would have known how to fix the problem. But when I sent the log file to Ed, he e-mailed back, not only diagnosing the problem, but telling me how my computer was configured (how many SCSI cards and devices, etc)! This is more help and more accurate, and certainly more info than I can type in myself to any newsgroup. So he was able to rev vuescan within a day. Without these logfile feedbacks, the bugs can't be found, and the program isn't improved for bugs. Doesn't it make sense to have a valuable feedback loop? It's been happpening for years with Vuescan. We are all Guina pigs to some extent... > >What happened between version 7.33 (worked fine) and version 7.35 and why > >doesn't Ed support the product anymore? In the past he has been eager to fix > >problems when we reported bugs to him. > > And up until yesterday he still was... :-) I think he is simply asking > folk not to email him as soon as something goes wrong - just by reading > this list it is obvious that there all sorts of problems getting a system > running sweetly, many of which are *not* Ed's responsibility. Yes, I agree on this with one provisio: If nothing else has changed such as scanner, settings, OS, hardware, etc, and one has been using Vuescan for months/years happily and are completely familair with controls, then suddenly with a new rev, very obvious things suddenly change for the worse, one has a right to suspect a bug in the software, and simply send a logfile to Ed, so that if a bug has been introduced as would appear, it can be squashed fast and easily. I also recognise that sometimes a mistake may be made on installation, even by an expericed user, as someone else has suggested; I will check this out, although I have already rebooted my computer. > > > Ed seems to me to be VERY responsive whenever there is a major issue, or a > problem that affects more than one user. This has been the case in the past. So I am simply asking why and when the change and to what extent he no longer accepts e-mails. I can understand a wider base of customers being a problem. I also understand feedback loops being important. And who gets the logfile now if not Ed? I am not angry. I am confused by having the furniture re-arranged suddenly after two years. > > > If you are having a problem that is Vuescan's fault, there's a good chance > others on this list will quickly back you up, As I said, this has not been the case ALWAYS in the past, as sometimes I am what is called in statistics a "Corner Case"...I use Vuescan to scan b&w negs at 16 bit with a SS 4000. As an example, most of you worry about color spaces. I don't, at least not much- they get dropped when it feeds into Pshop 6...and I assign a custom dotgain curve to the image- I don't even use gammma 2.2 greyscale. At least one of the times Vuescan had bugs in the past, there were only two or three of us at most that were affected by it- but no workarounds. > and I'm sure Ed will sort > it. In the meantime, drop back to the version you were happy with... Yes, I have dropped back before and will do this if a new install/ reboot doesn't help.. But you see, in ver 7.3.5, apparently Ed has fixed a problem with focusing on the SS 4000. This is an example of why eventually the latest version must work- hate to be stuck on version 5.2.whatever. > > > mark t -- Jim Hayes
Re: filmscanners:Vuescan bugs
[EMAIL PROTECTED] wrote: > In a message dated 12/17/2001 8:30:36 PM EST, [EMAIL PROTECTED] writes: > > > On my SS 4000, Win98SE version 7.33 worked fine. Using version 7.35 with b&w > > Tmax film the following happens: > > > > 1) Scan takes 15 minutes instead of about 3 minutes. > > Is the film being physically scanned more than once? Ed it looks as if the SS 4000 pulls the film holder in and out a few times or more during scan. Even more damning, the Vuescan progress bar on the right side says "color" and "busy" at different times...and it repeats, as if it's going through the "color-busy-etc" cycle two to four times(more or less). It doesn't repeat the "output crop0001" however. The preview cycle is well behaved however and both preview and scan image looks like it fairly represents the histogram. In photoshop-too bright, 1/2 the contrast range and my original "flipped" preview reflips upside down again. Here's something else, Ed, FWIW. Last time I found a bug it was due to my setting "Focus" from "on preview" to "always", which is I guess is a setting not many people choose, and the bug slipped through the crack this way. The repeated scanning cycles made me think of this oddball setting I use. I don't know if that is a good clue or not. > > > Are you getting a message about insufficient virtual memory? No. I have 512 mb RAM, am running just a few TSR's at same time. I give it 16 mb instead of 2 to zoom in on preview, and the crop0001 tiffs come in at about 22mb each. For the first time though I did change one thing- I finally checked "release memory"...that shoudn't hurt anything AFAIK. There is about 7 or 8 gigabytes left on my SCSI "c" drive...and I let windows 98SE manage it's own virtual memory. > > > > 4) I see from the viewscan site, he no longer answers e-mails for tech > > support!!! Is this really so? Then why is the log file option box still > > available? > > I answer 100 e-mails every day. However, 90% of the e-mails > I used to get could be answered by someone spending two > minutes reading the release notes or searching using > groups.google.com. Now that it isn't as simple to send me e-mail, > I get a higher percentage of e-mail about actual problems. Ed thank you for explaining that. My tone seems to have come off as angry, which was not my intent. I did mean to convey confusion and puzzlement, and a desire to know why, when and to what extent we should be refraining from e-mailing you. What you say makes perfect sense. And I have made my share of bone-headed mistakes, easily solvable. I have also worked through maybe four real problems with you that resulted in a rev to software, so I just wanted to know when to e-mail you and when not to. In this light, having a logfile is still very valuable. I just wish I could upload it to you and this could be figured out fast. But I'm not going to bomb you with an 11.8 mb file, and my ISP would not like it either. My last version I tried that worked was 7.2.8...I loaded ver 7.3.3 but didn't get a chance to use it, slight correction there. Thanks, > > > Regards, > Ed Hamrick -- Jim Hayes Digital Surrealism Images at http://www.jymis.com/~jimhayes
Re: filmscanners:Vuescan bugs
In a message dated 12/18/2001 4:16:28 PM EST, [EMAIL PROTECTED] writes: > Ed it looks as if the SS 4000 pulls the film holder in and out a few times or > more > during scan. Do you perhaps have the "Prefs|Release memory" option turned on? This option causes this kind of problem. It's fixed in 7.3.6, which I'll release in a day or so. Regards, Ed Hamrick
Re: filmscanners:Vuescan bugs isolated
Ed, I was just testing this very thing. I tried changing three things: 1) "focus" from "always" to "on preview"; 2) Changing both monitor and file space from Apple RGB to Adobe RGB and back (remember I have a b&w image); and 3) checking/unchecking the "release memory" box. I normally leave this unchecked, since Pshop can run with vuescan up. That's the variable that changes things Ed..."release memory" reflips, lightens, and compresses to 1/2 the contrast range in pshop. When I uncheck it I get nice, full histograms, correctly flipped image. I can also tell you that on my windows 98SE system, both the displayed image in Vuescan and the b&w image in Pshop are a little darker with "Adobe RGB" selected vs "Apple RGB". It is also reflected in the pshop histogram. I hope that helps solve your color space problem. [EMAIL PROTECTED] wrote: > In a message dated 12/18/2001 4:16:28 PM EST, [EMAIL PROTECTED] writes: > > > Ed it looks as if the SS 4000 pulls the film holder in and out a few times > or > > more > > during scan. > > Do you perhaps have the "Prefs|Release memory" option turned on? > > This option causes this kind of problem. It's fixed in 7.3.6, which > I'll release in a day or so. > > Regards, > Ed Hamrick -- Jim Hayes
Re: filmscanners:Vuescan bugs isolated
In a message dated 12/18/2001 5:35:10 PM EST, [EMAIL PROTECTED] writes: > That's the variable that changes things Ed..."release memory" reflips, lightens, > and compresses to 1/2 the contrast range in pshop. When I uncheck it I get > nice, full histograms, correctly flipped image. Yes, I've found the problem and fixed it. The problem was that it has to do two passes over the memory buffer in 7.3.5, once with the Monitor color space and another time with the File color space. The memory buffer was getting cleared after the first pass, so the passes for the file writing were going all the way to the scanner. > I hope that helps solve your color space problem. It's fixed in VueScan 7.3.6 - thanks to all the people on this mailing list for helping solve this. Regards, Ed Hamrick
