[pulseaudio-discuss] [PATCH 0/3] Fighting rewinds
David Henningsson
david.henningsson at canonical.com
Fri Dec 10 05:57:51 PST 2010
[adding gstreamer-devel to the discussion]
On 2010-12-09 17:18, pl bossart wrote:
>> However, the problem is quite complex and there does not seem to be one
>> perfect fix, it's more of an optimisation problem. GStreamer in particular
>> sends out many small data packages, and PulseAudio does not handle that very
>> well.
>
> That's the default behavior, but you can cut the traffic by using the
> latency-time property in pulsesink. This makes sure you send bigger
> buffers, up to the 64k limit that PulseAudio has internally.
Thanks, that's good to know. Now, I'm just playing a simple audio file
with totem, so obviously we want high latency and large packet sizes,
but I'm not a gstreamer developer - do you have an idea of what can be
at fault here? Should totem specify a big packet size (regardless of
sink?), or can we just change the default packet size to something big
for people not requesting anything in particular?
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
More information about the pulseaudio-discuss
mailing list