From: Raymond <rayau@netvigator.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Disagreement about versions following CVS update
Date: Mon, 22 Aug 2005 23:13:59 +0800 [thread overview]
Message-ID: <4309EBB7.9010706@netvigator.com> (raw)
In-Reply-To: <s5hoe7qp403.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Sun, 21 Aug 2005 08:55:37 +0800,
> Raymond wrote:
>
>>
>>It's strange to find the following mixer controls in CAPTURE VIEW of
>>alsamixer v1.0.10rc1 :-
>>
>>
>># amixer -version
>>amixer version 1.0.10rc1
>>
>>Simple mixer control '3D Control Sigmatel - Depth',0
>> Capabilities: volume volume-joined
>> Playback channels: Mono
>> Capture channels: Mono
>> Limits: 0 - 3
>> Mono: 0 [0%]
>>Simple mixer control '3D Control Sigmatel - Rear Depth',0
>> Capabilities: volume volume-joined
>> Playback channels: Mono
>> Capture channels: Mono
>> Limits: 0 - 3
>> Mono: 0 [0%]
>
>
> This must be a bug of new simple abstraction code.
>
>
> Takashi
>
>
Not only AC97 3D control, also EQ Peaks and 10-bands stereo EQ controls
Simple mixer control 'EQ0 31Hz',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 32767
Front Left: 16022 [49%]
Front Right: 16022 [49%]
Simple mixer control 'EQ1 63Hz',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 32767
Front Left: 16022 [49%]
Front Right: 16022 [49%]
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-22 15:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 19:33 Disagreement about versions following CVS update Philip Prindeville
2005-08-19 20:36 ` Lee Revell
2005-08-19 21:11 ` Philip Prindeville
2005-08-19 21:14 ` Lee Revell
2005-08-19 22:17 ` Philip Prindeville
2005-08-19 22:25 ` Lee Revell
2005-08-19 23:20 ` Philip Prindeville
2005-08-19 23:28 ` Lee Revell
2005-08-19 23:43 ` Philip Prindeville
2005-08-19 23:47 ` Lee Revell
2005-08-19 23:53 ` Philip Prindeville
2005-08-19 23:56 ` Lee Revell
2005-08-20 0:06 ` Philip Prindeville
2005-08-22 12:12 ` Takashi Iwai
2005-08-22 16:30 ` Philip Prindeville
2005-08-22 16:33 ` Takashi Iwai
2005-08-20 7:17 ` Raymond
2005-08-20 21:06 ` Lee Revell
2005-08-21 0:55 ` Raymond
2005-08-22 12:09 ` Takashi Iwai
2005-08-22 15:13 ` Raymond [this message]
2005-08-22 15:29 ` Takashi Iwai
2005-08-22 12:14 ` Takashi Iwai
2005-08-22 16:27 ` Philip Prindeville
2005-08-22 16:29 ` Takashi Iwai
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=4309EBB7.9010706@netvigator.com \
--to=rayau@netvigator.com \
--cc=alsa-devel@lists.sourceforge.net \
/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