Bug 75470 - CoreAudio Device latency configuration
Summary: CoreAudio Device latency configuration
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: modules (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Mac OS X (All)
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-24 21:35 UTC by Patrik Oldsberg
Modified: 2018-07-30 10:32 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Patrik Oldsberg 2014-02-24 21:35:23 UTC
I have been looking into the high latency when using PulseAudio as input and output on OS X with CoreAudio.
It seems like the default fixed latency of 250ms is used, which ends up being a total latency of 500ms. I tried lowering the latency using PULSE_LATENCY_MSEC but this seems to have no effect. It is however possible to increase the latency using this method.
I noticed that setting the PA_SINK_DYNAMIC_LATENCY and PA_SOURCE_DYNAMIC_LATENCY flags in module-coreaudio-device.c will reduce the latency to about 10ms. Perhaps there should be a way to enable dynamic latency, as this seems to reduce the latency by a significant amount.
Or perhaps there is a reason to not use dynamic latency that I am unaware of?
Comment 1 Tanu Kaskinen 2014-03-07 13:48:47 UTC
Implementing dynamic latency with CoreAudio would be good, but I believe doing it correctly would require more than just setting the DYNAMIC_LATENCY flag.
Comment 2 GitLab Migration User 2018-07-30 10:32:02 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/492.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.