[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: how to configure pulseaudio to use analog speaker on motherboard not hdmi on video card



On 02/01/14 02:44, Mitchell Laks wrote:

Before I kill pa the first time:

mlaks@Rashi:~$ aplay -D front piano2.wav
aplay: main:682: audio open error: Device or resource busy

then I do:

mlaks@Rashi:~$ ps aux|grep pulse
125       5074 14.4  0.0 457064  7192 ?        Sl   21:13   1:07 /usr/bin/pulseaudio --start --log-target=syslog
125       5570  0.0  0.0 117148  3204 ?        S    21:13   0:00 /usr/lib/pulseaudio/pulse/gconf-helper
mlaks     6601  0.0  0.0 311224  6432 ?        S<l  21:20   0:00 /usr/bin/pulseaudio --start --log-target=syslog
mlaks     6608  0.0  0.0 117120  3172 ?        S    21:20   0:00 /usr/lib/pulseaudio/pulse/gconf-helper
mlaks     6629  0.0  0.0   8528   876 pts/2    S+   21:21   0:00 grep pulse



mlaks@Rashi:~$ pacmd dump
Welcome to PulseAudio! Use "help" for usage information.
### Configuration dump generated at Wed Jan  1 21:34:11 2014

<snip>
set-default-sink alsa_output.pci-0000_01_00.1.hdmi-stereo
set-default-source alsa_output.pci-0000_01_00.1.hdmi-stereo.monitor


It looks like a tough nut to crack...
Mitchell


We might be getting there. See the two different users running pulseaudio, uid '125' and 'mlaks'. Who is this '125' anyway? I'd accuse them of hogging the audio sink, making it unavailable to 'mlaks'. Here is a similar report: <http://ubuntuforums.org/showthread.php?t=2143157&p=12650610#post12650610>

$ grep 125 /etc/passwd
$ grep audio  /etc/group

Here's a snipped I found on the ArchWiki Alsa pages:
"Membership in the audio group also allows direct access to devices, which can lead to applications grabbing exclusive output (breaking software mixing) (snip) Therefore, adding a user to the audio group is not recommended, unless you specifically need to[1].

[1] https://wiki.ubuntu.com/Audio/TheAudioGroup";

So, once you find out who '125' is, let's see whether you can then stop that process monopolising the audio card0.

BTW, killing and restarting the current user's PA process should be much easier than what you do:

$ pulseaudio -k

The default behaviour is to automatically respawn a process.

$ grep spawn /etc/pulse/client.conf
; autospawn = yes

--
Klaus


Reply to: