Configure krites from the studio¶
Everything you'd otherwise set with krites config — the AI reviewer, the ONNX
models, and your default cull thresholds — is editable from the studio, and
changes apply without a restart.
Global settings — the gear on the shoots page¶
Click the ⚙ gear in the top bar (visible on the shoots list) to open Settings · all shoots. These apply to every shoot:
- Default cull profile — the thresholds new and un-customised shoots inherit (focus, exposure, dedup, blink, face size). This is your house style; tune it once here.
- Object removal — turn the inpaint eraser on, pick a backend (LaMa for
quality, MI-GAN for speed), and point it at your
libonnxruntime. Toggling it takes effect immediately — the Remove-object tool lights up without a reload. - Eye detection — turn the closed-eyes / blink model on and set its runtime.
- AI review — choose a provider (Gemini or Claude) and paste its API key. The key is stored in your OS keychain, never in the config file or logs.
Each section saves on its own. After a save the panel re-checks availability, so a capability you just enabled (object removal, AI review) becomes usable right away.
Some things are global-only
The AI provider + key and whether the ONNX models run are install-level choices — they're set only here, not per shoot. Only the cull thresholds can differ between shoots (below).
Per-shoot overrides — inherit by default, override on purpose¶
Inside a shoot, the ⚙ Profile button opens that shoot's Cull profile panel. Every control starts inherited — it shows the global value, disabled, with an override checkbox beside it:
- Tick the checkbox to override that threshold for this shoot; the slider activates and your value is saved as a shoot override.
- Untick it to drop the override and go back to the global value.
So a sweeping change — "I want all my shoots a little more forgiving on focus" — is one edit to the global default, and every shoot that hasn't overridden focus follows. A shoot you've deliberately tuned keeps its overrides.
Saving re-resolves that shoot's verdicts against the new thresholds, keeping any manual per-frame keep/reject decisions. Nothing here touches your originals.
Doing it from the CLI instead¶
The same values are plain config keys — see the configuration reference. A global default:
A per-shoot override is the same key in the shoot's own config
(<shoot>/.krites/config.yaml). The studio is just a friendlier front end over
the same cascade.