Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
To: alsa-devel@lists.sourceforge.net
Subject: quattro multi plugin.
Date: Fri, 19 Jul 2002 16:11:54 +0900	[thread overview]
Message-ID: <3D37BBBA.7030308@boosthardware.com> (raw)

I have had some luck with getting 4 channels to register using the multi 
plugin.

I have the following in .asoundrc.

----
pcm.quattro {
         type multi;

         slaves.a.pcm "hw:2,0";
         slaves.a.channels 3;


         bindings.0.slave a;
         bindings.0.channel 0;
         bindings.1.slave a;
         bindings.1.channel 1;
         bindings.2.slave a;
         bindings.2.channel 2;
	
}

ctl.quattro {
         type hw;
         card 0;
}

pcm.q4 {
         type route;
         slave.pcm "quattro";
         ttable.1.1 1;
         ttable.2.2 1;

}
----

When I run jackd I get this output though:

----
  jackd -v -d alsa -d q4
jackd 0.37.1
Copyright 2001-2002 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

611 waiting for signals
creating alsa driver ... q4|1024|2|48000|swmon
new client: alsa_pcm, id = 1 type 1 @ 0x8067930 fd = 14
port alsa_pcm:in_1 buf shm key 0x164398c5 at offset 4096 bi = 0x8066d00
registered port alsa_pcm:in_1, offset = 4096
port alsa_pcm:in_2 buf shm key 0x164398c5 at offset 8192 bi = 0x8066d10
registered port alsa_pcm:in_2, offset = 8192
port alsa_pcm:in_3 buf shm key 0x164398c5 at offset 12288 bi = 0x8066d20
registered port alsa_pcm:in_3, offset = 12288
port alsa_pcm:in_4 buf shm key 0x164398c5 at offset 16384 bi = 0x8066d30
registered port alsa_pcm:in_4, offset = 16384
registered port alsa_pcm:out_1, offset = 0
registered port alsa_pcm:out_2, offset = 0
registered port alsa_pcm:out_3, offset = 0
registered port alsa_pcm:out_4, offset = 0
-- jack_rechain_graph():
client alsa_pcm: inprocess client, execution_order=0.
ALSA: poll time out polled for 45558.694314
driver wait function failed, exiting
telling signal thread that the engine is done
jack main caught signal 1
----

-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

             reply	other threads:[~2002-07-19  7:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19  7:11 Patrick Shirkey [this message]
2002-07-19  8:42 ` quattro multi plugin Patrick Shirkey
2002-07-19 13:56   ` Patrick Shirkey
2002-07-19 17:51     ` Takashi Iwai
2002-07-19 23:44       ` Thorsten Haas
2002-07-20 16:09       ` Patrick Shirkey
2002-07-20 16:22         ` Patrick Shirkey
2002-07-20 16:41           ` Patrick Shirkey
2002-07-21  8:20         ` Jaroslav Kysela
2002-07-22  9:58           ` Patrick Shirkey
2002-07-22 11:10             ` Takashi Iwai
2002-07-22 11:21             ` Patrick Shirkey
2002-07-28  8:14               ` quattro multi plugin - 4 channel recording Patrick Shirkey

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=3D37BBBA.7030308@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox