From: "Miroslav Šulc" <fordfrog@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: acer aspire 8943g with alc670
Date: Thu, 29 Jul 2010 16:28:02 +0200 [thread overview]
Message-ID: <4C518FF2.6040406@gmail.com> (raw)
In-Reply-To: <AANLkTinUo_OsHxzb6RHeNfPD=9SD+tsEVQ0=GMa+TEni@mail.gmail.com>
Dne 29.7.2010 15:54, Raymond Yau napsal(a):
> 2010/7/29 Miroslav Šulc <fordfrog@gmail.com>
>> .
>>> About the graph
>>> the blue line - connected audio path
>>> the grey line - unconncted audio path
>>> the line turn red when you put the mouse cursor near any line ,
>> so hovering over gray connection makes the connection in the card
>> driver, and hovering over blue connection disables the connection?
> No, I guess you have to clicked the buttons in the nodes
>
> the graph show just the connected audio path, and it allow you to know which
> widgets will be connected when you put your mouse over the line
hm, seems i have no idea how to use hda analyzer then :-) anyway, will
first file bug this evening and then will see.
> how did you get the hda_analyzer ?
http://www.alsa-project.org/main/index.php/HDA_Analyzer
and also:
git clone git://git.alsa-project.org/alsa.git alsa
cd alsa/hda_analyzer
python hda_analyzer.py
> using the previous version of run.py did not download all the programs
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-07-29 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 2:09 acer aspire 8943g with alc670 Miroslav Šulc
2010-07-29 13:20 ` Raymond Yau
2010-07-29 13:40 ` Miroslav Šulc
2010-07-29 13:54 ` Raymond Yau
2010-07-29 14:28 ` Miroslav Šulc [this message]
2010-07-29 15:10 ` Jaroslav Kysela
2010-07-29 16:24 ` Miroslav Šulc
2010-07-29 16:35 ` Miroslav Šulc
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=4C518FF2.6040406@gmail.com \
--to=fordfrog@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox