Bug 44806 - Local PulseAudio->remove PulseAudio tunneling does not work as well as PULSE_SERVER
Summary: Local PulseAudio->remove PulseAudio tunneling does not work as well as PULSE_...
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: misc (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-15 07:36 UTC by Elias Naur
Modified: 2018-07-30 10:21 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Elias Naur 2012-01-15 07:36:55 UTC
I have a Pulseaudio networked sound setup, where one laptop is connected to my HiFi through a mini-jack, and have pulseaudio configured to export the local sound device, while another laptop is configured to access the remote sound device for audio playback. It's a very nice and convenient setup, except that buffer underruns frequently occur, resulting in really annoying fallouts in the sound.

Using

PULSE_SERVER=<hifi-laptop> <audio-player>

works almost perfectly in terms of almost no underruns but this is an ugly workaround and I'd like to keep the ability to dynamically switch between laptop speakers and the stereo.

Is there a workaround or config I can tweak to increase buffering and/or debug what the problem is?
Comment 1 Colin Guthrie 2012-03-13 18:01:40 UTC
This is just simply that the tunnelling code is not a good as the direct connection. It really needs a bit of love and attention to make it more awesome.
Comment 2 GitLab Migration User 2018-07-30 10:21:04 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/366.


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.