Skip to content

Hard latency restriction for the PulseAudio backend. #170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

Hard latency restriction for the PulseAudio backend. #170

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
56f2269
Added the optional maxlatency argument to the member functions play, …
szlop Mar 21, 2023
cefc8fc
Added optional report_under_overflow argument to the player and play …
szlop Mar 21, 2023
f48e2da
Update README.rst
szlop Mar 21, 2023
6bc41dd
Reformated docstrings in pulseaudio.py to a length of 72 characters a…
szlop Apr 15, 2023
02022e6
- Fixed some typos in docstrings.
szlop Apr 15, 2023
3182f57
- Reformated pulseaudio.py to match PEP8 recommendations.
szlop Apr 15, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,13 @@ In order to request lower latencies, pass a ``blocksize`` to ``player`` or
try to honor your request as best it can. On Windows/WASAPI, setting
``exclusive_mode=True`` might help, too (this is currently experimental).

In Linux, it is possible to restrict the latency by setting the optional
parameter ``maxlatency``, which takes an integer number of samples. The setting
of this parameter limits the buffer size of the PulseAudio backend. If your
algorithm cannot keep up with the playback/recording, buffer underflows or overflows
will occur. Underflow and overflow events can be displayed by setting the optional
argument ``report_under_overflow`` to ``True``.

Another source of latency is in the ``record`` function, which buffers output up
to the requested ``numframes``. In general, for optimal latency, you should use
a ``numframes`` significantly lower than the ``blocksize`` above, maybe by a
Expand Down
Loading