From: Peter Christensen <peter@developers.dk>
To: alsa-devel@lists.sourceforge.net
Subject: Mixer control names out of control?
Date: Sat, 27 Nov 2004 10:26:40 +0100 [thread overview]
Message-ID: <41A84850.5000604@developers.dk> (raw)
Hello,
Am I the only one feeling that the names of the mixer controls in ALSA is somewhat out of control? Especially when it comes to IEC958.
First of all, the AC97 driver uses the name "IEC958 Playback SPSA". What's wrong with "IEC958 Playback Volume"?
Next, quite a few drivers do not use the SNDRV_CTL_NAME_IEC958 macro, whose purpose I suppose is to ensure that alle IEC958 mixer controls follow a
common naming syntax. Anyway, alot of drivers for some reason uses "Output" and "Input" instead of "Playback" and "Capture". Is this on purpose?
The reason I make such a fuss about it, is that I wanted to make a structured organized mixer for GTK, so that people don't have to use the sometimes
messy and confusing alsamixer and gnome volume control (in general, all mixers based on the ALSA Simple Mixer controls). But then it struck me that
the simple mixer did have some potentional, and the chaos basically was based on poor sorting of elements (which you can do manually in your program),
its inability to detect several "new" mixer control names such as (Front,Rear,Side, etc.), and then the inability to have both a Switch and a Route
element with the same name (The ice1724 driver was force to use "IEC958 Output Switch" instead of "IEC958 Playback Switch" due to this).
It is my belief, that if the simple mixer library routines was updated, and the mixer elements got proper names, the world would be alot better.
But is this simple caused by programmers not truely knowing the ALSA naming conversion or is there some deper sence in this?
I did consider makine a patch which changed the whole naming thing, but it would probably be to vital for people to accept?!
Thanks
Peter Christensen
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next reply other threads:[~2004-11-27 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 9:26 Peter Christensen [this message]
2004-11-27 19:24 ` Mixer control names out of control? Lee Revell
2004-11-28 9:54 ` Sergey Vlasov
-- strict thread matches above, loose matches on Subject: below --
2004-11-28 9:00 Peter Zubaj
2004-11-28 16:00 ` Peter Christensen
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=41A84850.5000604@developers.dk \
--to=peter@developers.dk \
--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