Polaroid SprintScan 35 Film Scanner

Reviewed by Liang-Wu Cai

I have only the privilege of an ordinary user for the scanner, so I know nothing about the installation. The model I used is the original SprintScan 35. From a page at Polaroid (see link above), several other models of this scanner have been introduced ever since, and pictures and the specifications therein seem to indicate that the model is currently designated as the SprintScan 35/SE. I cannot find the negative carrier, so I never used it to scan a negative. Anyway, most of my images are scanned by this scanner.

Specifications

The scanner captures the image in 10 bits per RGB color and outputs 8 bits each, optical density range is 0 to 3.0 (a.k.a. a dynamic range of 3). The light source is a 4W fluorescent tube. The scanner I used is connected to a Mac, and the main image processing program is Adobe's PhotoShop. The scanner driver is provided by Polaroid as a "plug-in" for PhotoShop.

First Impressions

The scanning process is straightforwardly one-pass. You first preview the image, which has a fixed resolution stored in the scanner's memory. Crop, set up image quality controls, then do the final scan. The scanning speed: about 50 second (not counting the preview) for a highest resolution of 2700dpi (dot-per-inch) and 15 to 20 seconds for 1012dpi. I am quite satisfied with the speed.

There are several controls for image quality:

In general, I feel the scanner is easy to use, fast, more than sufficient for web-related and newspaper publication needs. I have an image scanned at 1350dpi (B&W) and printed on an MIT's newspaper (The paper printer printed the image in a 800dpi laser printer then used the laser printer's output to make the printing plates for the paper). The image printed on the newspaper looks very decent, although a coarser than those reproduced directly from real photos.

Some Complains

This is the only slide scanner I have, in some sense, access to. I'd better stop bad- mouthing it. After all, I am happy just for being able to scan slides.

A Well-Intended But Mis-Programmed Mechanism

Polaroid claims a 3.0 dynamic range of the scanner. I cannot find the exact definitions for the terms dynamic range or optical density range. (Someone informed me that this is a well defined photographic term, see, for example, Ansel Adams: The Negative.) My reverse engineering shows me that 10 bits per color gives 1024 grades, which is about 10 to the 3.0 power. That is, 3.0 = log ( 210 ), where log is the logarithm of base 10, or the common logarithm. In any event, I still believe there are some relations between the "dynamic range" and the "bits per color".

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

I used the "auto-exposure" almost exclusively for quite a period of time, and found an undocumented feature: the auto-exposure is actually related to the selected area of the preview image. The selected area is the portion of the images that will be scanned. Afterwards, the selected area can be changed before final scan. This feature allows me to play with the image quality adjustment through "auto-exposure" and choose the best one.

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

After using this scanner for almost a year, I have finally settled with the following way of doing my scanning:

Conclusions

Easy to use, fairly fast, and gives very good quality image. But it could be really hard to obtain consistent results for serial shots with same color tone. More than enough for web publishing needs. If printing (using a high-quality photo printer) is the final goal, I think the dynamic range of this scanner is minimally usable: it would do a fine job for a properly exposed not-too-high-contrast image. Otherwise, it would be tough to get a satisfactory print.

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.


Back to my Digital Darkroom Page
First written: May 13, 1997. Last updated: March 12, 1998.