Repository navigation
Vision OCR 1.12.0 — big scans come out small again
A 568-page library scan went in at 31 MB and came out at 437 MB. It now comes out at 35 MB, with exactly the same text.
| size | |
|---|---|
| the original scan | 31 MB |
| 1.11.0 | 437 MB (14.0x) |
| 1.12.0 | 35 MB (1.13x) |
Two things were wrong, and the second was the interesting one.
Colour pages could not be stored in layers. Pages that mix text with a picture are normally split into a sharp 1-bit layer for the text and a compressed one for the picture — but colour pages were the single kind that could not be, so a scan the app read as coloured throughout kept every page as one full-resolution colour photograph of itself. 669 KB a page where three layers cost 110.
And even layered, the layers were far more detailed than paper needs. The 1-bit layer carrying the text already matched the Internet Archive's own scan of the same book to within 2%. The other layers cost 40.7 MB against their 4.3. Pages whose ink is all text now store their paper far more coarsely — and the app works that out per page, so there is nothing to set and nothing to think about. A page carrying a picture is left exactly as it was.
On the 232-document test corpus: 721 MB against 792, every document either smaller or byte-for-byte identical, not one larger, and the recognised text unmoved. Every photograph-heavy book in it came out identical to the byte. Scans of faint typescripts and manuscripts — the ones this app was mistaking for photographs — came down hardest: one 1941 speech to a fifth of its size.
If you keep Settings ▸ Photo detail at Maximum, nothing about your photographs changes at all; that setting is now honoured in full.
Also fixed: the updates section of Settings appeared twice, and the Start from preset buttons gave no sign they had done anything — they now say what changed, and say so out loud for VoiceOver instead of hiding it in a tooltip you need a mouse to find.
Requires macOS 13 or later. Unsigned by choice: System Settings ▸ Privacy & Security ▸ Open Anyway after the first launch attempt.
Every defect above is written up with its evidence in BUGS.md — R49 through R53, including a fix that was built, measured and refused, and three defects found by reviewing this release's own code before it shipped.
Known, and found after this release went out
Two ways Automatic can route a page wrongly were found on 2026-08-13 while measuring something else, and both lose what is on the page rather than merely degrading it. Neither is caused by anything in 1.12.0 — both are in 1.11.0 and earlier too.
- A pale drawing can be erased. Faded ink, light pencil, a pale wash: if a mark is too light to count as ink and too light to count as continuous tone, the page is treated as plain text and the mark is rendered as blank paper. The text beside it is unaffected, which is what makes the result look fine.
- A continuous-tone plate covering roughly a fifth of a page can come out solid black, taking the line of text above it with it.
If a document matters and carries pale artwork, compare the output against the original — or use Grayscale, which sends nothing down the 1-bit route and cannot do either of these things.
Both are written up with rendered before-and-after evidence as R56 and R57 in BUGS.md, including a luminance-based fix that was built, measured over four rounds and refused — the blind zone turns out to hold pale drawings you want kept, decorative shading you do not mind losing, and show-through from the back of the sheet you actively want gone, and no brightness test separates those three.