Commit Graph

20 Commits

Author SHA1 Message Date
Melbar 5a6ae2175c Slim README, move algorithm prose to docs, add stills + per-fps TC to cutter report
README: 550 -> 308 lines. The dense algorithm prose was moved verbatim to
docs/ALGORITHM.md and replaced in the README with a compact "Wenn ein Match
falsch wirkt" troubleshooting table and a link. The cutter-facing intro
points at the new in-report stills instead of the old HTML report.

Cutter report:
- Per-side frame rates: trailer timecodes use the trailer file's fps
  (typically 25), source timecodes use the source file's fps. ffprobe is
  used to detect each side; falls back to edl_frame_rate if unavailable.
- Side-by-side trailer/source preview stills extracted via ffmpeg, taken
  ~30% into the beat / match window. Stored under output/cutter_stills/
  (gitignored). Re-rendered only when the underlying video is newer than
  the cached jpg.
- Compact table at the top, detailed per-beat sections below with the
  stills inline so the cutter can sight-check phase agreement directly.
- New --no-stills flag for fast text-only regeneration.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-04 13:24:19 +02:00
Melbar 97a8f9e305 Add cutter report and auto-regen on each match
- New CUTTER_REPORT.md: per-beat hand-off table for the video editor doing
  the manual recut. Per beat: trailer SMPTE in/out, source SMPTE in/out,
  scene id, score, status (OK / ? / MAN.), and a one-line phase
  description from the cached vision text.
- New scripts/generate_cutter_report.py: pure renderer that reads the
  current cache (match_results.json + trailer_beats.json + optional
  vision_descriptions.json) and writes CUTTER_REPORT.md. No side effects on
  the cache.
- cli.py: after every successful match the cutter report is regenerated
  automatically (best-effort; failures are logged and do not abort).
- README.md: new top-section "Fuer den Cutter" describing exactly what the
  editor needs (which two files to look at, how the status flag works,
  the recommended NLE workflow). The technical algorithm description
  follows below.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-04 13:09:16 +02:00
Melbar 06a2326bf1 Broaden phase realign and add unmatched-beat recovery
- Phase realign for matched results: drop the "long scene" gate (>1.6x
  segment, >=6s) in favor of "scene has any meaningful slack beyond the
  segment". Already-confirmed segments in tight scenes are still skipped to
  protect strong matches. A repair is only committed if the new score is
  not meaningfully worse than the original (>=score-0.02).

- Recovery stage for unmatched beats: vibe-check (CV) feeds top-K candidate
  scenes into the semantic action-window search; CV alignment + vision phase
  validate gate decide whether the candidate becomes a provisional match.
  Beats without scoreable visual content (logos, title cards, full fades)
  remain unmatched by design.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-04 07:12:20 +02:00
Melbar 7b4a98d760 Match segment window by its own action phase
For segmented beats, the repair stage now searches for the source action
window using the segment's own description first; the full beat context is
used only as a fallback or when it scores noticeably higher. The trailer-
offset shift is applied only when the beat context is actually chosen.

Also harden vision-call retries to catch read-side network errors
(TimeoutError, socket.timeout, ConnectionError, OSError) and wrap the
filter/repair loop so a transient vision failure preserves the previously
cached match instead of dropping it.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-03 06:22:12 +02:00
Melbar 2cc05e4737 Trim retimed segments when phase drifts 2026-05-02 23:04:41 +02:00
Melbar e293835a86 Use beat context for segmented action retiming 2026-05-02 21:58:35 +02:00
Melbar 8415516f89 Retiming long scene matches by action phase 2026-05-02 20:47:59 +02:00
Melbar 252f710396 Rank long-scene probes without action penalty 2026-05-02 18:53:27 +02:00
Melbar 2d9ba91a7b Probe broader long-scene action windows 2026-05-02 18:25:16 +02:00
Melbar a5a84a9145 Use motion phase for in-scene timing 2026-05-02 17:59:18 +02:00
Melbar 3ea5582b49 Realign wrong in-scene action matches 2026-05-02 17:13:22 +02:00
Melbar 1a177d6b89 Reject vision matches with action phase mismatches 2026-05-02 16:49:47 +02:00
Melbar d9e470c877 Improve vision matching for dissolve-heavy beats 2026-05-02 16:15:51 +02:00
Melbar 858a814db1 Normalize segmented cache coverage 2026-05-02 14:11:27 +02:00
Melbar e6bd0faf03 Improve segmented vision matching quality 2026-05-02 13:49:16 +02:00
Melbar 884a0d4232 Add vision prepass for targeted matches 2026-05-02 13:03:15 +02:00
Melbar f1173eacee Add segmented fallback for unmatched beats 2026-05-02 11:46:33 +02:00
Melbar 535176c144 Lower provisional review threshold 2026-05-02 10:09:30 +02:00
Melbar e4dd0a77b2 Document multi-segment trailer beat matching 2026-05-02 09:18:46 +02:00
Melbar 8e1bcf142f Initial project import 2026-05-02 09:07:41 +02:00