Cull while the card copies: the twenty minutes you already spend

Every wedding night has one wait nobody argues with: the card copying to two drives. Twenty minutes, sometimes forty, of watching a progress bar. A culler that does its work inside that window costs you nothing on the clock, because the clock was already running. This is how that timing works and how to set the night up so it happens every time.

Where the gap comes from

During a card copy the bottleneck is the card reader and the drives, not the processor. Bytes move at a couple of hundred megabytes a second and the Mac's Neural Engine, GPU and performance cores sit almost idle. That idle capacity is enough to look at every frame as it lands, if the software is written to work in the gaps instead of fighting the copy for the disk.

Kepla is written that way. On the reference wedding, the copy of 4,812 frames to two drives at 214 MB a second took 24 minutes 10 seconds. The cull took 4 minutes 22 seconds inside it and finished 19 minutes 48 seconds before the copy did. The drive was the only thing anyone waited for.

Tools that decode the RAW cannot do this

A culler that decodes every RAW in full has to read each file twice: once for the copy, once for itself, and the second read competes with the first. That is why a full decode tool lands at 25 to 60 minutes on a shoot this size, and why it feels slower when you run it at the same time as an import. It is not slower at thinking. It is waiting for the disk.

Reading the JPEG the camera embedded in each RAW is a fraction of the bytes, so it fits in the idle moments without slowing the copy down. The real RAW is opened only where the JPEG cannot settle the answer: 214 frames out of 4,812 on the reference wedding.

A wedding evening on one Mac

1. Card in, copy starts. Two drives, the way you already do it. Nothing changes here.
2. Open Kepla. No setup, no profile, no questions. It reads the card and starts on frame one.
3. Sorting finishes before the copy. On the reference wedding that is a twenty minute head start. The clean count, the cleared count and the uncertain count are already on screen.
4. Answer the uncertain frames. 96 on this wedding, one key each. Blur that might be deliberate is yours to call.
5. Heart favourites, if you want to tonight. Kepla groups the clean frames into moments and asks for one favourite each. Leaving a moment empty is a real answer.
6. Open Lightroom Classic tomorrow. The sidecars are already beside the files. The plugin rebuilds your moments as collections and favourites arrive as five stars and a red label.

What it costs the machine

The reference wedding ran on a MacBook Pro M3 Max on battery at 21 W, sixty four frames at a time on the Neural Engine and GPU. That matters at a venue: the cull happens at the reception table, off the venue's wifi and off the venue's power, and the laptop is still charged when you leave.

The promise attached to a founding place is built on exactly this timing. If sorting does not finish before your card copy does, on your Mac, on battery, you owe nothing. That is the one number the whole app is built to win.

Three habits that make the window bigger

• Copy to two drives at once. The copy is the window. Two destinations takes no longer than one on a decent reader, and it is the backup you should be making anyway.
• Keep the sidecars with the copies. Kepla writes XMP beside the files on your drive, never to the card. Move the folder and the decisions move with it.
• Do the uncertain frames while the copy finishes. Ninety six key presses fits inside a twenty minute head start with time to spare.

Kepla for Mac is free through the private preview and the first hundred photographers keep it at $99 a year. Request Founding Access.

FAQ