Window resize leaves stale pixels in accepted action cut; need manual clip rejection

Overview Files Skills Discover Packages Releases Dependencies Issues3 Breadcrumbs Pull Requests1 Activity

Closed general

John Lauer · 22d ago ·closed by John Lauer

Astra post-delivery framing review found a nonblank but invalid WGC clip after resizing the recorded KiCad window from 3840x2064 to 1920x1080. The smaller live frame appears over stale pixels from the old canvas. The flat-colour blank checker accepted it and generated a 14.5-second action cut. See the attached contact sheet.

Run: https://wiki.adom.inc/adom/adom-aiflow/files/docs/runs/source-unplaced-codex-astra-20260914-0314/README.md Clip: window-8062990-20260914-180222.mp4, nets-2, raw 754.4 s. AI Flow 0.1.15, ConfRoomROG AB 2.1.118, KiCad Bridge 1.0.11.

Workaround: stopped capture, fixed window at 1920x1080 before recording, hid the empty Properties panel via native menu, and returned to nets for a fresh take. The resize was my mistake; the recorder should recreate its frame pool on size changes or stop explicitly instead of silently preserving stale pixels. AI Flow also needs a command to mark a visually rejected nonblank clip suspect/discarded, preserving raw evidence and excluding it from compose. A capture mark records the rejection and retake reason. Original delivery times are preserved.

window-8062990-20260914-180222-sheet

1 Reply

John Lauer · 21d ago

Fixed in adom-aiflow 0.1.16 (insiders): capture reject <step>-<visit> --reason "..." marks a clip the blank check accepted but you would not (stale pixels after a resize, a covered canvas). It stays on the page as evidence with your reason and is left out of the video, the same as a suspect clip; the ledger records who rejected it and why. The blank check itself still reads the middle of the frame; a resize that leaves stale pixels around a live smaller frame is exactly the case that needs a pair of eyes on the contact sheet, which is why the sheet is printed at every clip stop.