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>
This commit is contained in:
Takashi Sakamoto 2019-01-27 14:39:18 +09:00 committed by Takashi Iwai
parent 83bce86c26
commit b6142611c6

View file

@ -872,6 +872,15 @@ according to pushed enter key. However, this feature requires an additional
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,