Skip to content

· #article · #project · #photo

Copying only what's new

Why I wrote a small macOS app to get photos off a camera card, and what "already imported" should mean.

My originals live in plain dated folders, and editing happens in DxO PhotoLab. The weak step was getting photos off the card. Catalog apps want to own the library, and copying by hand means guessing which files on the card are new.

So I wrote Corvus, a small native macOS app that does only that step. It started as Andermic Photo Importer and was renamed when it joined my other Senex apps. Insert a card and it scans in the background. New photos are already selected in the grid, and nothing is copied until you click Import. Each photo lands in a Year/Month/Day folder for the day the camera recorded it, so a card that spans a week sorts itself. There’s no account, no cloud service and no photo library database.

What “already imported” means

A photo counts as imported only when a file with identical contents already exists somewhere under the destination, even if it was renamed. File size and small samples narrow down the candidates, but only the contents decide. Import reports are never treated as proof. The one catch is an original whose metadata another app edited. Its contents changed, so it shows up as new.

Copies you can trust

Every copy is staged, flushed, read back, verified, published without overwriting anything, and verified again before the card can be ejected. If an import stops partway, the verified copies stay, the half-finished staging files are removed and the card stays mounted. Files on the card are never changed or deleted.

The source is public on GitHub under the MIT license. It’s a preview you build yourself with ./build.sh, while I finish testing it with real cards and cameras.

What’s the step in your photo workflow you still do by hand?