#40: Alsa microphone is not working
------------------------+---------------------------------------------------
  Reporter:  iNPUTmice  |       Owner:  vadim          
      Type:  defect     |      Status:  new            
  Priority:  critical   |   Milestone:  QuteCom 2.2-RC4
 Component:  misc       |     Version:  2.2-RC3        
Resolution:             |    Keywords:                 
------------------------+---------------------------------------------------

Comment(by cavedon):

 Mhm, there is some incomplete code in the mixer management:
 libs/sound/src/linux/LinuxVolumeControl.cpp:
 {{{
 int LinuxVolumeControl::getLevel() {
         int level;
         // TODO: retrieve the sound card name from the AudioDevice
         if (_strDeviceType == "pcm") {
                 get_mixer_level("hw:0", PCM_VOLUME, &level);
                 return level;
         } else if (_strDeviceType == "capture") {
                 get_mixer_level("hw:0", CAPTURE_VOLUME, &level);
                 return level;
         }
 }}}

 There are a couple of things here:
  * as the comment says, this code does not get the device that in the user
 settings
  * I do not why "hw:0" was chosen, but a more sensible choice should be
 "default"
  * I think that "Master" value instead of "PCM" volume should be used for
 playback, the first one should be always present (e.g. both hw:0 and and
 pulseaudio), the latter is "hw:0" specific
  * the capture mixer device is somehat more difficult to choose; right
 know it is set to "Capture", but e.g. my hw:0 as only "Int Mic" and "Ext
 Mic" (and therefore I also see the messages reported by iNPUTmice).
 However my "default" device (i.e. pulseaudio) has "Capture", so I would
 leave it so

 That said, I am not sure what sould be the right way do deal with the
 mixer. For example, some cards have two capture volumes, like mine. How do
 you choose the right one? Ask the user? This should not be a concern of
 the application... I believe that pulseaudio is the right way to go...

-- 
Ticket URL: <http://trac.qutecom.org/ticket/40#comment:5>
QuteCom <http://trac.qutecom.org>

_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to