All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <ossman@cendio.se>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Non-continous channel map?
Date: Wed, 03 May 2006 16:00:55 +0200	[thread overview]
Message-ID: <4458B797.5000103@cendio.se> (raw)
In-Reply-To: <s5hd5evgtbw.wl%tiwai@suse.de>

Takashi Iwai wrote:
> 
> I vote for (b).  The method is simple enough.

Ok. I'll start implementing that then. :)

> 
> Does the server-side configuration change on the fly, or the setup is
> fixed once after the server-client connection is established?

Yes and no. A back end specifies its channel map during creation, so 
it's static during its lifetime. But we identify the back end using a 
name, so it is possible that "our" back end could get removed and 
another loaded with the same name.

It is possible to get notifications when this happens though, so we can 
handle this gracefully.

> In theory, ALSA controls can dynamically added/removed.  But this may
> rather confuse some applications that don't support the dynamic change
> of control elements.

Something that Polypaudio itself is probably guilty of. ;)

Rgds
-- 
Pierre Ossman                Telephone: +46-13-21 46 00
Cendio AB                    Web: http://www.cendio.com


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

      reply	other threads:[~2006-05-03 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27  5:52 Non-continous channel map? Pierre Ossman
2006-05-03 12:06 ` Clemens Ladisch
2006-05-03 12:43   ` Pierre Ossman
2006-05-03 12:52     ` Takashi Iwai
2006-05-03 12:56 ` Takashi Iwai
2006-05-03 14:00   ` Pierre Ossman [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=4458B797.5000103@cendio.se \
    --to=ossman@cendio.se \
    --cc=alsa-devel@alsa-project.org \
    --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.