xiayeandClaude Opus 4.6 ee4c00db6a fix(engine): cross-check nb_frames when video stream duration is absent ...

When ffprobe omits the video stream's own `duration` field,
`extractMediaMetadata` falls back to the container duration
(`format.duration`), which includes the longest stream in the
container. Stock and looping clips commonly have an audio track
2x the video length, inflating `videoStreamDurationSeconds` and
causing the downstream coverage gate to expect twice the frames
FFmpeg can actually produce — the "50% cluster" failure pattern.

Cross-check with `nb_frames / fps` when the stream duration is
absent. If the frame-derived duration is >10% shorter than the
container, use it instead. This corrects the inflation at probe
time without requiring a second ffprobe pass.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-09-23 15:37:35 -07:00

..

services

fix(cli): stopping the preview server no longer leaves a Chrome running (#4183)

2026-09-22 22:49:44 -04:00

utils

fix(engine): cross-check nb_frames when video stream duration is absent

2026-09-23 15:37:35 -07:00

cdp-headless-experimental.d.ts

initial code (#2)

2026-03-21 22:43:56 -07:00

config.test.ts

fix(cli): macOS 12 users get Chrome 150 automatically and can render (#4185)

2026-09-19 18:08:29 -04:00

config.ts

fix(cli): macOS 12 users get Chrome 150 automatically and can render (#4185)

2026-09-19 18:08:29 -04:00

index.ts

fix(cli): stopping the preview server no longer leaves a Chrome running (#4183)

2026-09-22 22:49:44 -04:00

types.ts

feat(engine): sample Chrome process memory per capture session

2026-09-18 20:52:03 -07:00