From: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: Thomas Charbonnel <thomas@undata.org>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: hdsp multiface pci.
Date: Mon, 20 Jan 2003 02:01:08 +0900 [thread overview]
Message-ID: <3E2AD9D4.90900@boosthardware.com> (raw)
In-Reply-To: 3E2AD34D.6070308@boosthardware.com
Patrick Shirkey wrote:
> Thomas Charbonnel wrote:
>
>>
>>
>> You have to understand that software outputs are not directly related to
>> physical outputs. On simpler hardware, software and physical outputs can
>> be considered the same. On the hdsp system, thanks to the internal
>> matrix mixer, software outputs are totally abstracted from physical
>> ones. On the multiface you have 18 software outputs, each of wich can be
>> independently routed to any of the 18 physical outputs. For convenience,
>> the hdsp linux driver's default behaviour is to have a 1:1 routing
>> policy: each software output is by default routed to to corresponding
>> hardware output.
In essence the hdsp can run 18 software streams at the same time as
processing upto 18 hardware input streams?
Do I need to set the volume for the analog inputs? Or will I be able to
capture from them without setting anything in amixer?
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-01-19 17:01 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
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 [this message]
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=3E2AD9D4.90900@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@lists.sourceforge.net \
--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