All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eliot Blennerhassett <linux@audioscience.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Takashi Iwai <tiwai@suse.de>,
	ALSA Development Mailing List <alsa-devel@alsa-project.org>,
	Lennart Poettering <mznyfn@0pointer.de>
Subject: Re: Master vs. Front/Rear/LFE/... elements
Date: Fri, 08 May 2009 18:36:02 +1200	[thread overview]
Message-ID: <4A03D2D2.1040800@audioscience.com> (raw)
In-Reply-To: <20090507100915.GB27897@sirena.org.uk>

Mark Brown wrote:
> On Thu, May 07, 2009 at 10:49:22AM +0200, Takashi Iwai wrote:
> 
>> IMO, the best would be a total rewrite of the current mixer API, as I
>> mentioned some times.  Right now it's more complicated than needed,
>> but not powerful enough to handle exceptional cases.
> 
> Indeed - for example, something that allowed audio routing to be
> expressed in the mixing API would be a very big win for embedded systems
> too.
> 
>> I know designing a generic and fully-working API is pretty difficult,
>> though...
> 
> Certainly non-trivial :)

I just dumped my notes here on other systems that have some concept of
routing/connectivity/topology

http://bigblen.wordpress.com/2009/05/08/linux-audio-control-topology/

Comments welcome

Still very much a work in progress...

--
Eliot

  parent reply	other threads:[~2009-05-08  6:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06 17:58 Master vs. Front/Rear/LFE/... elements Lennart Poettering
2009-05-07  8:49 ` Takashi Iwai
2009-05-07 10:09   ` Mark Brown
2009-05-07 10:30     ` Takashi Iwai
2009-05-07 10:53       ` Mark Brown
2009-05-07 12:56       ` Lennart Poettering
2009-05-07 13:10         ` Mark Brown
2009-05-07 13:12         ` Pavel Hofman
2009-05-08  6:36     ` Eliot Blennerhassett [this message]
2009-05-07 12:46   ` Lennart Poettering
2009-05-07 13:18     ` Takashi Iwai
2009-05-09 22:11       ` Lennart Poettering
2009-05-11  9:26         ` Takashi Iwai
2009-05-12  7:47   ` James Courtier-Dutton
2009-05-12  8:02     ` Jaroslav Kysela
2009-05-12  9:21     ` Mark Brown
2009-05-12 13:15     ` Lennart Poettering

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=4A03D2D2.1040800@audioscience.com \
    --to=linux@audioscience.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    --cc=mznyfn@0pointer.de \
    --cc=tiwai@suse.de \
    /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.