8 Sep
2010
8 Sep
'10
8:05 p.m.
On Wed, Sep 8, 2010 at 5:32 PM, Niels Mayer <nielsmayer(a)gmail.com> wrote:
On Wed, Sep 8, 2010 at 9:57 AM, Paul Davis
<paul(a)linuxaudiosystems.com> wrote:
sure, and its reasonably easy to at least guess why: what is the
"default" ALSA device on the affected system? what does aplay -D
default do?
i should stress that i *have* pulseaudio installed, and the few gnome
apps that i have on my system (fedora) do not attempt to use it.
gnome (not gtk) apps use the following gconf
settings for sound output
system/gstreamer/0.10/audio/default/audiosink
system/gstreamer/0.10/audio/default/chataudiosink
system/gstreamer/0.10/audio/default/musicaudiosink
I've long had these setup to skip pulseaudio, using alsasink with a
specific device (see
http://ccrma-mail.stanford.edu/pipermail/planetccrma/2010-March/016510.html
) :
<entry name="chataudiosink" mtime="1265693808"
type="string">
<stringvalue>alsasink
device="hw:Headset,0"</stringvalue>
</entry>
<entry name="musicaudiosink" mtime="1265693856"
type="string">
<stringvalue>alsasink
device="hw:SB,1"</stringvalue>
</entry>
<entry name="audiosrc" mtime="1282881667"
type="string">
<stringvalue>alsasrc
device="hw:BCD3000,0"</stringvalue>
</entry>
<entry name="audiosink" mtime="1282881208"
type="string">
<stringvalue>alsasink
device="default"</stringvalue>
</entry>
Unfortunately, despite these and other measures in place, I still
continue seeing signs of attempting to contact pulseaudio first in
gnome/gstreamer apps: "socket(): Address family not supported by
protocol" ( e.g.
http://www.spinics.net/lists/fedora-music/msg00607.html )