alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Alsamixertest
Date: Mon, 04 Oct 2010 14:25:34 +0200	[thread overview]
Message-ID: <4CA9C7BE.7020804@canonical.com> (raw)
In-Reply-To: <4CA9C22A.2010104@ladisch.de>

On 2010-10-04 14:01, Clemens Ladisch wrote:
> David Henningsson wrote:
>> On 2010-10-02 04:11, Raymond Yau wrote:
>>> It seem that the program keep complain about those controls without dB scale
>>> (e.g. AC97 3D Control - depth and rear depth , .) with the emulated intel8x0
>>> driver  and no volume control with the emulated sb16 in virtualbox
>>
>> It's a righteous warning if you ask me - all volume controls should
>> provide dB information,
>
> But "3D Depth" and some other controls are not volume controls and are
> not measured in dB.
>
>> or we don't know what they actually do.
>
> Where "we" = "generic software like PA".  Non-standard controls can be
> controlled only by hardware-specific tools or by the user.

Exactly, this is a test tool that checks whether the mixer control names 
and dB information live up to PulseAudio's expectations. That's the 
tool's purpose.

Given some thought, perhaps the application warning should be removed. 
It might be that it should only require dB information for the controls 
it actually wants to test (i e Master, PCM etc)...what do you think?

-- 
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic

  reply	other threads:[~2010-10-04 12:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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  5:54     ` Mark Brown
2010-09-27  6:53       ` Stas Sergeev
2010-09-27 22:00         ` Mark Brown
2010-09-28  5:38           ` Stas Sergeev
2010-09-28  9:36             ` Raymond Yau
2010-09-27 14:40       ` Stas Sergeev
2010-09-27 17:57     ` Colin Guthrie
2010-09-28  1:01       ` Raymond Yau
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                 ` David Henningsson [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2010-09-29  9:42 Alsamixertest David Henningsson
2010-09-29  9:48 ` Alsamixertest Raymond Yau
2010-09-29 10:12   ` Alsamixertest David Henningsson

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=4CA9C7BE.7020804@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    /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;
as well as URLs for NNTP newsgroup(s).