From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0001971]: Some elements incorrectly have capture flags
Date: Wed, 5 Apr 2006 18:42:14 +0200 [thread overview]
Message-ID: <7d0f72e0817d118338f2bca3ae83ff88@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1971>
======================================================================
Reported By: pzad
Assigned To:
======================================================================
Project: ALSA - lib
Issue ID: 1971
Category: simple mixer
Reproducibility: always
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 03-28-2006 12:16 CEST
Last Modified: 04-05-2006 18:42 CEST
======================================================================
Summary: Some elements incorrectly have capture flags
Description:
Some elemnts have capture flags even they have nothing to do with capture.
This will duplicate control in alsamixer - view ALL.
On VIA8233A + ALC650:
Simple mixer control '3D Control - Center',0
Capabilities: volume volume-joined
Playback channels: Mono
Capture channels: Mono
Limits: 0 - 15
Mono: 1 [7%]
Simple mixer control '3D Control - Depth',0
Capabilities: volume volume-joined
Playback channels: Mono
Capture channels: Mono
Limits: 0 - 15
Mono: 0 [0%]
On Audigy 1:
Simple mixer control 'Bass',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 40
Front Left: 23 [58%]
Front Right: 23 [58%]
Simple mixer control 'Treble',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 40
Front Left: 27 [68%]
Front Right: 27 [68%]
======================================================================
----------------------------------------------------------------------
Raymond - 04-03-06 19:08
----------------------------------------------------------------------
Do the order of the control appear in the alsamixer determined by the name
?
There is no need to place those 3D controls in the front
----------------------------------------------------------------------
Raymond - 04-05-06 18:42
----------------------------------------------------------------------
I can group the lower 4 bands to implement the bass control and the upper 6
bands to implement the treble control.
The new "Bass" and "Treble" will appear in kmix.
how can I add the surround of STAC9708 into kmix ?
/*
Bass control - the lower 4 bands
*/
static int
snd_vortex_bass_treble_info(struct snd_kcontrol *kcontrol, struct
snd_ctl_elem_info *uinfo)
{
uinfo->type = SNDRV_CTL_ELEM_TYPE_INTEGER;
uinfo->count = 2;
uinfo->value.integer.min = 0x0000;
uinfo->value.integer.max = 0x7fff;
return 0;
}
static int
snd_vortex_bass_get(struct snd_kcontrol *kcontrol, struct
snd_ctl_elem_value *ucontrol)
{
vortex_t *vortex = snd_kcontrol_chip(kcontrol);
ucontrol->value.integer.value[0] = vortex->bass[0];
ucontrol->value.integer.value[1] = vortex->bass[1];
return 0;
}
static int
snd_vortex_bass_put(struct snd_kcontrol *kcontrol, struct
snd_ctl_elem_value *ucontrol)
{
vortex_t *vortex = snd_kcontrol_chip(kcontrol);
int changed = 0, i;
if ( vortex->bass[0] != ucontrol->value.integer.value[0]) {
vortex->bass[0] = ucontrol->value.integer.value[0];
changed = 1;
};
if ( vortex->bass[1] != ucontrol->value.integer.value[1]) {
vortex->bass[1] = ucontrol->value.integer.value[1];
changed = 1;
};
for (i=0; i<4; i++) {
vortex_Eqlzr_SetLeftGain(vortex, i, vortex->bass[0]);
vortex_Eqlzr_SetRightGain(vortex, i, vortex->bass[1]);
}
return changed;
}
static struct snd_kcontrol_new vortex_bass_kcontrol __devinitdata = {
.iface = SNDRV_CTL_ELEM_IFACE_MIXER,
.name = "Tone Control - Bass",
.access = SNDRV_CTL_ELEM_ACCESS_READWRITE,
.info = snd_vortex_bass_treble_info,
.get = snd_vortex_bass_get,
.put = snd_vortex_bass_put
};
/*
Treble control - the upper 6 bands
*/
static int
snd_vortex_treble_get(struct snd_kcontrol *kcontrol, struct
snd_ctl_elem_value *ucontrol)
{
vortex_t *vortex = snd_kcontrol_chip(kcontrol);
ucontrol->value.integer.value[0] = vortex->treble[0];
ucontrol->value.integer.value[1] = vortex->treble[1];
return 0;
}
static int
snd_vortex_treble_put(struct snd_kcontrol *kcontrol, struct
snd_ctl_elem_value *ucontrol)
{
vortex_t *vortex = snd_kcontrol_chip(kcontrol);
int changed = 0, i;
if ( vortex->treble[0] != ucontrol->value.integer.value[0]) {
vortex->treble[0] = ucontrol->value.integer.value[0];
changed = 1;
}
if ( vortex->treble[1] != ucontrol->value.integer.value[1]) {
vortex->treble[1] = ucontrol->value.integer.value[1];
changed = 1;
}
for (i=4; i<10; i++) {
vortex_Eqlzr_SetLeftGain(vortex, i, vortex->treble[0]);
vortex_Eqlzr_SetRightGain(vortex, i, vortex->treble[1]);
};
return changed;
}
static struct snd_kcontrol_new vortex_treble_kcontrol __devinitdata = {
.iface = SNDRV_CTL_ELEM_IFACE_MIXER,
.name = "Tone Control - Treble",
.access = SNDRV_CTL_ELEM_ACCESS_READWRITE,
.info = snd_vortex_bass_treble_info,
.get = snd_vortex_treble_get,
.put = snd_vortex_treble_put
};
Issue History
Date Modified Username Field Change
======================================================================
03-28-06 12:16 pzad New Issue
03-30-06 11:01 Raymond Note Added: 0009028
03-30-06 12:50 pzad Note Added: 0009031
03-30-06 13:13 pzad Note Added: 0009032
03-30-06 13:22 Raymond Note Added: 0009033
03-30-06 13:29 Raymond Note Edited: 0009033
03-30-06 13:41 Raymond Note Edited: 0009033
03-31-06 04:36 Raymond Note Added: 0009041
03-31-06 04:50 Raymond Note Edited: 0009041
04-01-06 01:13 Raymond Note Edited: 0009033
04-03-06 19:08 Raymond Note Added: 0009103
04-05-06 18:42 Raymond Note Added: 0009121
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-04-05 16:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 16:42 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-24 14:44 [ALSA - lib 0001971]: Some elements incorrectly have capture flags bugtrack
2006-07-24 1:00 bugtrack
2006-07-23 2:19 bugtrack
2006-07-22 21:01 bugtrack
2006-07-22 3:25 bugtrack
2006-06-30 16:20 bugtrack
2006-04-14 4:21 bugtrack
2006-04-13 18:26 bugtrack
2006-04-13 9:32 bugtrack
2006-04-07 10:05 bugtrack
2006-04-06 7:44 bugtrack
2006-04-03 17:08 bugtrack
2006-03-31 2:36 bugtrack
2006-03-30 11:22 bugtrack
2006-03-30 11:13 bugtrack
2006-03-30 10:50 bugtrack
2006-03-30 9:01 bugtrack
2006-03-28 10:16 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=7d0f72e0817d118338f2bca3ae83ff88@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 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.