Bug 93515 - Native TCP Audio garbled when daemon runs as root on Raspberry Pi. Works as non root (Pulse 7.1)
Summary: Native TCP Audio garbled when daemon runs as root on Raspberry Pi. Works as n...
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: daemon (show other bugs)
Version: unspecified
Hardware: ARM Linux (All)
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-27 09:56 UTC by Jessy Exum
Modified: 2018-07-30 10:24 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Audio samples played through both servers, config files, and logs. (2.27 MB, text/plain)
2015-12-27 09:56 UTC, Jessy Exum
Details

Description Jessy Exum 2015-12-27 09:56:49 UTC
Created attachment 120708 [details]
Audio samples played through both servers, config files, and logs.

On a fresh install of raspbian lite (no X) running on a new Raspberry Pi 2B (happened on an Pi 1B too, but data here is for 2B), the pulseaudio daemon garbles data via the native TCP plugin. This issue has been happening to me since version 6.x.

Repeat steps:
* Get Pi 2B (maybe other models too).
* Attach speakers and ethernet to the Pi.
* Install Raspbian lite.
* Install prerequisites for pulse (my configure log is in the attached archive).
* make && sudo make install
* Add the following to /usr/local/etc/pulse/default.pa :
    load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;{your subnets address}/24 auth-anonymous=1
    load-module module-zeroconf-publish
* Edit /usr/local/etc/pulse/daemon.conf to set:
    exit-idle-time = -1
* Run:
    export LD_LIBRARY_PATH=/usr/local/lib 
  Or set the variable for every pulseaudio call, or put the export in bashrc.
* As the 'pi' user, run:
    pulseaudio -vvvvvvvvvvv
(pulseaudio should start fine, speakers should hiss for a few seconds, then fall quiet)
* Optionally test that loading the sine module produces a tone.
* On your computer (or the pi if you want), run:
    paplay --server={Pi's IP} {Some wav file, ideally a song}
(Assuming your network is fast enough the audio should start up, and play fine. Listen to pa_test_good.mp3).
* Kill the pulse server.
* As the 'pi' user, run:
    sudo pulseaudio -vvvvvvvvvvv
(pulseaudio should start fine, speakers should hiss for a few seconds, then fall quiet)
* Optionally test that loading the sine module produces a tone.
* On your computer (or the pi if you want), run:
    paplay --server={Pi's IP} {Some wav file, ideally a song}
(Everything is awful. Listen to pa_test_broke.mp3).
Comment 1 GitLab Migration User 2018-07-30 10:24:07 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/396.


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.