All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Davis <paul@linuxaudiosystems.com>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: pavans@india.ti.com, alsa-devel@lists.sourceforge.net
Subject: Re: List of control parameters needed
Date: Mon, 22 Mar 2004 12:19:04 -0500	[thread overview]
Message-ID: <200403221719.i2MHJ4w6000838@dhin.linuxaudiosystems.com> (raw)
In-Reply-To: Your message of "Mon, 22 Mar 2004 15:24:45 GMT." <405F053D.2040801@superbug.demon.co.uk>

>> Where can I get the complete list of controls which an audio codec has to
>> support.

there is no such list.

and lets get the terminology straightened out here before this goes
any further.

"codec" comes (in this context) from "coder/decoder". that maps
roughly to what is more properly referred to as an analog-to-digital
or digital-to-analog converter (or both). these days, it could also
include devices that convert from one digital format (e.g. ADAT
LightPipe) to another (e.g. S/PDIF or T/DIF). 

thus, the list you offered actually to do with audio codecs, but is in
fact a description of the types of controls you might find on a
*mixer*.

however, given that there are cards without a mixer at all, plus cards
with radically different mixer designs, plus cards with extremely
simple mixers plus cards with extremely complex designs, there cannot
be a list of controls that any mixer will support. Even the idea of a
microphone input is h/w specific, as is the idea of a master volume
control. 

the best you could probably hope for is to first see if the mixer you
have has support for a "standard mixer API", then use that API. but no
such API exists at this time, and you would still have to have a
fallback position if you are using h/w that has no mixer or a mixer
than cannot support a "standard mixer API".

--p


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-03-22 17:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-22 11:16 List of control parameters needed Pavana Sharma
2004-03-22 11:52 ` Giuliano Pochini
2004-03-22 15:24 ` James Courtier-Dutton
2004-03-22 17:19   ` Paul Davis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-22 11:35 p z oooo

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=200403221719.i2MHJ4w6000838@dhin.linuxaudiosystems.com \
    --to=paul@linuxaudiosystems.com \
    --cc=James@superbug.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pavans@india.ti.com \
    /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.