From: Takashi Iwai Subject: Re: --separate-channels issues Date: Tue, 10 May 2011 18:40:49 +0200 Message-ID: References: <119279.84562.qm@web161712.mail.bf1.yahoo.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.suse.de (cantor.suse.de [195.135.220.2]) by alsa0.perex.cz (Postfix) with ESMTP id 03084244F7 for ; Tue, 10 May 2011 18:40:54 +0200 (CEST) In-Reply-To: <119279.84562.qm@web161712.mail.bf1.yahoo.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: hong zhang Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Tue, 10 May 2011 09:34:40 -0700 (PDT), hong zhang wrote: > > Takashi, > > When I run following commands with 2 pins inputs. > > $ arecord -f S16_LE -r 48000 -c 4 -D plughw:0,1 --separate-channels c1.wav c2.wav c3.wav c4.wav > > hd c3.wav and c4.wav returns 0 but c1.wav and c2.wav got right data. > Such as > $ hd c3.wav > 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| > * > 005ad000 Use hw:0,1 instead of plughw:0,1. If the hardware really supports the multi-channels, it should work in that way. I guess you didn't notice that the input is 2 channels because plughw covers it. > Also, I see trigger Rx start command and then stop command immediately. This sounds like a driver issue. Takashi