
![]() | Polaroid SprintScan 35 Film ScannerReviewed by Liang-Wu Cai |
First Impressions
There are several controls for image quality:
Some Complains
A Well-Intended But Mis-Programmed Mechanism
Theoretically this is sufficient for almost all computer displays, which are typically 8 bits per color (and called 24-bit video, or 16 million colors). But my experience is that most scanning I've done do not contain as fuller as possible a dynamic range: the shadow details are not sufficient, and the image manipulations afterwards tend to worsen the situation as shadow details turn out in wrong colors. Occasionally, even the preview image shows the dark area in funny colors. In such cases, I think the best we can do is to take as large a dynamic range the scanner can offer during the scanning, then fine-tune the image in post-scanning image processing.
From this perspective, I think the white-point and black-point mechanism would ideally serve this purpose. However, in the actual use, the selection of white-point and the black-point is done on the preview image. It is a pity that the preview image has a very low resolution and cannot be enlarged to a size that is comfortable for working with pixels. It becomes very tricky to pick the correct pixel, and in the event the chosen point is not the brightest or the darkest point of the image, the image look weird.
Even I am lucky enough to have picked the correct (desired) point, guess what: the color cast can become very different. The software has a provision to maintain the color cast. However, I believe Polaroid software engineers have not had their minds straight. The software works this way: if the picked dark point has the RGB triplet as (10,10,15), the program subtracts 10 from each to give (0,0,5). So the dark cyan becomes dark pure blue. This might not be significant since the point is declared "black", but if the same method is used to scale all other colors, it is simply impossible to maintain the color balance. I think the correct way should subtract the each element in a proportional way to make it (2,2,3).
In any event, the white-point/black-point mechanism is a well-intended mechanism but practically useless as it is currently implemented. Using the programs "auto-exposure" usually is the best compromise between the speed and the quality of results. But, as mentioned before, the color cast again becomes an issue.
Undocumented Goody and Nightmare
The "auto-exposure" changes the color tone. Luckily, this information is displayed, so I can keep an watching eye on this issue, and correct the color if necessary. On the other hand, I found that is it almost impossible to obtain consistent results. This is the main reason that turned me away from using the "auto-exposure".
Actually, what I really want is to have faithful representations of my slides. All I want is to have the scanner scans the slide according to a set of predefined parameters, and I later use an image editing software to do a procedural fine-tuning. I had imagined that this would be a humble and actually quite a mechanical procedure.
With this scanner, things actually turned quite nasty. Even with a custom setting predefined in a file, scans still turn out different colorcasts. I suspect the reason of this hopeless situation is its calibration process. The scanner uses a cheap fluorescent tube as the light source. The designer of the scanner is aware of the quality (of the lack of) of such tubes, and thus the color calibration is done in every scanning. This calibration becomes a nightmare if one wants to obtain consistent results.
The Way I Do My Scanning
Conclusions
If I am in the market for a scanner for myself, I'd probably look for a higher model in the line: Polaroid SprintScan 35 Plus, a 12-bit-per-color model, or Nikon's equivalent Super CoolScan 1000.