Skip to content

Run the studio

The studio is krites' primary surface — a local, single-user web UI over a shoot.

First run

On a fresh install, run krites init once first (it writes your config). The packaged macOS launcher chains krites init && krites studio for you. See Getting started → First run.

Launch it

krites studio --shoot ~/Pictures/smith-wedding

krites starts a localhost-bound web server and prints the URL to open. By default it picks a free port; pin one with --port:

krites studio --shoot ~/Pictures/smith-wedding --port 8733

Run it from inside the shoot directory to drop --shoot.

Add a shoot from the studio

On the Shoots landing you can register a new shoot without a path by hand: hit Browse… to pick its folder of originals. On a desktop (macOS, or Linux with a display) that's your native OS folder chooser; over a headless/remote session it's an in-app folder browser that walks the server's directories. You can still type or paste an absolute path into the field.

What you can do there

  • Work the cull grid — confirm, override or reject verdicts across thousands of frames (it stays fast; previews are virtualised). It lays out as justified rows by default (uncropped frames, shot order kept); the Rows / Grid toggle switches to a dense uniform lattice and remembers your choice.
  • Inspect a frame in the loupe, straighten/crop/develop it, and remove objects. Hit Before / after to wipe a divider between the untouched original and your developed edits. The Faces strip shows a zoomed crop of every detected face with its eye state, ringing the ones that read as blinking — so you can see why a frame was flagged, not just read it. Hit Focus peaking (or press O) to glow the in-focus edges in green over the frame, so you can see at a glance which plane the cull judged sharp. The Why … panel is a reasons heatmap: each reason is a chip, and a face-bound one (a blink) drops a pin on the offending face — hover a chip to light its pin, or a pin to light its chip. Whole-frame reasons (soft focus, exposure) stay chips.
  • Hit lights-out (the Lights button, or press L) to dim the chrome and let the frames fill your attention; press L again to bring the lights back up.
  • Work in bulk — shift/⌘-click to select a range, then keep/maybe/reject or star-rate the whole selection at once. In the loupe, Select burst grabs every frame in a cluster so you can reject the also-rans in one go. A pace HUD in the footer tracks how many frames you've reviewed and your frames-per-hour.
  • Survey the bursts — a full-screen, one-cluster-at-a-time sweep where you crown each burst's keeper (click it or press its number) and its siblings drop to maybe. Skip moves on without deciding; Esc ends the survey.
  • Review your output — the Exported toggle flips the grid to the rendered files in export/ (click one to inspect it full-screen), so you can check the final deliverable without leaving the studio; toggle off to return to the cull.

Everything is non-destructive — edits are records, rendered only on export.

Notes

  • The studio binds to loopback only and uses per-launch authentication; it is single-user and not meant to be exposed to a network.
  • It reads and writes the same shoot files as the CLI, so you can move between them freely.

See the studio command reference for the full flag set.