- Joined
- Oct 11, 2006
- Messages
- 2,184
- Format
- Multi Format
A couple of thoughts: What dpi are you using? In principle if you want to reduce the risk of banding it is best to use higher dpi. Interpolated dpi doesn't count. Just real hardware limited dpi. The explanation of why this is so is somewhat involved and rather subtle, but I will explain it if anyone wants to hear the reason. I realize that the scanner resolution is limited to about 2400 effective dpi, so a lot of people will scan at low dpi. However, there are other factors in play here that makes it desirable to scan at higher dpi if you want to reduce the likelyhood of banding.I've been using a V850 Pro with both Epson Scan and SilverFast, started with Epson until I got the time to explore SilverFast, which I really like.
However - In scanning some 4x5 negs, black and white, which have large open sky areas (no clouds, the yellow filter kind), which attempting to deepen in value, I get banding. Some info on what I'm doing:
I adjust the scan settings to very close to final tonal values
Saving in Tiff 8bit grayscale (SF doesn't allow 16bit, for some reason)
Open the Tiff in raw, if any other adjustments are needed.
Open in PShop and make edits if needed.
I'm working on one with a large sky area which I want to deepen just the sky, doing so with a gradient mask, in PShop, to the sky area only. When I saw the banding the first time, I reopened the Tiff in Raw, deepened the whole thing, opened a second copy of the file, copied the darker image, and pasted it into the original file as its own layer, applied a gradient mask to that image layer, just to hide the part I don't want to see. The effect is right, but the banding is there anyway, just because the sky has it's own gradation, I guess.
I haven't had this happen with smaller formats, maybe because grain masks or prevents the banding.
I'm thinking this banding would be minimized in a 16 bit file, but SF won't allo that (it's selection is 16->8bit).
Epson Scan allows a simple 16 bit choice in their popup menu. (I've used it before)
Any ideas about this?
+1I use Lightroom extensively - I just need to figure out why it won't sync my photos properly. The reason for saving RAW from SilverFast is that the less expensive versions of SilverFast do not allow you to save as 16-bit TIFF files. Scanning in RAW is a work-around for this problem.
@gratSo your belief is that general purpose software is just as good as purpose-written, optimized software?
That's an... interesting viewpoint.
Yes, you probably can do the same sort of editing with Lightroom or Photoshop-- but you'll work considerably harder at it.
@alanrockA couple of thoughts: What dpi are you using? In principle if you want to reduce the risk of banding it is best to use higher dpi. Interpolated dpi doesn't count. Just real hardware limited dpi. The explanation of why this is so is somewhat involved and rather subtle, but I will explain it if anyone wants to hear the reason. I realize that the scanner resolution is limited to about 2400 effective dpi, so a lot of people will scan at low dpi. However, there are other factors in play here that makes it desirable to scan at higher dpi if you want to reduce the likelyhood of banding.
The other thing is that if you scan in 8 bit mode then before you do any processing of the stored file you should convert to 16 bits.
Those two things should reduce or eliminate the risk of banding.
Also,
@grat
Do I understand you correctly? Are you saying the same sort of corrections are easier to do in Silverfast or Vuescan than in Lightroom or Photoshop?
IF, IF, IF my understanding is correct, another point of view is that the editing features in the Adobe software are much better than the ones in any scanning software. And, you want to keep all your edits in one place.
I think you left out MT compensation. (Miller Time but may be Bud compensation)** It's possible I made some of those up.
If the noise is comparable to the ADC step size in the scan then you won't see banding if you follow the procedure I mentioned (i.e. converting to 16 bits before processing the image further.) For the purposes of this discussion, film grain is a form of noise, and so is sensor noise.@alanrock
If you scan at 8 bits, then even if you store and save as 16-bits, you only have 8 bits of data to work with. I think it's necessary to scan at the max bit depth allowed by the scanner.
It's an viewpoint based on practical experience and results. I've scanned 35mm, 120, and 4x5 film with both V600 and V850 Epson scanners and worked with Epsonscan for over ten years. And I've used Lightroom and PS Elements in post. The editing in all scan and post processing software changes colors, exposure values, black and white points, etc. Lightroom in particular is more powerful. PLus it has the added advantage of not changing a flat scan made by the scanner. Changes made by Epsonscan in other than the original capture functions just duplicate Lightroom's functions with less finesse. Plus, if you get edits wong during the scan, you have to rescan. I've never used Silverfast or Vuescan. But they edit the scanner's output as well except for special scans like multiple scans which I don't do or need. While I never used these, most people who have reported that SF in particular is a very difficult program to use, Vuescan a lot less so.So your belief is that general purpose software is just as good as purpose-written, optimized software?
That's an... interesting viewpoint.
Yes, you probably can do the same sort of editing with Lightroom or Photoshop-- but you'll work considerably harder at it.
I just noticed this post after posting my last one. Some questions on your three points.No. I'm saying that the software and algorithms inside SilverFast are specifically designed for scanning. Take negafix-- If you ever get a chance to look at the "expert" mode, you'll see it's applying not just level adjustments, but actual color curves and some mapping. All of these features are available in Lightroom, but I can't click "Fuji --> Pro --> 400h (6x6)" in Lightroom.
The reason that Adobe (or Affinity) is a better suite of editing tools, is that SilverFast isn't an editing package. It's a scanning package, that allows you to get a head start on your image editing-- which, as you say, should be done in an editing package. Scan with scanning software, edit with editing software-- I'm not sure where that became confused.
To me, the most useful parts of SilverFast are:
Everything else? iSRD, USM, WTF, SRDx, GANE, AACO, BBQ**... I turn those off. I used GANE (noise reduction) once on a very, very bad negative, and it probably helped.
- negafix: I wish they'd come out with some more profiles, but it's nice to have your negative inversion "just work". By the way, trim out the white borders around the images for best results.
- histogram before scanning. I tweak the histograms to 1) avoid clipping and 2) set the histogram to match the dynamic range of the image. If I'm scanning 8 bits per channel, I want 0 to be the darkest pixel, and 255 to be the brightest: If it's 16 bits, then I want the brightest spot to be 65535 (check with densiometer function).
- multi-exposure: For negative film especially, it should give a better dynamic range. I need to pull out one of my "trouble" negatives and re-scan to verify that, though.
After that, all the work is done inside the editor of choice, which for me right now is Affinity.
** It's possible I made some of those up.
I've been using a V850 Pro with both Epson Scan and SilverFast, started with Epson until I got the time to explore SilverFast, which I really like.
However - In scanning some 4x5 negs, black and white, which have large open sky areas (no clouds, the yellow filter kind), which attempting to deepen in value, I get banding. Some info on what I'm doing:
I adjust the scan settings to very close to final tonal values
Saving in Tiff 8bit grayscale (SF doesn't allow 16bit, for some reason)
Open the Tiff in raw, if any other adjustments are needed.
Open in PShop and make edits if needed.
I'm working on one with a large sky area which I want to deepen just the sky, doing so with a gradient mask, in PShop, to the sky area only. When I saw the banding the first time, I reopened the Tiff in Raw, deepened the whole thing, opened a second copy of the file, copied the darker image, and pasted it into the original file as its own layer, applied a gradient mask to that image layer, just to hide the part I don't want to see. The effect is right, but the banding is there anyway, just because the sky has it's own gradation, I guess.
I haven't had this happen with smaller formats, maybe because grain masks or prevents the banding.
I'm thinking this banding would be minimized in a 16 bit file, but SF won't allo that (it's selection is 16->8bit).
Epson Scan allows a simple 16 bit choice in their popup menu. (I've used it before)
Any ideas about this?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?