Our validator checked files, not frames — the first external user taught us the difference
说明与用途
auto‑xhs 验证器之前未检查帧级视觉缺陷。新增空帧、低比特率检查以及模板规则更新,现在会警告用户这些问题。
问题
The validator for auto‑xhs did not detect visual flaws in generated videos because it only inspected file metadata, not individual frames.
结果
After incorporating frame‑level checks and template rule changes, the validator now warns about blank frames, low bitrate, and overlapping cards, improving video quality detection without hard errors.
工作流
- Run auto‑xhs pipeline as released.
- Generate videos and observe visual flaws.
- Submit issue #1 with detailed description of flaws.
- Implement frame‑level blank‑frame check: sample frames every 0.5 s, shrink to grayscale, detect flat color, warn if two seconds of blank frames occur.
- Implement low‑bitrate check: warn if bitrate < 2000 kb/s.
- Adjust assembler bitrate settings: target 3 M, cap 4 M, remove conflicting -crf option.
- Update template rules to enforce one delayed entrance per area and use layout containers for overlapping cards.
- Run validator again to confirm warnings are issued.
- Review and merge user PRs first if they address these issues.
证据
The validator checked the file — duration, resolution, word counts, silence gaps — but never looked at a single frame.
Blank frames are now a check. Every 0.5 seconds we grab a frame, shrink it to a small grayscale image, and ask whether it is nearly one flat color.
Low bitrate is now a check. Below 2000 kb/s the validator warns.
The assembler got a bitrate floor: target 3M, cap 4M. A small trap here: we had -crf 21 and -b:v set together, and in that combination ffmpeg follows crf and the bitrate target is ignored. Dropping crf fixed it.
- 记录日期: 2026-10-18T05:41:36.475Z