Re: filmscanners: VueScan 6.4.x suggestion
Ed: I found the same with Vuescan vs. PS 5 for both slides and negatives on my LS-30. I rescanned but with the brightness set at 1.3 for the slide and negative rather than .7. The slide was fine, the negative was OK but with less contrast than the slide. Gordon shAf wrote: > Ed makes us aware ... > > however, what > Vuescan shows me and what I end up with in Photoshop is quite > different (what being acceptable ends up in PS, Vuescan showing me a > darker image). > > shAf :o)
Re: filmscanners: VueScan 6.4.x suggestion
Try increasing the preview dpi and see if you get a closer match between vuescan and PS. - Original Message - From: "Gordon Tassi" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, January 14, 2001 2:20 PM Subject: Re: filmscanners: VueScan 6.4.x suggestion > Ed: I found the same with Vuescan vs. PS 5 for both slides and negatives > on my LS-30. I rescanned but with the brightness set at 1.3 for the slide > and negative rather than .7. The slide was fine, the negative was OK but > with less contrast than the slide. > > Gordon > > shAf wrote: > > > Ed makes us aware ... > > > > however, what > > Vuescan shows me and what I end up with in Photoshop is quite > > different (what being acceptable ends up in PS, Vuescan showing me a > > darker image). > > > > shAf :o) >
Re: filmscanners: VueScan 6.4.x suggestion
>Try increasing the preview dpi and see if you get a closer match between >vuescan and PS. A few days ago Ed told this list that the Preview will rarely match the scan. Once I found out that the Preview in Vuescan was supposed to be different than in the other scanning software I have used it has made using Vuescan easier. I now use the Preview *only* for cropping since all other results are unreliable. Here is what I do -- I know it is a real pain: 1. Do a Preview. 2. Crop. 3. Scan using a a medium resolution. 4. Make adjustments on the Color tab, scan from memory, make adjustments, etc. I iterate through this until I get a result that I like. Each time the image is going to Vueprint so I can check the histogram and also so I can get a bigger image. 5. When I am satisfied with the results of #4 I then reset the resolution to the highest and do the final scan. I have been doing this for about 10 days because that is when I learned that the Preview couldn't be used for anything but cropping. In effect I do two previews. The first one using the Preview button is used for cropping and the second one using the Scan button is used for other adjustments. It slows things down and means doing three scans, but the final scan doesn't surprise me anymore. Naturally, it would be great if the Preview really was an accurate representation of the final scan. Maybe in the future? Henry http://www.bigfoot.com/~hrich _ Get your FREE download of MSN Explorer at http://explorer.msn.com
re: filmscanners: VueScan 6.4.x suggestion
On my scanwit, and I would speculate that other none exposure adjusting scanners as well, the preview and the scan image are very close. Close enough to use preview mem while adjusting color settings to get an image that is great in PS and requires very little tweaking. alan >> I have been doing this for about 10 days because that is when I learned >> that >> the Preview couldn't be used for anything but cropping.
Re: filmscanners: VueScan 6.4.x suggestion
Henry writes ... > A few days ago Ed told this list that the Preview will rarely match the > scan. Once I found out that the Preview in Vuescan was supposed to be > different than in the other scanning software I have used it has made using > Vuescan easier. ... I've never expected the Vuescan preview (or scan window) to match exactly either. However, with this this most recent version the mismatch seems to be more than I've been used too ... and when I drop the brightness to 0.7 for negatives, it is even darker (actually quite a bit darker) ... but I get a good scan into PS ... and I do most of my twiddling in PS anyway. Is there any reason for the Vuescan displays to be darker in these recent versions? shAf :o)
Re: filmscanners: VueScan 6.4.x suggestion
Henry, I've been doing the same for quit some time now, but with a small alteration: I like the autonumbering feature if Vuescan a lot but rescanning will not allow it if you output every file to VuePrint (or whatever...) Instead I start with turning OFF the output file before I even do the preview. Then I scan the slide at the desired resolution. I test different settings in VueScan and each time performes an Scan Mem When I'm satisfied with the look within VueScan I switch it on again and do a last scan mem to output the file. This way I can use the fast scan mem to tweak VueScan to best results in a very fast way and I only have to actually scan the slide twice (preview + scan). It still happens from time to time that I have to perform another scan mem after seeing the histogram of the slide.. Thus the workflow is something like 1) Turn output file OFF 2. Do a Preview. 3. Crop. 4. Scan at the desired resolution. 5. Make adjustments on the Color tab, scan from memory, make adjustments, etc. 6. When satisfied, turn output file ON and perform Scan mem. Off course step 5 would be alot easier if there was a histogram tool within Vuescan and a Zoom tool (Just wishing...) For this to work for everyone I guess that Vuescan should support ICM and take it into account when presenting the scanned picture but this is OK for me right now. Johan Henry Richardson wrote: > > >Try increasing the preview dpi and see if you get a closer match between > >vuescan and PS. > > A few days ago Ed told this list that the Preview will rarely match the > scan. Once I found out that the Preview in Vuescan was supposed to be > different than in the other scanning software I have used it has made using > Vuescan easier. I now use the Preview *only* for cropping since all other > results are unreliable. Here is what I do -- I know it is a real pain: > > 1. Do a Preview. > 2. Crop. > 3. Scan using a a medium resolution. > 4. Make adjustments on the Color tab, scan from memory, make adjustments, > etc. I iterate through this until I get a result that I like. Each time > the image is going to Vueprint so I can check the histogram and also so I > can get a bigger image. > 5. When I am satisfied with the results of #4 I then reset the resolution > to the highest and do the final scan. > > I have been doing this for about 10 days because that is when I learned that > the Preview couldn't be used for anything but cropping. In effect I do two > previews. The first one using the Preview button is used for cropping and > the second one using the Scan button is used for other adjustments. It > slows things down and means doing three scans, but the final scan doesn't > surprise me anymore. > > Naturally, it would be great if the Preview really was an accurate > representation of the final scan. Maybe in the future? > > Henry > http://www.bigfoot.com/~hrich > > _ > Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: filmscanners: VueScan 6.4.x suggestion
>Then I scan the slide at the desired resolution. I test >different settings in VueScan and each time performes an Scan Mem When >I'm satisfied with the look within VueScan I switch it on again and do a >last scan mem to output the file. This way I can use the fast scan mem >to tweak VueScan to best results in a very fast way and I only have to >actually scan the slide twice (preview + scan). The reason I do a scan at a medium resolution (usually 705 dpi) to test out different settings before doing the final scan at 2820 dpi is because even scanning from memory a 2820 dpi 64 bit RGBI scan can take awhile. The intermediate scan from memory at 705 dpi finishes pretty quickly. I typically do 4-8 of these before I'm ready to do the 2820 dpi scan. _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: filmscanners: VueScan 6.4.x suggestion
Alan, Don't you find that the colour balance is markedly altered when you crop the preview and then scan it? I find that my principal subject, somewhere inside the frame, is often more colourful than its surroundings. I find this on my own Scanwit. For this reason I alter the 'Crop|Buffer%' strip round the edge to 10% so that I centre-weight the preview colour balance. It then changes less radically if I crop the image. I haven't worked out whether it's a 10% linear strip right round the outside of the image (1-0.8*0.8, 36% of the pixels) or 10% of the pixels. (Ed H?) Or do you always work on the full image area and crop it later? (Arguably this is an easier way to work.) Regards, Alan T - Original Message - From: Alan Womack <[EMAIL PROTECTED]> To: Majordomo leben.com <[EMAIL PROTECTED]> Sent: Sunday, January 14, 2001 4:19 PM Subject: re: filmscanners: VueScan 6.4.x suggestion > On my scanwit, and I would speculate that other none exposure adjusting scanners as well, the preview and the scan image are very close. Close enough to use preview mem while adjusting color settings to get an image that is great in PS and requires very little tweaking.
re: filmscanners: VueScan 6.4.x suggestion
Yep, and usually on maximum so I get a bit of black border. alan >> Or do you always work on the full image area and crop it >> later? (Arguably this is an easier way to work.) >> Regards, >> Alan T
