Release notes
Videorc 0.9.82 Beta 1
Some of you have hit a state where, after the app has been open a while, the preview starts lagging and recordings come out choppy until a restart. This update makes Videorc detect and record that state the moment it starts, warns you when a recording likely contains frozen frames instead of staying silent, and fixes a camera startup error and a background logging loop found in the same investigation.
Videorc can now see its own slowdowns
- Videorc now monitors its own capture pipeline and records exactly when and where frame delivery degrades, instead of lagging silently until a restart.
- Recordings that likely contain frozen frames now raise a visible warning, even when the automated file check cannot finish.
- The post-recording quality check no longer gives up early on longer or 4K recordings.
- Cameras with fractional frame rates (29.97, 59.94) no longer hit a hidden error on every camera start.
Added
- Capture pipeline health monitoring. The compositor now watches its own frame-delivery rates continuously — idle, recording, and streaming — and writes a clear diagnostic the moment fresh-frame delivery collapses, naming the stage that degraded and when it recovered. The lag some of you have hit after long app uptime previously left no trace at all; from this version, one occurrence is enough to pin down where it starts.
Fixed
- Frozen recordings now warn you. When the live pipeline reports frozen output and the post-recording check cannot reach a verdict, Videorc now raises a warning on the recording instead of filing a silent internal note.
- The quality check finishes on real recordings. Its time budget now scales with the recording's length and resolution — a two-minute 4K file could previously time out unexamined every time.
- Fractional-rate cameras start cleanly. Cameras that advertise rates like 29.97 or 59.94 fps were asked for an impossible whole-number rate on every startup and rejected it internally. Videorc now requests the camera's own exact rate.
- A background error loop is gone. A leftover sign-in recovery file could make the app log the same error every five seconds for its entire run. The file is now cleaned up once and the loop is silenced.