From: Anssi Hannula <anssi.hannula@iki.fi>
To: Xavier Claessens <xavier.claessens@collabora.com>,
alsa-devel@alsa-project.org
Subject: Re: Split a 7.1 device into 4 stereo devices
Date: Tue, 08 Jul 2014 21:26:37 +0300 [thread overview]
Message-ID: <53BC37DD.5060104@iki.fi> (raw)
In-Reply-To: <1404832691.13359.9.camel@X230>
08.07.2014 18:18, Xavier Claessens kirjoitti:
>
> Hello,
>
> I have a 7.1 sound device and speaker-test -c8 can output on each
> speaker. But what I would like to do is using it as 4 stereo devices so
> I could play different sounds on each of them.
>
> Ideally I would like to avoid dmix and friends to be able to have
> gapless and bit-perfect output.
>
> On IRC "debianuser" said it is possible with hdajackretask to make it
> appear as 4 different hw devices in "aplay -l" but we didn't succeed
> doing that. Anyone knows what configuration is needed for that?
>
> Here is my setting:
> http://www.alsa-project.org/db/?f=bf0744873d5e6d42d3adc0076c5f66189e9191b7
I guess this really belongs on alsa-user@ list, but oh well...
No idea about hdajackretask, but you can use e.g. "dshare" plugin.
Simple example below with 6ch split to three stereo devices, see
documentation/Google for more information on options. You don't see the
result in "aplay -l" but in "aplay -L".
pcm_slave.shared_dev {
pcm "hw:CARD=PCH,DEV=7"
channels 6
rate 48000
}
pcm.kas {
type dshare
ipc_key 119922141
slave shared_dev
bindings {
0 0
1 1
}
hint.description "Channels 0 and 1"
}
pcm.mo {
type dshare
ipc_key 119922141
slave shared_dev
bindings {
0 2
1 3
}
hint.description "Channels 2 and 3"
}
pcm.foobar {
type dshare
ipc_key 119922141
slave shared_dev
bindings {
0 4
1 5
}
hint.description "Channels 4 and 5"
}
--
Anssi Hannula
next prev parent reply other threads:[~2014-07-08 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 15:18 Split a 7.1 device into 4 stereo devices Xavier Claessens
2014-07-08 18:26 ` Anssi Hannula [this message]
2014-07-09 15:32 ` Raymond Yau
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=53BC37DD.5060104@iki.fi \
--to=anssi.hannula@iki.fi \
--cc=alsa-devel@alsa-project.org \
--cc=xavier.claessens@collabora.com \
/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.