From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: [Question] Different routing + sample formats for input and output
Date: Mon, 17 May 2021 04:42:20 +0200 (CEST) [thread overview]
Message-ID: <20210517024220.106F3F8012C@alsa1.perex.cz> (raw)
In-Reply-To: <1621219337408587933-webhooks-bot@alsa-project.org>
alsa-project/alsa-lib issue #135 was edited from flatmax:
One soundcard I use has different output and input sample formats. The input format is S32_LE. The output format is S24_3LE.
There is also a routing change I like to do.
My current .asoundrc (below) uses the asym plugin to manage input and output difference. The asym plugin creates problems for some unknown reason where I get overruns :
`ALSA lib pcm.c:8545:(snd_pcm_recover) overrun occurred`
If I switch my setup to using the soundcard for output and a second USB microphone for input, then I don't get any overruns. I still use the asym plugin to make it work and it works nicely.
I have also tried simply the plug pluging, however I still get overruns.
Is there any way to setup the one soundcard with routing and format changes without using the asym plugin ? Or is there a better way to setup the one soundcard with the required routing and format changes ?
```
########## BEGIN ~/.asoundrc ###################
@hooks [
{
func load
files [
"~/.asoundrc"
]
errors false
}
]
pcm.!default {
type asym
playback.pcm "UMC1820_12ch_play"
capture.pcm "UMC1820_10ch_capt"
}
ctl.!default {
type hw
card "UMC1820_8ch"
}
pcm.UMC1820_12ch_play {
type route;
slave.pcm "hw:UMC1820";
slave.format S24_3LE;
slave.channels 12;
ttable.0.2 1
ttable.1.3 1
ttable.2.4 1
ttable.3.5 1
ttable.4.6 1
ttable.5.7 1
ttable.6.8 1
ttable.7.9 1
ttable.8.10 1
ttable.9.11 1
ttable.10.0 1
ttable.11.1 1
}
pcm.UMC1820_10ch_capt {
type route;
slave.pcm "hw:UMC1820";
slave.format S32_LE;
slave.channels 10;
ttable.0.0 1
ttable.1.1 1
ttable.2.2 1
ttable.3.3 1
ttable.4.4 1
ttable.5.5 1
ttable.6.6 1
ttable.7.7 1
ttable.8.8 1
ttable.9.9 1
}
########## END ~/.asoundrc ###################
```
Issue URL : https://github.com/alsa-project/alsa-lib/issues/135
Repository URL: https://github.com/alsa-project/alsa-lib
next parent reply other threads:[~2021-05-17 2:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1621219337408587933-webhooks-bot@alsa-project.org>
2021-05-17 2:42 ` GitHub issues - edited [this message]
[not found] <1621219379998601913-webhooks-bot@alsa-project.org>
2021-05-17 2:43 ` [Question] Different routing + sample formats for input and output GitHub issues - edited
[not found] <1621219286014741898-webhooks-bot@alsa-project.org>
2021-05-17 2:41 ` GitHub issues - opened
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=20210517024220.106F3F8012C@alsa1.perex.cz \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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