From: David Henningsson <david.henningsson@canonical.com>
To: alsa-devel@alsa-project.org
Subject: Alsamixertest
Date: Wed, 29 Sep 2010 11:42:43 +0200 [thread overview]
Message-ID: <4CA30A13.2030802@canonical.com> (raw)
Here's the tool "one of the Mandriva guys" ;-) was talking about the
other day. I should probably have announced it on both lists simultaneously.
Anyway, over the previous weeks I've been working on a small script
which tests whether the ALSA mixer lives up to PA's expectations. If you
are familiar with dbmeasure or dbverify by Lennart Poettering, this
application's purpose is very similar, but this one is hopefully easier
to set up, more user friendly, and also tests that the names of the
volume controls are correct.
My hope is that this will aid as a debugging tool for all these
"everything below 20% of my speaker is muted, and then 21% blows my
speakers" bugs.
To use the tool, you'll need some kind of loopback. You can e g use a
loopback cable and connect that between line in and line out, or test
your laptop's internal speakers with your laptop's internal mic (just
stop humming when you do so :-) ). Just set up the recording levels
appropriately.
Alsamixertest is available for Ubuntu Lucid and Ubuntu Maverick from
these PPAs:
Lucid: https://launchpad.net/~diwic/+archive/ppa
Maverick: https://launchpad.net/~diwic/+archive/maverick
For other distributions, download the tarball:
https://launchpad.net/~diwic/+archive/ppa/+files/alsamixertest_47.14.tar.gz
Unpack and read the readme file for compilation and install instructions.
When it is installed, run "alsamixertest -r" for a small tutorial and
"alsamixertest -h" for command line options help.
Looking forward to your comments about this new little tool! I think it
should be considered "beta" quality at this point.
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next reply other threads:[~2010-09-29 9:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 9:42 David Henningsson [this message]
2010-09-29 9:48 ` Alsamixertest Raymond Yau
2010-09-29 10:12 ` Alsamixertest David Henningsson
-- strict thread matches above, loose matches on Subject: below --
2010-09-26 15:17 how to mandate the use of PCM plugin? Stas Sergeev
2010-09-27 0:58 ` Mark Brown
2010-09-27 4:48 ` Stas Sergeev
2010-09-27 17:57 ` Colin Guthrie
2010-09-28 4:07 ` Raymond Yau
2010-09-29 9:28 ` David Henningsson
2010-10-02 2:11 ` Raymond Yau
2010-10-04 7:51 ` Alsamixertest (was: how to mandate the use of PCM plugin?) David Henningsson
2010-10-04 12:01 ` Alsamixertest Clemens Ladisch
2010-10-04 12:25 ` Alsamixertest David Henningsson
2010-10-04 12:34 ` Alsamixertest Clemens Ladisch
2010-10-06 4:08 ` Alsamixertest Raymond Yau
2010-10-05 1:50 ` Alsamixertest Raymond Yau
2010-10-12 14:33 ` Alsamixertest Raymond Yau
2010-10-21 4:36 ` Alsamixertest Raymond Yau
2010-10-21 7:50 ` Alsamixertest David Henningsson
2010-10-22 1:53 ` Alsamixertest Raymond Yau
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=4CA30A13.2030802@canonical.com \
--to=david.henningsson@canonical.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 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.