Doug Franklin wrote: > Make sure you've got at least 256MB of RAM in your system or you're > going to do a lot of waiting. I'm maxed out at 512MB and it helps when > you've got more than one image in memory, like batch scanning. 1GB is not > too much if you want to batch scan all six frames in the negative carrier > at once at full resolution.
Not a problem. I have 512... I'd have 1Gb by now if it wasn't for Win ME. I don't plan on doing batch scanning. > That allows you to scan an entire roll of APS film at once. I hate to > think how much memory that takes at full resolution. Who cares ;) I do wish it could scan true panoramas (mine are 24x68mm). The HP S20 is the only 35mm scanner I know of that can do this. But thats a minor point as my Arcus 1200 can handle those, if my calibration slide ever turns up. > Scanning a frame at 4000 dpi, 42-bit color, with FARE (IR scratch/dust > removal) enabled, will take around ten to fifteen minutes per frame. That's quite a long time but for the price I have to expect to make some tradeoffs. I saw one review posted a couple of samples images with FARE on and off and it looks quite good. Unless you use the "strong" setting there appears to be very little, if any, image degradation. Rather than using FARE I will start by just cleaning the slide and rubber- stamping dust out. If thats too much of a chore I'll put the FARE on :) > The > vast majority of this time seems to be the actual scanning. It doesn't > look like changing from USB to SCSI would help much, as a fraction of the > total time. It seems like it might knock off fifteen to thirty seconds, > but that seems to be about it. I had to buy a SCSI card for the Arcus 1200 so I'll buy another cable and hook it onto that. The Canon scanner only supports USB1.1 which isn't exactly blazingly fast for this kind of application. USB2.0 is a lot faster. > FARE works very well, but big scratches or hairs or things will cause it > to fail. The bummer is that the driver doesn't detect the failure until > after the entire scan is done, then it throws away the image due to the > failure. Cleaning the negative and rescanning almost always works. I keep a blower-brush at the computer desk and _always_ clean my slides prior to scanning. A five-second brush saves several minutes of retouching... > These operational problems are not enough to keep me from using the > scanner, though the memory leaks can get me pretty frustrated > sometimes. Yeah it does sound a little annoying, but bad software is a lot easier to fix than bad hardware :) Have you tried it with Vuescan? > The biggest problem I'm having is what appears to be grain aliasing. It > only happens at 4000 dpi, and I'm afraid the only real way to fix it is to > go up or down in resolution. I've heard that grain aliasing occurs with all 4000dpi scanners anyway. Do you know what slide films would be like in that case? The films I use most are Kodak E100SW and Fuji Provia 100F (and a few rolls of Velvia). > I'm still trying to figure out a really good way to even it out after > scanning. The Arcus 1200 driver has an amazingly good descreening function, but that's designed to get rid of regular line-screens from halftoned material. Thanks for the comments, Doug. Do you have any specific comments on the scanner's dynamic range? Cheers, - Dave http://www.digistar.com/~dmann/ (out of date) - This message is from the Pentax-Discuss Mail List. To unsubscribe, go to http://www.pdml.net and follow the directions. Don't forget to visit the Pentax Users' Gallery at http://pug.komkon.org .
