gramps/LlamaCasty
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

feat(chroma): opt-in auto key, and alert clips key like any other clip

Browse Source 
TASK 64 slice F — the two things left after the feature worked by hand.

- App Settings → **Video clips → Auto Green/Blue Screen** (off by default). When on, a
  high-confidence detected screen is keyed as soon as the clip is added; the panel says
  "Removed automatically" so an automatic change is never silent. Medium confidence still
  asks, low says nothing — a wrong automatic key eats the picture.
- **A clip is a clip:** the alert box's own replacement clip keys through the same settings
  block (one alert box per layout, so its settings are the ones the next alert uses), and
  choosing an alert clip runs the same detector. The Green/Blue Screen panel now appears for
  a video layer *or* an alert box with a custom clip (`Source.ShowsChromaKey`).
- Spill ships as the creator-facing **Fringe** switch; nothing further to tune behind it.

Test: `ChromaKeyApplyTests` gains the auto-apply case (no click, still explicit in the panel)
and an alert-clip case (its pipe asks ffmpeg for colorkey+despill with the blue screen type).

Docs: TASK 64 complete in TASKS.md, known limits recorded in the task file, HANDOFF rewritten.
verify.sh: 546 passed, 0 failed, 0 warnings.
This commit is contained in:
gramps
2026-11-05 08:20:33 -08:00
parent ea24405ba2
commit 7bb1207fb2
12 changed files with 192 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
HANDOFF.md
+6 -6
View File
@@ -9,15 +9,15 @@
Sessions are keyed by **path + look**, so identical looks share one decoder.
- Detection stays silent on lawns/pitches (confidence = coverage × hue tightness) and ignores
letterbox bars. It never acts on its own.
- Tests: `ChromaKeyDetectorTests` (pure) + `ChromaKeyApplyTests` (pipe asks ffmpeg to key; offer →
accept → keyed session feeds the resolver; survives save). App build 0 warnings; full suite green
apart from the two documented pre-existing failures.
- Slice F shipped too: **App Settings → Video clips → "Auto Green/Blue Screen"** (off by default,
high confidence only, and the panel states when a key was automatic) and **alert clips** key through
the same settings block (one alert box per layout).
- Tests: `ChromaKeyDetectorTests` + `ChromaKeyApplyTests` (pipe asks ffmpeg to key; offer → accept →
keyed session feeds the resolver; survives save; auto-apply; alert clip keyed). App build 0 warnings.
## Next action
- TASK 64 slice F: the **"Auto Green/Blue Screen"** opt-in setting (App Settings, high confidence
only) and wiring alert clips to the same settings block.
- Then TASK 49 (chat profanity filter). Day 3's TASK 32/33 resilience slices remain outstanding —
- TASK 64 is complete. Next queued: TASK 49 (chat profanity filter). Day 3's TASK 32/33 resilience slices remain outstanding —
32·4 (fragmented MP4) is the smallest.
- Do not push absent a checkpoint request.