Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@attbi.com>
To: Thomas Charbonnel <thomas@undata.org>
Cc: Patrick Shirkey <pshirkey@boosthardware.com>,
	Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: hdsp multiface pci.
Date: 19 Jan 2003 08:23:11 +0000	[thread overview]
Message-ID: <1042964591.10196.4.camel@Godzilla> (raw)
In-Reply-To: <1042992464.1649.55.camel@satellite.undata.org>

On Sun, 2003-01-19 at 16:07, Thomas Charbonnel wrote:
> 
> So the "numid=5 26,26,16384" line says:
> connect software output 1 (called "playback" in the above table) to line
> out left, as the syntax of the call is input_source,output_source,value.
> 
Thomas,
   I have possibly more than a passing interest in this subject as I use
the HDSP 9652 card that Patrick mentioned and find this whole amixer
language completely unfathomable.

   In your quote above, could you outline what each parameter stands
for?

"numid=5 26,26,16384"

numid=5 - Is this a physical connection? A mixer input or output? An
abstract number just used to keep track of things?

26,26 - clearly Patrick and I were thinking that these two numbers
related to specific hardware inputs and outputs, but apparently not.

16384 - a mixer volume?

Thanks in advance for helping.

Cheers,
Mark




-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en

  reply	other threads:[~2003-01-19  8:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-19 12:08 hdsp multiface pci Patrick Shirkey
2003-01-19 14:12 ` Thomas Charbonnel
2003-01-19 15:29   ` Patrick Shirkey
2003-01-19 15:55     ` Patrick Shirkey
2003-01-19 16:07     ` Thomas Charbonnel
2003-01-19  8:23       ` Mark Knecht [this message]
2003-01-19 17:27         ` Thomas Charbonnel
2003-01-19 16:33       ` Patrick Shirkey
2003-01-19 17:00         ` Roger Williams
2003-01-19 12:21           ` Mark Knecht
2003-01-19 22:24             ` Roger Williams
2003-01-19 16:34               ` Mark Knecht
2003-01-20  2:14                 ` Roger Williams
2003-01-19 19:59                   ` Mark Knecht
2003-01-20  6:25                     ` Roger Williams
2003-01-20  5:06                       ` Mark Knecht
2003-01-20 13:46                         ` Roger Williams
2003-01-20  6:44                     ` Roger Williams
2003-01-20  8:31                       ` Marcus Andersson
2003-01-20 13:35                         ` Roger Williams
2003-01-19 17:01         ` Patrick Shirkey
2003-01-19 17:20         ` Thomas Charbonnel
2003-01-19 23:12           ` Roger Williams
  -- strict thread matches above, loose matches on Subject: below --
2003-01-20 15:57 markknecht
2003-01-20 16:12 markknecht
     [not found] <E18aeXp-00009y-00@sturgeon.coelacanth.com>
2003-01-20 17:01 ` Roger Williams
2003-01-22 18:19   ` Paul Davis
2003-01-22 18:30     ` Roger Williams
2003-01-22 18:41       ` Paul Davis
2003-01-22 18:54       ` Mark Knecht

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=1042964591.10196.4.camel@Godzilla \
    --to=markknecht@attbi.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pshirkey@boosthardware.com \
    --cc=thomas@undata.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox