<br><br><div class="gmail_quote">On Thu, Apr 29, 2010 at 5:46 PM, Alexandros Diamantidis <span dir="ltr"><<a href="mailto:adia@hellug.gr">adia@hellug.gr</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* Paul Davis [2010-04-29 16:43]:<br>
<div class="im">> use a h/w mixer control application (e.g. the ugly and terminal-based<br>
> but-so-far-unmatched alsamixer) to set the capture source of the device back<br>
> to, perhaps, "line in". then later, switch it to the "mic".<br>
<br>
</div>Thanks, that worked. Strange thing is I actually had to set the capture<br>
source first to "Stereo Mixer" and then to "Mic" - the other sources<br>
(CD, Line, Front Mic, Stereo Mixer, or setting "Front Mic" and then<br>
"Mic") all exhibited the same behaviour, but setting it to "Stereo<br>
Mixer" and then to "Mic" and leaving it there allowed starting jack with<br>
nothing connected to any jack. I wonder why the source selected *before*<br>
switching to "Mic" matters!<br></blockquote><div><br>the wonders of the world of Intel HDA ... if you care about recording music, you'll get something else when you can.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Also, it seems there's no need to connect an actual mic - connecting just<br>
a 1/4" to 3.5mm adapter works just as well. I think I'll just leave it<br>
plugged in.<br></blockquote><div><br>correct. Jack sensing is a purely mechanical thing. there's no complex "detection" going on.<br><br>--p<br><br></div></div>