LookingGlass/client
Chris Spencer 081a0a419d [client] audio: use actual device period if larger than expected maximum
This is rare and I'm not sure what causes it, but PipeWire sometimes uses a
larger period size than requested for no obvious reason (e.g., we could
request a period size of 512, but PipeWire uses 2048 anyway). This causes
us to stay in a permanent state of underrunning because the target latency
is too low.

With this change, we use the actual device period in the target latency
calculation if it is larger than the expected maximum. We may still get
some glitches at the beginning of playback (because the startup latency is
based upon the expected maximum period size), but it will recover after a
few seconds as it adjusts to the new target latency.
2022-11-01 08:02:37 +11:00
..
audiodevs [all] cmake: standardize indentation to 2 spaces 2022-05-29 11:16:16 +10:00
displayservers [client] wayland: fix attempt to confine when pointer is locked 2022-09-19 14:58:27 +10:00
include [client] displayservers: add name field 2022-07-13 07:05:07 +10:00
renderers [client] opengl: render cursor in spice mode 2022-09-19 14:58:47 +10:00
src [client] audio: use actual device period if larger than expected maximum 2022-11-01 08:02:37 +11:00
CMakeLists.txt [client] cmake: pass -Wstrict-prototypes for C files only 2022-05-29 11:16:16 +10:00
DEBUGGING.md [doc] Fix formatting 2018-05-23 08:46:03 +10:00