On Tue, Sep 15, 2009 at 6:45 AM, Takashi Iwai tiwai@suse.de wrote:
At Mon, 14 Sep 2009 12:36:47 -0400, Alistair Boyle wrote:
For the capture settings, "digital" should be the first setting since its the master capture control,
You should keep this "Digital" control to 50%, corresponding to 0dB.
"front mic" controls the stereo built-in mic (good), "line" doesn't do anything(?), "mic" sets the mic jack (good), there are two capture volumes (capture and capture 1) and two "input source"s (line, mic, or front mic). I think there should only be mic or front mic unless there's someway to set the mic jack as "line in" somewhere else?
This is my question, too. The original patch mentioned about a line-in. I guess a prototype machine had it, but not on real machines.
I can now record from the built-in mic ("front mic") vs 1.0.20.
This seems to be a bit of a regression: the recording source labels are reversed. To record from the built-in mic I have to set the "input source" selector to "mic" instead of "front mic" and vice-versa for plugging in a mic. There doesn't seem to be any automatic switching of recording sources occurring. Both recording sources still work.
So to summarize: - independent headphones don't have separate headphone volumes - "digital" should be the master capture control - there seems to be duplicate capture controls (capture & capture 1, wit corresponding "input sources") - "pc beep" seems to be a bit busted
OK, now I fixed these issues. There were some left-over bugs indeed. The driver also supports the automatic mic selection via plugging for S14 now.
(Note that the multiple capture controls are no bug. The codec has multiple ADCs and the driver provides the multiple streams, too. But, together with the auto-mic feature, only one ADC is used now.)
Try the latest alsa-driver snapshot below, and report back. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
The headphones are still both controlled by the single "headphone" control and are not independent and the "pc beep" still emits crackling on a xterm beep and has to be muted.
The reason I was asking about the "digital" control is because, when using Skype, the program tries to adjust the recording volume on-the-fly. In windows this works fine, in linux I see it trying to fiddle with the "front mic" recording volume which only has three settings and doesn't affect the mic jack. I'd think "Digital" would be more appropriate to twiddle since it controls both the built-in mic and the jacked one and has finer control. I can disable this behavior in Skype but I'm guessing there's no way, in general, for programs to know which alsa control is generally the "master" record control and they're just guessing that the first one they grab is?
I've attached a new alsa-info.
Thanks for the speedy response! Alistair