All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Channel modes feature request.
Date: Tue, 12 Aug 2003 11:37:23 +0200	[thread overview]
Message-ID: <s5hvft3i5d8.wl@alsa2.suse.de> (raw)
In-Reply-To: <3F38B29E.3080906@superbug.demon.co.uk>

At Tue, 12 Aug 2003 10:25:50 +0100,
James Courtier-Dutton wrote:
> 
> Takashi Iwai wrote:
> > At Tue, 12 Aug 2003 00:19:34 +0100,
> > James Courtier-Dutton wrote:
> > 
> >>I have a SB live audio card.
> >>I can open it with device names like: -
> >>surround40 (Front Left, Front Right, Rear Left, Rear Right)
> >>surround51 (Front Left, Front Right, Rear Left, Rear Right, Center, LFE)
> >>
> >>There is a requirement for: -
> >>surround41 (Front Left, Front Right, Rear Left, Rear Right, LFE)
> >>surround50 (Front Left, Front Right, Rear Left, Rear Right, Center)
> >>
> >>How can I get alsa to support these ?
> > 
> > 
> > i still don't understand your question quite correctly.
> > 
> > do you mean open a multi-channel (5ch) pcm stream wihh the
> > configuration above?
> > if so, it's not too difficult for sb live (but not always easy for
> > other cards).  it would look like:
> 
> Can you expand on why. Because it seems sensible to me that all cards 
> that do surround51, can also do surround50 and surround41.

ok, so you mean a generic support for these formats.

> If by what you say, it is not possible (when I say not possible, I mean 
> not possible with adding extra memcpy's to move the channels around in 
> alsa-lib) , then I will adjust my application to use the surround51 pcm, 
> and just mute the un-needed channel.

well, after thinking a bit more, it turned out that it's easy to do
this in generic way (but with an overhead, of course).

e.g. surround41 can be derived from surround51 such as

pcm.surround41 {
	type route
	slave.pcm surround51
	ttable.0.0 1
	ttable.1.1 1
	ttable.2.2 1
	ttable.3.3 1
	ttable.4.5 1
}

we can define this as a default while the optimized version can be
defined in each card definition (as written in my previous post).


Takashi


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

  parent reply	other threads:[~2003-08-12  9:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11 23:19 Channel modes feature request James Courtier-Dutton
2003-08-12  9:12 ` Takashi Iwai
2003-08-12  9:25   ` James Courtier-Dutton
2003-08-12  9:32     ` Jaroslav Kysela
2003-08-12  9:37     ` Takashi Iwai [this message]
2003-08-12  9:40       ` Takashi Iwai

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=s5hvft3i5d8.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=James@superbug.demon.co.uk \
    --cc=alsa-devel@lists.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.