Bug 59267

Summary:	network playback choppy for some clients when streaming via mDNS tunnel
Product:	PulseAudio	Reporter:	jrollins
Component:	core	Assignee:	pulseaudio-bugs
Status:	RESOLVED MOVED	QA Contact:	pulseaudio-bugs
Severity:	normal
Priority:	medium	CC:	astrand, lennart
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description jrollins 2013-01-12 02:12:18 UTC

The problem occurs for some clients and not others, and goes away entirely if a direct connection is used (by setting PULSE_SERVER or pax11publish).  This happens primarily iceweasel (firefox).

I found that if I switch the sink back and forth between the local and remote server I can eventually get the choppiness to go away.  If I pause the audio at the source the choppiness returns.

ohsix on the #pulseaudio channel suggested I look at the sink latency with "pacmd list-sinks".  In either case, either when playback is good or when choppy, the "current latency" reported by the remote sink is absurdly high.  For instance:

current latency: 5515241.32 ms

I can guarantee I'm not actually seeing a 1.5 hour latency.  (Maybe this is a red herring, but if it is it probably indicates a bug in it's own right.)

Please let me know if there's any further information I can provide.

The local and remote servers are both version 2.0-6 from Debian wheezy.

Thanks for the help, and for such a great piece of software.

Comment 1 GitLab Migration User 2018-07-30 09:34:58 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/32.

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.