From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0001909]: Labelling of controls for SB Extigy is confusing
Date: Thu, 3 Aug 2006 09:47:24 +0200 [thread overview]
Message-ID: <66e1e883d8eed74fe47002bb0d59aa1a@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1909>
======================================================================
Reported By: andersin
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1909
Category: alsamixer
Reproducibility: always
Severity: text
Priority: normal
Status: new
======================================================================
Date Submitted: 03-11-2006 16:33 CET
Last Modified: 08-03-2006 09:47 CEST
======================================================================
Summary: Labelling of controls for SB Extigy is confusing
Description:
The controls for the SB Extigy are all labelled as Master. The names should
reflect the channel(s) that they control. Amixer shows this information
(albeit its mapping of controls to actual channels is off).
Additionally a Master 1 control exists that changes the volume of all
channels.
======================================================================
----------------------------------------------------------------------
Raymond - 08-03-06 04:16
----------------------------------------------------------------------
Most likely both alsamixer and amixer cannot handle these two controls
properly
http://www.alsa-project.org/~iwai/writing-an-alsa-driver/x851.htm
The index field holds the index number of this control. If there are
several different controls with the same name, they can be distinguished
by the index
number. This is the case when several codecs exist on the card. If the
index is zero, you can omit the definition above.
You have to ask the ALSA developer why index controls can have different
count.
The mixer applications need to be very smart to handle this difference in
count
control.16 {
comment.access 'read write'
comment.type INTEGER
comment.count 6
comment.range '0 - 200'
iface MIXER
name 'Master Playback Volume'
value.0 130
value.1 130
value.2 130
value.3 130
value.4 130
value.5 130
}
control.17 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 200'
iface MIXER
name 'Master Playback Volume'
index 1
value 130
}
----------------------------------------------------------------------
Raymond - 08-03-06 09:47
----------------------------------------------------------------------
Syntax: SOURCE [DIRECTION] FUNCTION
The following controls appear in capture view of alsamixer because it miss
the 'Playback' direction
Simple mixer control 'Bass',0
Capabilities: volume volume-joined
Playback channels: Mono
Capture channels: Mono
Limits: 0 - 96
Mono: 48 [50%]
Simple mixer control 'Treble',0
Capabilities: volume volume-joined
Playback channels: Mono
Capture channels: Mono
Limits: 0 - 96
Mono: 48 [50%]
The following control should only appear in capture view of alsamixer,
because the control name did not follow Syntax: SOURCE [DIRECTION]
FUNCTION
Simple mixer control 'Capture Input Source',0
Capabilities: enum
Items: 'Input 0' 'Mic' 'Mixer'
Item0: 'Input 0'
Simple mixer control 'Digital In',0
Capabilities: volume volume-joined pswitch pswitch-joined
Playback channels: Mono
Capture channels: Mono
Limits: 0 - 200
Mono: 200 [100%] Playback [on]
These control also not follow the syntax.
Simple mixer control 'Channel Routing Mode Select',0
Capabilities: volume volume-joined
Playback channels: Mono
Capture channels: Mono
Limits: 0 - 6
Mono: 6 [100%]
similar bug report https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1971
and https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1366
http://hg-mirror.alsa-project.org/alsa-kernel?f=2cd9765e57f6;file=Documentation/ControlNames.txt;style=gitweb
Issue History
Date Modified Username Field Change
======================================================================
03-11-06 16:33 andersin New Issue
08-02-06 02:40 Raymond Note Added: 0011384
08-02-06 14:31 andersin Note Added: 0011388
08-02-06 14:31 andersin Note Added: 0011389
08-03-06 04:06 Raymond Note Added: 0011395
08-03-06 04:16 Raymond Note Edited: 0011395
08-03-06 09:47 Raymond Note Added: 0011397
======================================================================
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2006-08-03 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:47 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 2:06 [ALSA - utils 0001909]: Labelling of controls for SB Extigy is confusing bugtrack
2006-08-02 12:31 bugtrack
2006-08-02 12:31 bugtrack
2006-08-02 0:40 bugtrack
2006-03-11 15:33 bugtrack
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=66e1e883d8eed74fe47002bb0d59aa1a@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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