[Bug 275998] Re: internal mic capture very low volume when routed through pulseaudio

[mabawsa]

I was fairly miffed at the pulsepeople closing the bug and saying its
the HW issue. This is not good as it used to work in hardy and works
great in ALSA with no pulse; and dare I say it even Vista ;)

So I reopened the bug to try to get a better answer. Maybe people here
can lend a hand to get the volume of messages on this bug up and
something may get done. I for one am convinced the issue is with pulse.

Here is what I wrote:

#423: pulse audio breaks the microphone recording on Intel ICH7/8/9 chipsets
-----------------------+----------------------------------------------------
  Reporter:  mabawsa   |       Owner:  lennart                   
      Type:  defect    |      Status:  reopened                  
  Priority:  high      |   Milestone:                            
 Component:  libpulse  |    Severity:  major                     
Resolution:            |    Keywords:  Intel Microphone Recording
-----------------------+----------------------------------------------------
Changes (by mabawsa):

  * status:  closed => reopened
  * resolution:  elsewhere =>


Comment:

 This all used to work in Ubuntu 8.04.
 Something changed to stop the digital amplification in ALSA being used
 when pulse is installed from Intrepid and Jaunty.
 Do you know what Lennart?

 ALSA also works incredibly well once pulseaudio is removed.
 So where is the resolution? The gnome-volume-control has been dropped by
 Jaunty. If I use pulse with Skype it creates massive lag rendering it
 useless. If I use hw microphone in Skype (the workaround for this) the
 microphone is faint and cannot be boosted.

 This is effecting many users and all paths lead to an issue with
 pulseaudio. So I have reopened the bug.
 Thanks for your effort on this, it would be nice to have pulseaudio
 working  as it looks like it is somewhat useful.

 mab

-- 
internal mic capture very low volume when routed through pulseaudio
https://bugs.launchpad.net/bugs/275998
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.