Same-day selects for wedding and event shooters

Ceremony at two, dinner at seven, and a same-day edit expected on the ballroom screen before the last dance. Nobody blows that deadline by cutting too slowly. They blow it at eight-forty, still hunting the ring exchange across six cards and three hundred clips while the DJ asks for an ETA. The same-day edit is a finding problem wearing an editing costume, and finding problems get solved before dinner or not at all. Here is the day that works.

The clock starts when the cards do

Weddings are the genre with no second take, so offload discipline is not negotiable: checksums on both ends, an ASC-MHL manifest, and no card called safe until two destinations hold verified copies. Offload between events, not at the end of the night; the run you start after cake finishes after midnight, and midnight is when you need selects on a screen, not a progress bar. Run the cards through ClipLogger and it also refuses to re-copy a card it already knows, which matters at five o'clock when nobody can remember whether the cocktail-hour card went in before or after family formals. The tile says already ingested, and you move on. None of this is the glamorous part. It is the part that buys the calm for everything after, because a shooter who is not certain the vows are safe cannot think clearly about selects, and the couple only gets one set of vows.

Decide the vocabulary at breakfast

The cheapest speed you will buy all day costs nothing and works on paper. Agree the moment list before the ceremony, short and closed: prep, ceremony, ring, kiss, cocktail, speeches, first-dance, party. Agree what a flag means: usable, not perfect, because perfect is a debate and usable is a decision. If there is a second shooter, they get the same list spelled the same way, since "reception candids" and "party" must not fork into two categories somebody reconciles at nine. Then mark takes at the moment of offload, while you still know which card held the vows and which speech ran long. Whether the marks land in an app, a camera report, or Sharpie on card cases matters less than that they land the same day, in the same words. A closed vocabulary decided at breakfast beats a clever one invented at night, and at a wedding, night is exactly when you will have no time to be clever.

Run the pass during dinner

Dinner is forty-five minutes when nothing needs shooting, and that is when the batch runs. Prepare pushes the day's clips through an AI pass against my own fields. The local engine costs nothing and frames never leave the Mac, which is the right default. When the clock is tight I use Rush instead: the batch fans out to parallel cloud workers on larger models, comes back faster, and reads the hard frames (dim church, backlit toasts) better. The pricing takes no thought at seven in the evening, which is the point of flat pricing: one credit per clip, and the cost shows before anything runs, so a three-hundred-clip day reads 300 clips, 300 credits, decide. Either way the results land identically: as suggestions, pending, waiting on a human. I confirm between courses, Return to accept, a keystroke per field, and by the toasts the day is described: moments filled, people linked, junk flagged. The model did the typing. The decisions stayed mine, which is why I will trust the filters in an hour.

Filter to the first dance

With confirmed fields, the hunt is over before it starts. Filter the moment field to first-dance, add the flag, sort by the quality score, and the grid is the shortlist. Stack in who is in frame when the couple's entrance matters more than the uncles', since confirmed subjects filter like any other value. String-out the shortlist to watch it in order, top to bottom, one scrub bar, and pull the keepers. Then export to FCPXML and cut the actual piece in the NLE, which is where cutting belongs; ClipLogger organizes and hands off, and the handoff is the product. The edit that gets applause at ten was findable at five past eight. The applause is for the finding; the cutting was twenty minutes of work that finally had room to happen.

The second shooter's cards, no meeting required

Folding in a second shooter used to be a conversation: what did you shoot, where are the speeches, which card has the processional. Skip it. Their cards go through the same verified offload, their clips take the same AI pass against the same fields, and everything lands in one review under one vocabulary, which is why breakfast mattered. If they logged on their own machine, better still: the metadata rides in sidecars beside their files, so a folder handed over on a drive arrives already described, nothing reprocessed, and the content key re-attaches everything even if files were renamed in transit. Markers carry an author stamp, so whose note is whose stays obvious when there are two of you working the same day. The wedding stops being my folder plus their folder and becomes one searchable day, which is the only shape a same-day deadline can afford.

Same-day selects are decided at breakfast and found at dinner; the cutting was never the hard part.