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
2017-12-14 22:22:44 +11:00
2022-09-20 07:13:27 +10:00
2022-07-13 07:02:17 +10:00
2022-01-05 19:42:46 +11:00
2022-08-09 15:17:58 +10:00
2018-05-31 13:28:36 +10:00
2017-10-31 19:07:16 +11:00

Looking Glass

An extremely low latency KVMFR (KVM FrameRelay) implementation for guests with VGA PCI Passthrough.

Documentation

IMPORTANT

This project contains submodules that must be checked out if building from the git repository! If you are not a developer and just want to compile Looking Glass, please download the source archive from the website instead:

https://looking-glass.io/downloads

Source code for the documentation can be found in the /doc directory.

You may view this locally as HTML by running make html with python3-sphinx and python3-sphinx-rtd-theme installed.

Description
An extremely low latency KVMFR (KVM FrameRelay) implementation for guests with VGA PCI Passthrough.
Readme GPL-2.0 9.6 MiB
Languages
C 89.3%
C++ 7.1%
CMake 2.4%
NSIS 0.4%
GLSL 0.4%
Other 0.4%