[pulseaudio-tickets] [Bug 90210] Pulse audio NOT USED multithreading
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed May 6 03:06:12 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=90210
--- Comment #13 from Tanu Kaskinen <tanuk at iki.fi> ---
(In reply to Alessandro Ferri from comment #10)
> > Step 1: Install the speex development headers (on Raspbian they're in
> > package libspeex-dev)
> >
> > Step 2: Run the configure script again, and build as usual.
> >
> > By the way, the parameters that you currently give to configure look
> > strange: what purpose do "--disable-rpath" and
> > "--with-module-dir=/usr/lib/pulse/modules" serve?
>
>
> Thanks for the info,
> the next few days I will try to configure Pulseuadio with speex.
> About the two configuration parameters, I did not place a lot of problems, I
> repeated what I found in the post of raspberry Pi forum with some of my
> personal adjustment, I'll carry the link, at the bottom there is the guide
> to install pulseaudio 5.0:
>
> https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=87138
>
> At this point, you know what are those two parameters, since I do not know?
"RPATH" is an attribute stored in shared libraries that tells the dynamic
linker what directories to search for the dependencies of the shared libraries,
in addition to the default directories. I don't know why anyone would want to
disable it. In my experience RPATH is necessary for some of the modules (such
as the alsa modules) to work, because they depend on libraries in a
non-standard location. Apparently my understanding of this thing is not
perfect, since modules seem to be loading fine on your system despite
--disable-rpath.
--with-module-dir just sets the module directory to something else than the
default. Setting it to /usr/lib/pulse/modules does no particular harm (other
than making your setup non-standard, and therefore potentially harder to
debug), but there's no reason to set that option, as far as I can see.
By the way, something that I missed earlier: you set --prefix to /usr, which is
something that you should never do. When you use /usr as the prefix, you
overwrite the files that are managed by the distribution's package manager, and
if you ever update the distribution's version of pulseaudio, the package
manager will then overwrite the files that you installed from source. Using
/usr as the prefix is a good way to mess up your system. You don't need to set
prefix, the default prefix (/usr/local) works just fine.
> I have connected the speakers to the raspberry, using HiFiBerry AMP. I play
> music from my iPad to raspberry Pi2, via Bluetooth and also via WiFi. In
> this latest case I use shairport connected to pulseaudio.
> When I play music, with resample-method = ffmpeg, via wifi (with shairport +
> pulseaudio) from my iPad to raspberry, I not have issues and I listen music
> really well, when instead I play music, with resample-method = ffmpeg, via
> Bluetooth from my iPad to raspberry, I do not hear any music and some times
> from the speakers comes a sound like "grrrrr" or "pzzzz". So it seems that
> with the Bluetooth the resample method = ffmpeg is not working. I attacked
> both my daemon.conf that system.pa
The resampler is not a likely cause of corrupted audio. What if you record
audio from the a2dp source with this command:
parecord --device=SOURCE --fix-rate --fix-channels --fix-format >
~/test.wav
Does that file contain corrupted audio too? If it does, then there's something
wrong in the bluetooth source.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/pulseaudio-bugs/attachments/20150506/b6088f22/attachment.html>
More information about the pulseaudio-bugs
mailing list