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.

Источник