[opensuse-kde] PulseAudio and flash
My workflow generally consists of listening to amarok, reading akregator, pausing amarok, and then watching flash videos on youtube (this is not what I do all day. Is it?) Anyways, pulse audio is the preferred media device with the xine backend. Almost everytime amarok will freeze, youtube won't have audio and I will have to restart amarok, the browser, kmix, and the alsasound service. I've tried this with x86 and x86_64 versions of flash. The x86 makes amarok freeze until the browser instance that spawned flash is quit. The x86_64 version will only allow the audio to recover if alsasound is restarted. Any help would be nice. Thanks -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Onsdag den 27. januar 2010 02:57:42 skrev Marc Benstein:
My workflow generally consists of listening to amarok, reading akregator, pausing amarok, and then watching flash videos on youtube (this is not what I do all day. Is it?)
Anyways, pulse audio is the preferred media device with the xine backend. Almost everytime amarok will freeze, youtube won't have audio and I will have to restart amarok, the browser, kmix, and the alsasound service.
I've tried this with x86 and x86_64 versions of flash. The x86 makes amarok freeze until the browser instance that spawned flash is quit. The x86_64 version will only allow the audio to recover if alsasound is restarted.
Any help would be nice.
Any reason why you don't just remove pulseaudio? It's not part of an 11.2 default kde installation - for a reason. Don't know if the problems can be fixed with configuration - or maybe getting a sound card with hardware mixing(?) - since I personally have been avoiding PA like the plague so far :-) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
2010/1/27 Martin Schlander
Onsdag den 27. januar 2010 02:57:42 skrev Marc Benstein:
My workflow generally consists of listening to amarok, reading akregator, pausing amarok, and then watching flash videos on youtube (this is not what I do all day. Is it?)
Anyways, pulse audio is the preferred media device with the xine backend. Almost everytime amarok will freeze, youtube won't have audio and I will have to restart amarok, the browser, kmix, and the alsasound service.
I've tried this with x86 and x86_64 versions of flash. The x86 makes amarok freeze until the browser instance that spawned flash is quit. The x86_64 version will only allow the audio to recover if alsasound is restarted.
Any help would be nice.
Any reason why you don't just remove pulseaudio? It's not part of an 11.2 default kde installation - for a reason.
Workaround instead of tiny modification and using PulseAudio which is great solution :) -- Rafał -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
2010/1/27 Marc Benstein
My workflow generally consists of listening to amarok, reading akregator, pausing amarok, and then watching flash videos on youtube (this is not what I do all day. Is it?)
Anyways, pulse audio is the preferred media device with the xine backend. Almost everytime amarok will freeze, youtube won't have audio and I will have to restart amarok, the browser, kmix, and the alsasound service.
I've tried this with x86 and x86_64 versions of flash. The x86 makes amarok freeze until the browser instance that spawned flash is quit. The x86_64 version will only allow the audio to recover if alsasound is restarted.
Any help would be nice.
Solution is trivial, for some reason openSUSE provides configuration file with wrong name. Please do following: $ su [password] # zypper in alsa-plugins-pulse # mv /etc/asound-pulse.conf /etc/asound.conf Then I suggest just restarting system. -- Rafał -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Mittwoch 27 Januar 2010 schrieb Rafał Miłecki:
2010/1/27 Marc Benstein
: My workflow generally consists of listening to amarok, reading akregator, pausing amarok, and then watching flash videos on youtube (this is not what I do all day. Is it?)
Anyways, pulse audio is the preferred media device with the xine backend. Almost everytime amarok will freeze, youtube won't have audio and I will have to restart amarok, the browser, kmix, and the alsasound service.
I've tried this with x86 and x86_64 versions of flash. The x86 makes amarok freeze until the browser instance that spawned flash is quit. The x86_64 version will only allow the audio to recover if alsasound is restarted.
Any help would be nice.
Solution is trivial, for some reason openSUSE provides configuration file with wrong name. Please do following:
$ su [password] # zypper in alsa-plugins-pulse # mv /etc/asound-pulse.conf /etc/asound.conf
Then I suggest just restarting system.
Ouch! cat > ~/.kde/env/pulse.sh << EOF export ALSA_CONFIG_PATH=/etc/alsa-pulse.conf EOF The file name is not wrong. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
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
On Wednesday, January 27, 2010, Pedro Lopez-Cabanillas wrote:
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.
And you can do that using YaST->Hardware->Sound. Locate the "other" combo, at the bottom-right: * Other->PulseAudio configuration ... * Check the "Enable PulseAudio Support" box. * Press OK. It changes the "/etc/environment" file, that will be used the next time you login, so you need to restart your desktop session. Regards, Pedro -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (5)
-
Marc Benstein
-
Martin Schlander
-
Pedro Lopez-Cabanillas
-
Rafał Miłecki
-
Stephan Kulow