Volume of microphone set to zero

Asus laptop with Leap 42.1 and default KDE desktop. Everything in regards of Multimedia works without problem, however there is one annoyance. After every reboot the microphone volume is set to zero. The microphone is only used for skype calls, but if you forget to set the microphone volume to 100% the other end of the call doesn’t hear you. I have tried to find where the setting could be made so that even after a reboot the volume of the microphone is up but I couldn’t find anything. Any ideas anyone? Thank you Uli

Try using pavucontrol to set the desired levels. They should persist through reboot.

Thank you, deano_ferrari, but for some reason that does not work - see screenshot https://paste.opensuse.org/57760848. On the left the pavucontrol settings. Then I opened YAST (right) and the microphone is still set to zero. I have to slide that across before I can use skype. I would like to have the settings with the microphone in YAST set to 100% remaining but it always goes back to zero on reboot.

Try clearing the settings for pulse I think they are in ~/.config/pulse now used to be in ~/.pulse. Changed in Leap. In any case corrupted file there can cause odd behaviour. Could also try a different test user.

Hmm…I’ve never needed to adjust levels with YaST. Try adjusting using ‘alsamixer’ (via terminal). You can select your sound card using F6. Once done, save it with

sudo alsactl store

Those settings should be persistent now.

Thank you gogalthorp and deano_ferrari, but no success so far. I tried alsamixer and alsactl store but after a reboot the microphone setting was back to zero. Then I deleted the files in the .pulse directory and restarted - again the the microphone setting was back to zero. Any ideas what next?

See if anything in this thread helps…

https://forums.opensuse.org/showthread.php/507291-Microphone-volume-very-low-when-routed-through-Pulseaudio

Thanks, deano_ferrari, in this link is a quote from oldcpu "One possible explanation is your mic boost is too low:
Code:

Simple mixer control 'Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 3
  Front Left: 0 [0%] [0.00dB]
  Front Right: 0 [0%] [0.00dB]

"
I don’t know where this is coming from - some config file??? If I know where this is I could try to edit this file. Otherwise I couldn’t find any help there.
But if nobody knows what I could do next - is there the possibility to have a startup script which is opening the mic settings?

AFAIU, the alsa levels are stored in /var/lib/alsa/asound.state, but you don’t edit that file directly.

You can check your hardware settings in a terminal with

amixer -c0

but it will only confirm what you already know ie that the mic level is at zero.

Yes, I guess you could set the desired level with something like

amixer -c 0 sset 'Mic' 50

and verify the applied setting with

amixer -c 0 sget 'Mic'

BTW, you can get the available control names for your sound card with

amixer -c 0 scontrols

Create a script file eg ~/mic-level.sh with your favourite editor

#!/bin/bash
amixer -c 0 sset 'Mic' 50

Make it executable with

chmod +x ~/mic-level.sh

Once you have your script file and have made it executable, you can have it autostart via
SystemSettings5 > Startup and Shutdown > Autostart > Add script
It will execute the next time you start your desktop.

Thank you, deano_ferrari, that is excellent help !

Only if it works for you. Let us know how you get on.

Yes the script works - I rebooted 3 times by now and the microphone volume was up each time. The only difference to your post was that I needed to put ‘Mic Boost’ instead of ‘Mic’ in the script. But that showed up when I used the command

amixer -c 0 scontrols

as you explained.
Thanks again.
Uli

I thought that might be the case, but wasn’t sure about which specific control was zero from your earlier posts. (To be honest, I’m not sure why PA keeps resetting that value at boot, but the autostart script corrects that anyway.)

But that showed up when I used the command

amixer -c 0 scontrols

as you explained.
Thanks again.
Uli

Glad to have been of help. :slight_smile: