Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Christensen <peter@developers.dk>
To: Peter Zubaj <pzad@pobox.sk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Mixer control names out of control?
Date: Sun, 28 Nov 2004 17:00:42 +0100	[thread overview]
Message-ID: <41A9F62A.9080105@developers.dk> (raw)
In-Reply-To: <200411280900.iAS90NIP014838@www4.pobox.sk>

Oh, I didn't know that about SPSA, but it does make quite some sence, as I don't see why one would have volume control on IEC958 :p. But wouldn't it 
then be more correct to use an enumerated control instead of integer?

But as of simple mixer element vs. kernel mixer controls, I am fully aware, that they are not the same thing. However, the simple elements are 
generated by the ALSA library based on the names of the mixer controls. But the library basically only recognized the names listed in 
Documentation/ControlNames.txt when it sorts the simple elements, which means that elements such as Front, Rear and Side are placed almost last on my 
Aureon card, between lots of unrelated elements.
It would be nice if the library did so good a sort, so that you would have the master playback volumes together 
(Master,Front,Rear,Side,Center,LFE,Surround, etc.), the source volumes together (PCM,Wave,Line,CD,Mic,Aux,Phone,AC97,Video,PC Speaker, etc.), and the 
IEC958 controls together. And it would be very nice if the simple mixer API had a fuction to tell wether the element was actually read-only. The 
ICE1724 driver have some sort VU meter or something, which the simple mixers think are ordinary volume controls, although they're read-only.

Peter Christensen

Peter Zubaj wrote:
>>First of all, the AC97 driver uses the name "IEC958 Playback SPSA".
> 
> What's wrong with "IEC958 Playback Volume"?
> 
> IEC958 Playback SPSA - this is not volume - this controls what AC97
> slot will be used for spdif output.
> 
> AFAIK
> simple mixer element != kernel mixer control. simple mixer element can
> containd 6 kernel controls (mayby more):
> Playback Volume
> Playback Switch
> Playback Route
> 
> Capture Volume
> Capture Switch
> Capture Route
> 
> 
>>Front,Rear,Side
> 
> I think there is not constraint on names, there is only recomendation.
> On some cards you are unable to fit to default names, because you want
> name something what has diffrent meaning as control on other card.
> Have you better names for this ?
> 
> Peter Zubaj
> ____________________________________
> http://www.pobox.sk/ - najvacsi slovensky freemail
> 
> 
> 
> 



-------------------------------------------------------
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/

  reply	other threads:[~2004-11-28 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-28  9:00 Mixer control names out of control? Peter Zubaj
2004-11-28 16:00 ` Peter Christensen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-27  9:26 Peter Christensen
2004-11-27 19:24 ` Lee Revell
2004-11-28  9:54 ` Sergey Vlasov

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=41A9F62A.9080105@developers.dk \
    --to=peter@developers.dk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pzad@pobox.sk \
    /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