DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to pick the best frames and match exposure across a shoot with Rembrandt

Keep the sharpest frames and make the rest of the shoot look consistent in one pass.

  • Content
  • Intermediate
  • 45 minutes
  • From the README
  • Any agent

Who it is forA wedding, event or product photographer with hundreds of burst frames who needs a clean, consistent set quickly.

The problemSorting bursts and matching exposure and white balance across a shoot by hand is slow and inconsistent.

The outcomeEach burst has one sharpest frame with open eyes selected, the other frames are flagged as rejected, and the rest of the shoot is matched to a hero frame.

What you need first

  • A computer running macOS, Windows or Linux with a photo folder you want to edit
  • A terminal for the Linux and self-host install commands
  • A GPU with WebGL 2 support is helpful; the README says older graphics cards are supported at reduced working size
  • Permission to open unsigned builds (System Settings › Privacy & Security › Open Anyway on macOS, More info › Run anyway on Windows)

Steps

  1. Open the folder of the shoot in Rembrandt's library.
  2. Select the shoot and run Pick the best. Your own flags are kept and one Undo reverts the whole action.
  3. Review the picks in Compare (C), which shows 2 to 4 frames side by side with zoom and pan linked.
  4. Select the shoot again, choose a hero frame, and run Make these consistent so exposure and white balance match the hero.
  5. Check a few matched frames against the hero to confirm the results look right.

Prompt for your agent

Using the repo thesnarkitecht/rembrandt, run Pick the best on the shoot at <folder-path> and then Make these consistent using <hero-frame-name> as the hero. Report how many frames were picked and rejected, and check that your own flags were kept.

Caveat. The README describes the picks as the sharpest frame with open eyes in each burst, so review them before final export.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page