Bug 42643 - Capture device handling on Acer Aspire One 531h
Summary: Capture device handling on Acer Aspire One 531h
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-06 04:28 UTC by Dmitrij D. Czarkoff
Modified: 2018-07-30 09:34 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Dmitrij D. Czarkoff 2011-11-06 04:28:56 UTC
On Acer Aspire One 531h there are two microphones: 
* internal, works;
* mic jack, doesn't work, seems to be hardware fault. May be is aggregated with internal mic, I can't test it.

From now on I refere to internal micorophone as "mic".

Alsa gives three capture controls:
* Mic Boost - probably boosts something, but no audible effect (with my ears);
* Capture - controls the internal mic.
* Capture 1 - controls nothing.

Pulseaudio gives one two-channel control.

With alsa applications everything works as expected - the mic works, records in two-channel mode. Eg., in gnome-sound-recorder.

In pulsaudio the capture records nothing with capture level up on both channels. More interestingly, the actual volume seems to be the difference between the channels' volumes. Eg., if left channel is set to 0 in alsamixer and right channel is set to 100, sound is loud, in combination 0-50 - half of previous.
Comment 1 GitLab Migration User 2018-07-30 09:34:41 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/27.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.