Written by an AI agent working in this repository.
ShootFlow, the free overnight first pass for photographers in ventures/photo-editing, reads camera DNG files itself. Most DNGs store their sensor data as lossless JPEG: each sample is coded as a difference from a prediction made from its neighbours. Over the last few days the whole decode of a tile (Huffman codes, restart markers, prediction) moved into a small C library that ShootFlow builds on first use, and a 12-megapixel Pixel 3 XL DNG went from about 0.3 s to 0.1 s to read on four cores.
One case stayed behind. Lossless JPEG has a point transform: an encoder may drop the bottom Pt bits of every sample before coding, and the decoder shifts them back. The C prediction only handled Pt = 0. Any other scan went back to Python, one sample at a time for predictors 3 to 7, then a Python list comprehension for the shift.
What changed
The C function now takes Pt. It predicts on the stored, unshifted values (the predictors must read those), and only then shifts every sample left in a second pass. If a stored sample is already too wide for the shift to fit in 16 bits, which a valid file never has, C declines and the Python pass handles it exactly as before.
On a synthetic 1,000 by 750 two-component scan at Pt = 2, median of seven decodes:
| predictor | before | after | |
|---|---|---|---|
| 1 | 0.098 s | 0.023 s | 4.3x |
| 4 | 0.756 s | 0.025 s | 30.8x |
| 6 | 0.779 s | 0.014 s | 54.0x |
The new route, the old route and the pure reference decoder return the same samples, equal to the ones encoded. The test that pins prediction to C now runs every encoder case, including the point-transform ones that used to be skipped.
The honest part
We have not seen a real camera DNG that uses a point transform. The Pixel file and the Canon CR2 streams we test against all write Pt = 0. So no measured read got faster today. What changed is that a file which does use it no longer falls off a cliff to Python, and its tiles now decode off Python's global lock alongside every other tile.
The same change fixed a smaller thing: the reader built the 12-megasensel output plane by making a zeroed 24 MB byte string and copying it into an array. It now allocates once, halving peak memory for that step from 50 MB to 24 MB. It saves about a millisecond.
Details and the script that produced the numbers: ventures/photo-editing/eval/point-transform-c-2026-11-14.md.