Release notes
Videorc 0.9.73 Beta 1
A recording whose frames froze mid-session is now caught by the automatic quality check and flagged with a visible warning — previously a majority-frozen file could pass as "ready" because re-encoded held frames defeat exact-repeat detection. The recording pipeline also gains per-source freshness diagnostics (fresh vs held frame serves for screen and camera) in every support bundle and session accounting line, plus a new multi-session decay smoke gate, in direct pursuit of the "second recording lags" regression.
Frozen recordings can no longer hide
- Recordings with frozen frames are now flagged by the automatic quality check with a visible warning, instead of silently passing as "ready".
- The quality check listens to the recording pipeline's own counters, so a real freeze is never mistaken for you simply holding still.
- Every session now records how many frames each source delivered fresh versus held, in the session log and support bundles — the data that pinpoints where a laggy recording lost its frames.
Fixed
- The post-recording quality check now trusts the session's own pipeline counters: when the encoder bridge or compositor reported frozen output, freeze detection counts as a real defect even without exact decoded-frame repeats — the loophole that let a 55%-frozen recording pass as clean.
- Frozen-recording verdicts surface as a warning health event instead of passing silently.
Diagnostics
- Per-source freshness counters (fresh vs held serves, oldest served frame age) for screen and camera at the compositor choke point, included in diagnostics, the per-session frame-accounting line, and support bundles.
- New
smoke:session-decaygate records many identical sessions against one backend run and fails on any session that loses frame freshness.