On Wednesday, January 27, 2010, Rafał Miłecki wrote:
# mv /etc/asound-pulse.conf /etc/asound.conf
Then I suggest just restarting system. It should not be necessary, the config file is loaded whenever you start any ALSA application. You need only to restart your applications.
Instead of renaming the file, pointing the environment variable ALSA_CONFIG_PATH to it should be enough. Maybe the packagers could add a "/etc/profile.d/pulse.sh" script for that. You can also just symlink the configuration file: # cd /etc # ln -s asound-pulse.conf asound.conf Another (maybe better) option is to copy it to your home with the name ".asoundrc" , so only applications started by your account are affected: $ cp /etc/asound-pulse.conf ~/.asoundrc The alsa-pulse plugin will work only for applications using the "default" ALSA device. So if one application opens, for instance, the device "hw:0" it would not use pulse. An useful test is to try the program "speaker-test" that comes with alsa-utils, and at the same time opening the "pavucontrol" (PulseAudio volume control) showing the "playback" tab. $ speaker-test -t wave If pulse is enabled for the "default" device, pavucontrol will show a meter labeled "ALSA plugin [speaker-test]" in the "playback" tab. BTW, in my opinion the main problem with pulse is related to the default values of the pulse daemon, which aren't good enough for some soundcards. In this case, the user needs to tweak the configuration file "/etc/pulse/daemon.conf" Regards, Pedro -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org