Posts

Native Resolution Scanning on Coolscan Units and the Limits of Upsampling

Australia has a small but devoted community of film scanning hobbyists from Hobart to Cairns, many running older Coolscan units that have survived decades in former photo labs in Melbourne and Sydney. The country imports most scanner hardware second-hand from Japan and the United States, so people feeding slides through a Coolscan today are often the third or fourth owner. With that secondhand economy, the question of how to get the best file from a given piece of glass comes up constantly on forums and in club meetings.

Native resolution on a Coolscan refers to the optical pixel count the sensor captures in a single pass, with the lens and stepper motor delivering the film at its true physical sampling density. On the LS-5000 that figure sits near 4000 pixels per scan line for a 35mm frame, while the LS-8000 and LS-9000 push into the 5000 to 6000 pixel range through finer optical steps. These numbers are tied to the physical aperture, the LED light bar behaviour, and the precision of the lead screw.

Upsampling, in the form most Coolscan owners practise, means running a lower optical resolution scan and enlarging the pixel dimensions through software such as Photoshop, GIMP, or one of the AI resizers bundled into modern raw converters. The scan completes faster because the scanner takes fewer samples, the file shrinks, and in some cases the operator believes they are smoothing over sensor noise. Some AI upscaling demonstrations also suggest modern software can hallucinate convincing detail from thin information.

The Australian context adds wrinkles. Hard drives cost more per terabyte than in many comparable markets, archival-grade optical media is harder to source in Adelaide or Perth, and the humidity along the Queensland coast can damage both film and storage. Those pressures push some users toward smaller files, but they also make it tempting to oversell what an upsampled image actually contains.

How Native Resolution Works on Coolscan Hardware

The optical path inside a Coolscan begins with a focused light source, a cold cathode lamp on early units and an RGB LED bar on the LS-5000 and later. The light passes through the negative or slide, through a fixed lens assembly, and onto a linear CCD sensor. That sensor has a fixed number of photosites, and the film is moved past it by a precision stepper motor that advances in increments tied to the optical formula of the lens.

When the user selects a higher resolution in Nikon Scan or VueScan, the software asks the motor to take smaller steps, producing a longer scan with more samples across the same frame. The native ceiling is reached when the steps become so small that diffraction, lens aberrations, and sensor noise dominate. Beyond that ceiling, additional samples do not represent new optical information; they are essentially overlapping samples of the same patch of film.

The LEDs on later models pulse in sequence to expose each colour channel, calibrated so the red, green, and blue exposures land on the same physical points of the film. This alignment is what makes the native scan honest. The file is a faithful representation of what the lens and sensor could see, with very little hidden guesswork.

The Data Your Negatives Actually Contain

A 35mm colour negative or transparency, shot on a sharp lens and properly focused, contains a finite amount of resolvable detail. For most consumer films of the last forty years, the effective resolution of the emulsion and the recording lens sits between 4000 and 6000 pixels per frame width. That range aligns with the resolving power of films like Portra 400, Ektar 100, and Velvia 50, and with the limits imposed by the camera lens.

When a Coolscan samples at its native optical rate, each pixel in the output file corresponds to a real measurement taken from the film. When the scanner is asked to step finer than the hardware can resolve, the output starts to contain averaged neighbouring samples, which means adjacent pixels begin to carry the same value. This is not extra detail. It is a softer, smoother file that only appears sharper because of interpolation.

Upsampling adds even more generated pixels on top of that already-averaged data. The software fills in values between samples by guessing at what might have been there. Sometimes the guess is plausible, and sometimes it is not, but it is always generated rather than measured. The file looks larger and may print larger, but it does not contain more information than the original capture.

Why Software Upsampling Cannot Recover Detail

The persistence of the upsampling habit often comes down to a misunderstanding of how resolution works in a sampled system. Detail has to be captured at the moment of measurement. If two objects on the film are closer together than the spacing of the sensor samples, the sensor cannot distinguish them, and software cannot retroactively separate them, because the wavefront has already been discretised.

Modern AI upscalers do something cleverer than bicubic interpolation, and can produce images that look more detailed than the input. They learn typical structures from training data, recognise textures that match what the input seems to contain, and paint in plausible continuations. For low-resolution snapshots and family photos, that can be a genuine improvement. For archival film scans where the goal is honest reproduction, it is closer to invention.

There is also a danger specific to archival work that matters in the Australian climate. Film stored in a garage in Brisbane or a shed in Darwin can develop mildew, fading, and density shifts that change over time. If a scan is upsampled, those flaws are also upsampled and amplified, because the software cannot tell the difference between subject texture and artefact. A native scan preserves the flaws at their true scale.

File Size, Storage and Workflow Realities in Australia

Storage costs and habits shape scanning choices more than most people admit. A native 4000 dpi scan of a single 35mm frame on an LS-8000 produces a 16-bit TIFF in the 60 to 100 megabyte range once all three colour passes are combined. Multiply that by a few hundred frames from a holiday trip to the Kimberley or a year of family slides, and the numbers climb quickly into hundreds of gigabytes.

Bandwidth for cloud backups over the National Broadband Network can make uploading multi-hundred-gigabyte archives slow, especially for households on satellite or fixed wireless connections in regional Western Australia or the Northern Territory. That pressure pushes some users toward smaller files, and smaller files almost always mean upsampling or aggressive JPEG compression.

The honest path is to keep the native scan as a master, store it on redundant local media such as mirrored external drives, and only produce downsampled or compressed derivatives for sharing. A master file is the only record that can be re-edited if better colour science or dust removal software appears in years to come.

When Higher Pixel Counts Are Legitimate

There are situations where the rule of native resolution has to bend. Multisampling on the LS-9000 takes multiple scans at the same native rate and combines them to reduce sensor noise without inventing new detail. That is a legitimate way to clean up dense shadows on a heavily underexposed frame, particularly for astrophotography slides taken in the Australian outback where light was scarce.

There is also a role for higher resolution on medium format film. The LS-8000 and LS-9000 can scan 120 and 220 strips with their optional medium format holders, and the larger negative area genuinely contains more detail. A native scan of a 6x9 frame can carry around 8000 to 10000 pixels of real information across the long dimension, and asking the scanner for that resolution produces a file that earns its file size.

The exception worth being wary of is using AI upscalers on already-scanned files. For casual sharing on social media or A4 prints, a tasteful upscale of a native scan can look very good. For archival purposes, prints larger than A3, or any work intended for publication, the AI result should sit alongside the native master and not replace it.

Practical Workflow for Honest Resolution

A clean workflow starts with the scanner itself. The Coolscan should be warmed up for at least fifteen minutes so the LEDs and sensor stabilise, the film holder should be inspected for dust, and the focus should be set using a focus target rather than relying on the autofocus button. These steps make sure any native scan is the best the hardware can produce.

Once captured, post-processing should work in a wide gamut colour space and 16-bit depth to preserve nuance. Editing in 8-bit JPEG introduces banding that no amount of upsampling can fix. The master file should be archived in TIFF or a lossless format, and only then should derivatives be created for sharing or printing.

For users who want to compare approaches on the same frame, the simplest test is to scan a single slide at three resolutions, native, double native, and a heavily upsampled low resolution, and view them at 100 percent in an editor. The differences become obvious quickly. The angelrute guide on the site walks through this kind of side by side comparison in detail.

A useful checklist for anyone running a Coolscan today:

The next practical step for any Coolscan owner reading this is to pull one frame from a recently completed roll, scan it at its native setting, save the TIFF, and save a second version upsampled by 200 percent through the software of your choice. Open both files side by side at 100 percent view and study a high contrast edge, such as the line of a building against the sky in a Melbourne street scene, or the fine texture of bark on a gum tree photographed in the Blue Mountains. The native scan will show a clean, measurable edge; the upsampled version will show a softer, invented transition. That single experiment will set the standard for every scan that follows.