[pulseaudio-discuss] cannot control input devices from pavucontrol + crashes in recording tab
gmane at colin.guthr.ie
Wed Dec 22 06:27:04 PST 2010
'Twas brillig, and Maarten Bosmans at 22/12/10 12:20 did gyre and gimble:
> 2010/12/22 Peter Hercek <phercek at gmail.com>:
>> Well that says it alll. When I try to control muting or levels of input
>> deviced in pavucontrol then it does not work. I can do this with 'alsamixer
>> -c 0'. I use archlinux and I set pulseaudio based on this page:
>> I also read
>> and it did not seem to contain something which would help.
>> Playback, Output Devices and Configuration tabs seem to work well.
>> Recording tab results in a pavucontrol crash when I try to mute a microphone
>> which is used by arecord.
>> Anything I do in Input Devices does not seem to have any effect.
> [In order to look into the crash, a backtrace would be nice to have
> (don't forget to install debug symbols of all the relevant libraries)]
Yeah a backtraces from pavucontrol would be nice to aid debugging here.
I tried to reproduce here but it didn't crash...
Tho' as I think about it, there should not be a mute on the Recording
tab.... There is no stream volume (or mute) on source outputs (recording
streams), only playback (I did start support to add this to source
outputs but didn't get very far before I found something more
interesting to do!)
So the bug is really that pavucontrol even offers you a mute there at
all! I'll fix that.
> Why are you using arecord? That way you bypass PulseAudio completely
> and record directly from the alsa sound source. Using parec instead
> gives you all the pulse goodies you can handle!
Actually arecord will typically use the "default" PCM which should be
mapped to pulseaudio in any sensible setup. It should work fine (it does
Tribalogic Limited [http://www.tribalogic.net/]
Mageia Contributor [http://www.mageia.org/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
More information about the pulseaudio-discuss