summaryrefslogtreecommitdiff
path: root/axfer
diff options
context:
space:
mode:
authorTakashi Sakamoto <o-takashi@sakamocchi.jp>2019-01-27 14:39:18 +0900
committerTakashi Iwai <tiwai@suse.de>2019-01-29 16:43:24 +0100
commitb6142611c68a380644ce34f885e2d67da084b538 (patch)
treeb31eecba24f8e509fc625ebfbf5fde38d2a3d378 /axfer
parent83bce86c26be6c04bcef584fbe00f320b3582c92 (diff)
downloadalsa-utils-b6142611c68a380644ce34f885e2d67da084b538.tar.gz
axfer: fulfill section for backward compatibitity for chmap option
At present, axfer losts backward compatibility to aplay in a point of 'chmap' option. This commit filfills a section to describe lose of backward compatibility of chmap option. Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp> Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'axfer')
-rw-r--r--axfer/axfer-transfer.19
1 files changed, 9 insertions, 0 deletions
diff --git a/axfer/axfer-transfer.1 b/axfer/axfer-transfer.1
index 02e5b4c..1fdfc91 100644
--- a/axfer/axfer-transfer.1
+++ b/axfer/axfer-transfer.1
@@ -873,6 +873,15 @@ input handling in main loop and leave bothersome operation to maintain PCM
substream.
.TP
+.I \-m, \-\-chmap=CH1,CH2,...
+ALSA PCM core and control core doesn't support this feature, therefore
+remapping should be done in userspace. This brings overhead to align audio
+data frames, especially for mmap operation. Furthermore, as of alsa-lib v1.1.8,
+some plugins don't support this feature expectedly, thus this option is a lack
+of transparent operation. At present, this option is not supported yet not to
+confuse users.
+
+.TP
.I SIGTSTP, SIGCONT
This performs suspend/resume of PCM substream. In aplay(1) implementation,
these operations bring XRUN state to the substream, and suspend/resume is done