Repository navigation
Recording (Linux): keep the capture clock ticking while cursor messages flow #936
Description
Part of #920 (rank 19). Effort S, risk low.
Problem
- The Linux helper's main loop advances the capture clock (
capture.advance(), which holds the last picture forward and drains audio) only onFrameReadyand onrecv_timeoutexpiring (pipewire-capture/src/main.rs). - Every other message resets the
recv_timeout. Cursor messages arrive at the compositor's rate (up to 144/s) while the mouse moves, so on a static screen with a moving mouse the timeout never expires and nothing advances. - Hypothesis on the consequence: the 2 s audio ring saturates and silence is inserted; the video holds no frames for that span.
Proposal
- Advance whenever a tick has elapsed since the last advance, whatever message woke the loop.
Verify
- A unit test on the tick rule.
- On Linux: static screen, mouse moving for 10 s, with sound: no
audio-droppedwarning, audio continuous.
Activity
github-actions commentedon Sep 30, 2026
Fixed by #940 and merged into
main.This change is assigned to the
Next Releaserelease milestone and is not necessarily available in the latest downloadable desktop release yet. It is currently marked asstatus: pending releaseuntil a packaged release containing it is published.EtienneLescot commentedon Sep 30, 2026
Moved into
v2.0.0as part of the pre-release cut.fix(linux): keep the capture clock ticking while cursor messages flow