From: Takashi Iwai <tiwai@suse.de>
To: Joern Nettingsmeier <nettings@folkwang-hochschule.de>
Cc: "alsa-devel@lists.sourceforge.net"
<alsa-devel@lists.sourceforge.net>,
jackit-devel <jackit-devel@lists.sourceforge.net>
Subject: Re: [Alsa-devel] sblive 4ch output w/ jack - asoundrc magic?
Date: Thu, 05 Feb 2004 16:02:45 +0100 [thread overview]
Message-ID: <s5had3xa7sa.wl@alsa2.suse.de> (raw)
In-Reply-To: <40217B62.5020604@folkwang-hochschule.de>
At Thu, 05 Feb 2004 00:08:18 +0100,
Joern Nettingsmeier wrote:
>
> [crossposted to alsa-devel and jackit-devel]
>
> hi *!
>
> i'd like to use the rear outs of my sblive platinum with jack.
>
> the following works:
> # aplay some.wav -Dfront &
> # aplay someother.wav -Drear
> both signals end up at my mixer as expected, so it seems the devices
> are independent.
>
> front is hw:0,0 which is a duplex device.
> rear is hw:0,3 and is playback only.
hmm? hw:0,3 isn't for the rear output...
there is already a standard definition for 4.0 output, "surround40".
so, something like below would be better:
ctl.jtest {
type hw
card 0
}
pcm.jtest {
type asym
playback.pcm {
# route for mmap workaround
type route
slave.pcm surround40
ttable.0.0 1
ttable.1.1 1
ttable.2.2 1
ttable.3.3 1
}
capture.pcm {
# 2 channels only
type hw
card 0
}
}
and run jack with -d jtest -i 2 -o 6 options.
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
next prev parent reply other threads:[~2004-02-05 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 23:08 sblive 4ch output w/ jack - asoundrc magic? Joern Nettingsmeier
2004-02-05 15:02 ` Takashi Iwai [this message]
2004-02-05 19:10 ` [Alsa-devel] " Joern Nettingsmeier
2004-02-05 19:26 ` Joern Nettingsmeier
2004-02-06 11:42 ` Takashi Iwai
2004-02-07 10:56 ` Joern Nettingsmeier
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=s5had3xa7sa.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=jackit-devel@lists.sourceforge.net \
--cc=nettings@folkwang-hochschule.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.