# Scanning single row of pixels using picamera HQ? **URL:** \ **Category:** Software\ **Created:** [January 4, 2024, 1:48am UTC](https://forums.kinograph.cc/t/scanning-single-row-of-pixels-using-picamera-hq/2686 "2024-01-04T01:48:38Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![friolator](https://forums.kinograph.cc/user_avatar/forums.kinograph.cc/friolator/32/2747_2.png) [@friolator](https://forums.kinograph.cc/u/friolator)\ **Post date:** [January 8, 2024, 5:16pm UTC](https://forums.kinograph.cc/t/scanning-single-row-of-pixels-using-picamera-hq/2686/7 "2024-01-08T17:16:26Z")
continuous motion with a line scanner is problematic when there are splices. The result is a kind of warping at the splice. This is a common problem with all the line-scan based machines like the Spirit, Shadow, Scanity, GoldenEye. In fact, it’s so bad in the GoldenEye that DigitalVision includes a copy of their restoration tools with a plugin that fixes splice bumps in software. Kind of crazy. And as someone mentioned above, no possibility of multiple exposures per frame. The Northlight used a different approach: the film is moved into a gate and held firmly in position, then the whole gate is moved past a line sensor. This eliminates the splice bumping that you get with continuous motion, but it’s a much slower process. That particular scanner took seconds per frame, even the faster Northlight 2 model. Great scanner, beautiful piece of hardware, but painfully slow. Modern hardware could probably be made to run faster but there’s a lot of extra engineering that goes into that. A camera with a rolling shutter kind of works like this though, it’s just all done in the camera. We use one on [Sasquatch](https://forums.kinograph.cc/t/sasquatch-70mm-scanner/1631) (film held still then separate red, green, blue images are taken of that frame and processed in software into a color image). --- _[View the full topic](https://forums.kinograph.cc/t/scanning-single-row-of-pixels-using-picamera-hq/2686)._