New answers tagged pulseaudio
You could specify the file be created in /tmp by adding that value to /etc/pulse/client.conf: cookie-file = /tmp/pulse-cookie
sudo modprobe snd_aloop Adds a loopback device to ALSA, which appears in the PulseAudio Volume Control. Redirect your stream there, and presto! Not sure how to add multiple loopback devices.
The problem lies in a PulseAudio module called module-role-cork which exists to pause music and video during phone calls. All applications are given a media-role property which can be either music video or phone. The Cork module will give any application tagged phone exclusive access to the PulseAudio server and pause anything not tagged as such. Simply ...
Check the volume control settings. The Recording Tab should also show a jumping VU-meter. If not: Change the 'Alsa capture from'
As explained in https://bbs.archlinux.org/viewtopic.php?id=172491, this is a problem with semi-installed (as in, not installed at all, but modules still exist) bluetooth support. If you deactivate bluetooth fully in your /etc/pulse/default.pa, by commenting out the following lines: ### Automatically load driver modules for Bluetooth hardware #.ifexists ...
Have you tried disabling suspend-on-idle in /etc/pulse/default.pa? I change this: ### Automatically suspend sinks/sources that become idle for too long load-module module-suspend-on-idle to this: ### Automatically suspend sinks/sources that become idle for too long #load-module module-suspend-on-idle and then killall pulseaudio to restart it.
You should start OSS applications using padsp. This would seem to be the obvious thing to do, but you don’t mention it.
Top 50 recent answers are included