From: MNTGE <mntge@indra.es>
To: kevine@esm.rochester.edu, Kevin Ernste <kevine88@yahoo.com>,
alsa-devel@alsa-project.org, alsa-user@alsa-project.org
Subject: Re: Hammerfall channel/device routing
Date: Thu, 4 Apr 2002 08:41:58 +0200 [thread overview]
Message-ID: <a8gt6j$mau$2@main.gmane.org> (raw)
In-Reply-To: <20020403015708.92522.qmail@web11503.mail.yahoo.com>
On Wed 03 Apr 2002 03:57, Kevin Ernste wrote:
> Hello -
>
> I am running a Hammerfall 9652 in Alsa 0.9beta11 (under Madrake 8.1) and
> I am
> looking for information about how to route to the varous output channels
> from
> the command line (say, with ecasoubd or aplay). Right now, sound goes
> to EVERY
> channel (8 ADAT channels, AND the coaxial/SPDIF stereo).
>
> I would like to be able to route sounds separately, as the ADAT channels
> go to
> an ADAT deck (limted to 48k), while the coaxial/SPDIF line goes to
> converters
> which can handle 96k. I would love to be able to do both.
You are suffering from an erroneous decision of ALSA team when it was changed
a feature of the PCM API (0.4 to 0.5 transition): file descriptors were
bounded up with channels, now is bounded up with cards.
Separate operation on multichannel card is easy at application level.
However, low-level operations (i.e. routing) for each channel at kernel level
is unnecessary complex.
Regards,
prev parent reply other threads:[~2002-04-04 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020402172302.22a135e1.mdeboer@iua.upf.es>
2002-04-03 1:57 ` Hammerfall channel/device routing Kevin Ernste
2002-04-03 16:17 ` Paul Davis
2002-04-04 6:41 ` MNTGE [this message]
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='a8gt6j$mau$2@main.gmane.org' \
--to=mntge@indra.es \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@alsa-project.org \
--cc=kevine88@yahoo.com \
--cc=kevine@esm.rochester.edu \
/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.