# The ReelSlow8 Film Scanner

**URL:** <https://forums.kinograph.cc/t/the-reelslow8-film-scanner/2491>\
**Category:** Machine Design\
**Created:** [February 25, 2023, 7:28am UTC](https://forums.kinograph.cc/t/the-reelslow8-film-scanner/2491 "2023-02-25T07:28:25Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![npiegdon](https://forums.kinograph.cc/user_avatar/forums.kinograph.cc/npiegdon/32/2729_2.png) [@npiegdon](https://forums.kinograph.cc/u/npiegdon)\
**Post date:** [May 1, 2023, 6:25pm UTC](https://forums.kinograph.cc/t/the-reelslow8-film-scanner/2491/19 "2023-05-01T18:25:32Z")

</div>

> [@cpixip](#):
>
> Well, the density variation of a standard color-reversal film, say Kodachrome, easily covers a range equivalent to a 12 to 13 bit/channel sensor.

Ah ha, I understand what you meant now. And while I’ll agree that reducing the contrast will help you acquire the full range of the image more easily (possibly in a single exposure), isn’t a loss of contrast essentially the same as a loss of information? (It’s almost a tautological statement: we need multiple exposures to capture high-contrast images _because_ there’s more information there than a 10- or 12-bit sensor can capture in one go.)

Outside of presenting the final results on HDR viewing equipment, I understand at some point in the processing chain (hopefully near the end) there is a “mix down” step where you convert to some 8-bit/SDR “window”, but in general it seems like the goal should be to maximize the available contrast/bit-depth available right up until that step.

This particular sensor has a couple 12-bit modes and a 16-bit raw mode for retrieving image data, but that’s just a description of the range of expressible values over the wire. I haven’t done any testing to see what sort of real dynamic range I’m getting from the sensor yet. Although, starting from one of Sony’s Gen3 Pregius models, I have high hopes. With a well depth of 20Ke-, in theory there should be somewhere in the vicinity of 14-bits to play with, but reality probably won’t be quite so kind.

> [@cpixip](#):
>
> In the last century, most people working in film and photography aimed at the same target: getting as little grain as possible.

We have direct evidence of this claim from the 1996 demo of Kodak’s “Vision” system in this RobinoScan [post](https://forums.kinograph.cc/t/robinoscan-rt-16-35-scanner/2189/42). The host mentions film grain (in the context of it being a negative thing that you want to minimize) several times starting at 5m30s and again at 8m30s. Reducing grain is one of the four major feature points they tout as the reason to switch to the new film stock!

> [@cpixip](#):
>
> This is usually done by employing the temporal coherence of film frames viewing the same area in consecutive frames.

My favorite app for this is made by the NeatLab folks. They already have best-in-class de-noising for still images in their Neat Image product. And then their [Neat Video](https://www.neatvideo.com/home) product adds a temporal component on top of that. Combine that with very attractive pricing and I’ve been using it to clean up digital sensor noise for years. I haven’t tried it with film grain yet, but I’m excited to see what it can do. The results usually feel a little like magic.

I agree that temporal denoising is one of the first and most important steps.

> [@cpixip](#):
>
> Looking forward to your next update - it is really fun to follow your progress!

This is getting exciting now that a couple sub-systems are starting to come together. I just finished moving everything from my electronics/assembly bench over to my usual programming workstation. It’s time to get this software doing more interesting things!

---

_[View the full topic](https://forums.kinograph.cc/t/the-reelslow8-film-scanner/2491)._
