All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Florian Schmidt <mista.tapas@gmx.net>
Cc: alsa-user@lists.sourceforge.net, alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-user] copy pcm plugin
Date: Wed, 28 Jan 2004 18:37:32 +0100	[thread overview]
Message-ID: <s5hllns5603.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040128180546.4cc88584.mista.tapas@gmx.net>

At Wed, 28 Jan 2004 18:05:46 +0100,
Florian Schmidt wrote:
> 
> 
> Hi, as far as i understand it, the copy plugin does nothing but copy its
> input to its output. I wonder if it would be easily possible to extend
> this plugin to copy to multiple slave pcms. This way it would be
> (easily?) possible to "distribute" a stereo signal to 4 or even 6
> channels.

route (and plug) plugin already can do that.
for example,

pcm.ch40dup {
	type route
	slave.pcm surround40
	slave.channels 4
	ttable.0.0 1
	ttable.1.1 1
	ttable.0.2 1
	ttable.1.3 1
}

pcm.ch51dup {
	type route
	slave.pcm surround51
	slave.channels 6
	ttable.0.0 1
	ttable.1.1 1
	ttable.0.2 1
	ttable.1.3 1
	ttable.0.4 0.5
	ttable.1.4 0.5
	ttable.0.5 0.5
	ttable.1.5 0.5
}


and you can play two channel WAV like

	% aplay -Dch40dup 2ch-stereo.wav

	% aplay -Dch51dup 2ch-stereo.wav

for 4.0 and 5.1 surrounds, respectively.
of course, this is just copy of left/right samples, no dolby prologic 
effect is included ;)


Takashi


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  reply	other threads:[~2004-01-28 17:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28 17:05 copy pcm plugin Florian Schmidt
2004-01-28 17:37 ` Takashi Iwai [this message]
2004-01-28 19:02   ` [Alsa-devel] " Takashi Iwai
2004-01-28 21:30     ` Florian Schmidt
2004-01-28 18:46 ` [Alsa-devel] " Jaroslav Kysela

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=s5hllns5603.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=mista.tapas@gmx.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.