From: Rimas Kudelis <rq@akl.lt>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Test model
Date: Tue, 21 Feb 2006 12:17:28 +0200 [thread overview]
Message-ID: <43FAE8B8.4000400@akl.lt> (raw)
In-Reply-To: <200602202317.k1KNHPMb021810@auster.physics.adelaide.edu.au>
Hello,
>> I think I pointed both capture sources at MIC1 (my internal/external
>> microphone), then selected both channels for capture in capture mixer.
>>
> What program did you then use to do the recording?
Gnome sound recorder.
> In a vast majority of
> cases this will only record from the first PCM, so even though alsamixer had
> both ADCs selected, odds are you were still only recording one of them.
> This probably explains the silence in your initial test - you were still
> only recording ADC0, but in that case it didn't have any source enabled.
>
> Therefore the only odd thing about that test is the fact that you didn't
> get any signal from the mic.
>
Yes, and I also wonder, where could that hiss have come from...
>>> What kind of microphone were you using? Did you have a bias setting
>>> configured for the jack the mic was connected to?
>>>
>> I tried it with the internal mic. I could clearly hear in the speakers
>> when I tapped the computer with my fingers, so I assumed I should be
>> able to record that sound too. However, all I got was the hiss ...
>>
> I would have expected that to work. Which speakers did you hear the tapping
> in? The internal ones and the headphone jack aren't currently functional,
> so that leaves only the external mic jack operating as an output, doesn't
> it? If so then perhaps it's some kind of coupling.
>
No, I used the Line-In jack (LINE1 channel) operating as output. Mic
(MIC1 channel) was set to 50pc or 80pc mic, of course. I could clearly
hear my tapping from the external amplified speakers connected to the
Line-In jack, but nothing was recorded no matter which ADC(s) I selected
for capture.
>>>> Also, not sure if it's alsamixer's or driver's fault, alsamixer always
>>>> says "Input Source 1" is "1", even though it selects the required source.
>>>>
>>> I'm confused by this - "1" isn't an option AFAIK. "MIC1", "MIC2", "LINE1",
>>> "LINE2" etc are the options.
>>>
>> Right. So I can select MIC1, LINE1 etc in the alsamixer, but the
>> indicator at the top always says "1" no matter what I select.
>>
> I'll have to check this on my laptop tonight - in particular, I'm not sure
> what the "indicator at the top" is off-hand.
>
There's an informational block at top-left of alsamixer.
>> OTOH, I haven't recompiled ALSA utils (I think, Im using what Ubuntu has
>> provided me with), so it might just be version incompatibility.
>>
> Which version of alsautils is that - the version number should be at the top
> of alsamixer.
>
I can't check it now.
> The initverbs for the test model unmute both the input and output of NIDs
> 0x0f to 0x15, so they are ready for whichever mode is configured by the mode
> switch. This is why there are no explicit switches in the mixer for this.
> Having switches for this would add significantly to the number of things a
> tester would have to think about. It was clear from my tests that having
> both input and output unmuted didn't cause any trouble (beyond perhaps
> contributing to a slight increase in the noise level when sampling), so
> there was no basis to include manual switches for these.
>
That's why I said it should probably go to the extended test model.
However, on the other hand, if unmuting those ports indeed increases
noise level, maybe it would indeed be better to mute certain unused
ports in certain models that don't have anything connected to them anyways.
> Having said all that, I think it's actually possible to include manipulation
> of these mute switches as part of the jack mode control. Doing so will reduce
> the ADC noise level slightly.
>
That's a positive effect.
> This is simply to enable or disable the SPDIF control. Having it disabled
> puts it into the Hi-Z state, which is short for "high impedence". Essentially
> this means that the current driver/receiver is disconnected from the pin.
> It doesn't mean that analog audio is enabled.
>
Oh, I see.
Another thing: hda_local.h defines six pinctl values:
#define PIN_IN 0x20
#define PIN_VREF80 0x24
#define PIN_VREF50 0x21
#define PIN_OUT 0x40
#define PIN_HP 0xc0
#define PIN_HP_AMP 0x80
Did you miss the PIN_HP_AMP option when adding channel mode switchers,
or is it not available for ALC260, or what? If it's available in ALC260,
I think it should be added to the list of options. Just to make sure
we're not missing anything...
Another weird detail. Look at the picture here:
http://notebooky.idnes.cz/obrazek/acer_tm4600_aspire1690_09.jpg. On my
mothers notebook (which is almost identical to the one in the pic), the
outside of Line In and Mic jacks is made of metal, while the outside of
Headphones jack is made of black plastic. I wonder what is the reason
for this...
>>> The only way I would have thought the digital outputs could come into play
>>> is if for some reason the internal speaker and headphone jack were driven
>>> off an external DAC. As I mentioned in a previous post though this doesn't
>>> seem sensible from where we stand.
>>>
>> Well, having no sound from internal speakers in Linux, while having it
>> in Windows, doesn't seem sensible too... ;) It's as I said - when no
>> sane options are left, it's probably the time to try those that seem
>> insane. Just to make sure.
>>
> No arguments there. I can't help but think that we're missing something
> though.
I think so too. However, there's one weird thing - one user of a similar
laptop said on Ubuntu forums that the sound worked for him initially.
However, it seems like he's too „untechnical“ and unmotivated to give
any detail or even engage into a dialog... :( I wouldn't even be
surprised to find out that his notebook is not a member of the
Travelmate 4060 series at all...
RQ
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
next prev parent reply other threads:[~2006-02-21 10:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 22:49 Test model Rimas Kudelis
2006-02-15 23:48 ` Jonathan Woithe
2006-02-16 9:29 ` Rimas Kudelis
2006-02-16 10:05 ` Rimas Kudelis
2006-02-17 2:05 ` Jonathan Woithe
2006-02-16 10:08 ` Paulo Matias
2006-02-16 16:52 ` Rimas Kudelis
2006-02-17 2:14 ` Jonathan Woithe
2006-02-17 2:12 ` Jonathan Woithe
2006-02-17 1:59 ` Jonathan Woithe
2006-02-17 12:07 ` Rimas Kudelis
2006-02-17 12:57 ` Paulo Matias
2006-02-17 13:17 ` Rimas Kudelis
2006-02-17 18:18 ` Rimas Kudelis
2006-02-17 18:24 ` Paulo Matias
2006-02-17 18:36 ` Rimas Kudelis
2006-02-20 0:44 ` Jonathan Woithe
2006-02-17 18:40 ` Paulo Matias
2006-02-20 0:27 ` Jonathan Woithe
2006-02-19 17:05 ` Rimas Kudelis
2006-02-19 23:33 ` Jonathan Woithe
2006-02-20 5:32 ` Rimas Kudelis
2006-02-20 6:32 ` Jonathan Woithe
2006-02-20 7:13 ` Rimas Kudelis
2006-02-20 23:17 ` Jonathan Woithe
2006-02-21 10:17 ` Rimas Kudelis [this message]
2006-02-21 23:20 ` Jonathan Woithe
2006-02-22 6:40 ` Rimas Kudelis
2006-02-22 23:50 ` Jonathan Woithe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43FAE8B8.4000400@akl.lt \
--to=rq@akl.lt \
--cc=alsa-devel@lists.sourceforge.net \
--cc=jwoithe@physics.adelaide.edu.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.