Registered Member
|
Using KDE 4.1 under Arch (Arch version, not KDEmod).
In order for the microphone to work under Skype, I need to check the capture box beneath the volume slider in the mixer window. This setting does not stick, so I need to set it again after a reboot. Tried setting it with alsamixer, but that didn't help either. Any ideas?
Last edited by XiniX on Mon Dec 08, 2008 12:15 pm, edited 1 time in total.
XiniX, proud to be a member of KDE forums since 2008-Oct.
|
Administrator
|
In KMix > Configure KMix, do you have Restore volumes on login checked? With regard to the setting 'sticking' does this happen under other Desktop Environments or at the terminal? If it still does ( capture being disabled on reboot ), then it would be a feature report ( asking for KMix to restore more than just the volume of sliders but also Mute, Capture, etc ). If it doesn't and KMix is actually disabling capture for some reason then file a bug report. Reports ( bug or feature requests ) are filed on the KDE bug tracker.
Last edited by bcooksley on Sun Dec 07, 2008 8:03 pm, edited 1 time in total.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Thanks for the reply.
Yes, the setting for 'restore volumes' is ticked. I don't know if other DEs behave the same under Arch. I know that on the same machine, MEPIS with KDE 3.5.8 works correctly. In alsamixer, I can change the capture volume, but there is no option to disable capture, so my guess capture is supposed to be always 'on' under alsa. It seems to me it is a KDE4 thing. I'll check the bug tracker if there's any mention of this issue.
XiniX, proud to be a member of KDE forums since 2008-Oct.
|
Administrator
|
In alsamixer, if a Capture device is currently enabled, then it will show CAPTUR above the volume number. You can press space to toggle the setting.Could you please try the following to see if it an Arch specific alsa setting, or if it is a KMix bug:
If your capture settings stuck, then it is KMix, otherwise it is a Arch specific probably Alsa related bug.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Thanks again.
Did some tests as you suggested. Noticed that when I run alsamixer from a VT before logging on, all volumes are set to 0. When I log on, all volumes are restored, except for the capture device. This got me thinking, since I also had noticed before that the mute button was lit before logging on, and that it got unlit after logging on. And stupid me, I then found I never loaded alsa in the rc.conf. So KDE is smart enough to launch alsa by itself, but then alsa settings do not stick. Loading alsa before kdm kicks in fixed the problem. So thanks for pointing me in the right direction!!
Last edited by XiniX on Mon Dec 08, 2008 9:48 am, edited 1 time in total.
XiniX, proud to be a member of KDE forums since 2008-Oct.
|
Administrator
|
If your problem is solved, can you please add a [SOLVED] tag to the title. Thanks.
|
Registered Member
|
done, sorry
XiniX, proud to be a member of KDE forums since 2008-Oct.
|
KDE Developer
|
Don't worry, you didn't do anything that you need to apologize for. :P
|
Administrator
|
Thank You
|
Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]