All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Williams <raw@qux.com>
To: Mark Knecht <markknecht@attbi.com>
Cc: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: hdsp multiface pci.
Date: 19 Jan 2003 17:24:53 -0500	[thread overview]
Message-ID: <m3ptqskcay.fsf@grouper.coelacanth.com> (raw)
In-Reply-To: 1042978893.1341.108.camel@Godzilla

>>>>> Mark Knecht <markknecht@attbi.com> writes:

  >> amixer cset numid=5 26,26,16384
  >> amixer cset numid=5 28,26,16384
  >> amixer cset numid=5 30,26,16384
  >> amixer cset numid=5 32,26,16384
  >> amixer cset numid=5 27,27,16384
  >> amixer cset numid=5 29,27,16384
  >> amixer cset numid=5 31,27,16384
  >> amixer cset numid=5 33,27,16384

  > ... is the use of 26 and 27 on the output part of the command
  > telling the hardware to route whatever it is that you're mixing to
  > the line out connectors on your box?

Yes.  (Not outputs 1 & 2, as I erroneously stated.)

  > Second, where do the inputs numbered 26-33 come from.

As far as the Multiface's analogue I/O goes, channels appear to be
numbered like this:

Multiface inputs 1-8               = amixer source channels 0-7
Multiface outputs 1-8              = amixer destination channels 0-7
Multiface line (headphone) outputs = amixer destination channels 26-27
alsa_pcm:playback_1-8              = amixer source channels 26-33

So amixer cset numid=5 0,26,16384" routes the signal from input 0 to
the left headphone channel.  And "amixer cset numid=5 0,0,16384"
routes the signal from input 0 to output 0.  And

    for i in 0 2 4 6; do amixer cset numid=5 $i,0,16384; done
    for i in 1 3 5 7; do amixer cset numid=5 $i,1,16384; done

will route inputs 1+3+5+7 to output 1, and inputs 2+4+6+8 to output 2.

On playback "amixer cset numid=5 26,0,16384" routes the playback_1
source to Multiface output 1, and

    for i in 26 28 30 32; do amixer cset numid=5 $i,0,16384; done
    for i in 27 29 31 33; do amixer cset numid=5 $i,1,16384; done

routes playback_1+3+5+7 to output 1 and playback_2+4+6+8 to output 2.

  > I presume that your use of 16384 is to reduce volume so that after
  > summing 4 channels you do not create output clipping if all the inputs
  > hit maximum volume at the same time?

Yes.  This is just a submix for headphone monitoring, so I route it to
outputs 26 and 27.  This is a monitor submix I use when recording with
ecasound.  If I were using Ardour, I'd set up a monitor submix in
Ardour itself, and route outputs 1 and 2 to the headphone output with

    amixer cset numid=5 26,26,65535
    amixer cset numid=5 27,27,65535

  > If you wanted to route input 0 directly to an output, could
  > you use a command like:

  > amixer cset numid=5 0,26,16384
  > amixer cset numid=5 1,27,16384

This routes hardware inputs 1 and 2 to the headphone outputs.

-- 
Roger Williams <raw@qux.com>
Qux Tool & Die, Middleborough, Massachusetts
// Omne tulit punctum qui misquit utile dulci //


-------------------------------------------------------
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 22:24 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
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 [this message]
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=m3ptqskcay.fsf@grouper.coelacanth.com \
    --to=raw@qux.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=markknecht@attbi.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.