From: Manuel Jander <manuel.jander@usm.cl>
To: andi@lisas.de, alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: The ALSA Situation
Date: Fri, 12 Nov 2004 10:33:58 -0300 [thread overview]
Message-ID: <1100266438.2082.6.camel@localhost> (raw)
In-Reply-To: <20041112082446.GA16172@rhlx01.fht-esslingen.de>
Hi,
On Fri, 2004-11-12 at 09:24 +0100, Andreas Mohr wrote:
> Hi,
> > 2) * Multichannel card:
> > - Use one channel for softmixing (reserved for ever for that purpose,
> > at highest audio quality). Just the same as for the single channel card.
> > - Use a "Resource Manager" that assigns hardware channels as are
> > available, and choose the softmixing engine coupled to the reserved
> > channel when we get out of hardware channels.
>
> Don't we have a problem here??
>
> If we have 4 hardware-mixed channels and 7 sound streams, then we end
> up with:
> a) H/W (1/4)
> b) H/W (1/4)
> c) H/W (1/4)
> d) H/W (1/4): S/W (1/4), S/W (1/4), S/W (1/4), S/W (1/4)
> == (!!)
> d) H/W (1/4) * S/W (1/4) each == S/W (1/16) each !!
>
> which clearly has a different volume (1/16 of total output) than each
> of the H/W-mix-only channels (1/4).
>
> Hmm, OTOH there's a 150% likelihood that the card can adjust hardware
> channel volume individually, so just adjust channel d) to have 4 times
> the volume of each other H/W channel and you end up with equal volume.
>
> OK, so that should be a non-issue after all (but we need to remember to
> adjust H/W channel volume each time the number of S/W channels changes!),
OK, there maybe some details, but that it absolutely irrelevant, because
it *can* be solved. The really import thing here IMHO is to solve the
concurrent access to the soundcard in a most useful manner, which is an
issue that is *not* solved yet.
--
Manuel Jander
Electronic Engineer
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next prev parent reply other threads:[~2004-11-12 13:33 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041112040611.8390B1D2669@sc8-sf-uberspam1.sourceforge.net>
2004-11-12 8:24 ` The ALSA Situation Andreas Mohr
2004-11-12 13:33 ` Manuel Jander [this message]
2004-11-12 15:06 ` Clemens Ladisch
[not found] <20041110235502.6C8211D2B2D@sc8-sf-uberspam1.sourceforge.net>
2004-11-11 8:56 ` Andreas Mohr
2004-11-11 15:50 ` Manuel Jander
2004-11-10 0:24 Eugenia Loli-Queru
2004-11-10 1:50 ` Paul Davis
2004-11-10 2:38 ` Eugenia Loli-Queru
2004-11-10 2:55 ` Paul Davis
2004-11-10 5:59 ` Lee Revell
2004-11-10 23:22 ` James Courtier-Dutton
2004-11-10 10:57 ` Jaroslav Kysela
2004-11-10 16:09 ` Lee Revell
2004-11-10 16:43 ` Linus Torvalds
2004-11-10 17:30 ` Takashi Iwai
2004-11-10 18:08 ` Linus Torvalds
2004-11-10 17:45 ` Jaroslav Kysela
2004-11-10 18:15 ` Linus Torvalds
2004-11-10 18:41 ` Paul Davis
2004-11-10 19:09 ` Linus Torvalds
2004-11-10 21:13 ` Paul Davis
2004-11-10 22:34 ` Linus Torvalds
2004-11-10 23:53 ` Fernando Pablo Lopez-Lezcano
2004-11-11 6:32 ` Jaroslav Kysela
2004-11-11 6:42 ` Linus Torvalds
2004-11-11 16:34 ` Takashi Iwai
2004-11-11 16:58 ` Linus Torvalds
2004-11-11 17:25 ` Takashi Iwai
2004-11-11 18:23 ` Linus Torvalds
2004-11-11 22:34 ` Manuel Jander
2004-11-12 8:57 ` Takashi Iwai
2004-11-12 8:51 ` Takashi Iwai
2004-11-12 15:50 ` Linus Torvalds
2004-11-12 22:06 ` Florian Schmidt
2004-11-13 1:15 ` Manuel Jander
2004-11-13 10:38 ` Jaroslav Kysela
2004-11-14 4:00 ` Manuel Jander
2004-11-13 10:42 ` Jaroslav Kysela
2004-11-13 12:11 ` Florian Schmidt
2004-11-13 18:01 ` Linus Torvalds
2004-12-02 1:48 ` Florian Schmidt
2004-11-12 9:07 ` Giuliano Pochini
2004-11-11 22:52 ` Manuel Jander
2004-11-12 13:44 ` Takashi Iwai
2004-11-10 22:00 ` Hannu Savolainen
2004-11-10 17:13 ` Giuliano Pochini
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=1100266438.2082.6.camel@localhost \
--to=manuel.jander@usm.cl \
--cc=alsa-devel@lists.sourceforge.net \
--cc=andi@lisas.de \
--cc=mjander@users.sourceforge.net \
/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.