From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6DEDDC4740C for ; Mon, 9 Sep 2019 17:48:57 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E19F221924 for ; Mon, 9 Sep 2019 17:48:56 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="SZSRg3nE" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E19F221924 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id D399515F9; Mon, 9 Sep 2019 19:48:04 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz D399515F9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1568051334; bh=ucPOKc9uNdZbANrcG5NPzJlbdLywT/0snosFbVz6nnI=; h=Date:From:To:In-Reply-To:References:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=SZSRg3nElXqP12brqQKU4z29IcwEeIbwL7GSZdK+7sKF22UkSOn7l6rHOnnBRMBpb 7UI7xZ5+s1T3Il/AuRvi+KXuZkgAzKpC8bVqefz5KhSXMPdRv/W7wmG/OOHb2pDSDO 5+LRRhA/zpl3eRoJUBY9yUFNO1GOB2HN+xXDPXsU= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 54CF1F800A9; Mon, 9 Sep 2019 19:48:04 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 415ACF80323; Mon, 9 Sep 2019 19:48:02 +0200 (CEST) Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id A4572F800A9 for ; Mon, 9 Sep 2019 19:47:59 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz A4572F800A9 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 9EC4BAF2B; Mon, 9 Sep 2019 17:47:58 +0000 (UTC) Date: Mon, 09 Sep 2019 19:47:58 +0200 Message-ID: From: Takashi Iwai To: "Yang, Xiaotao (X.)" In-Reply-To: References: User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Cc: mailing list Subject: Re: [alsa-devel] about pop chime on pcm api X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Fri, 30 Aug 2019 10:31:25 +0200, Yang, Xiaotao (X.) wrote: > > Hi: > Why should I call api between the interval if I want to play a wav file two times repeatly, Otherwise pop chime occurs? > > Eg: (fake code as follows): > Following codes works good. > Pcm.open();//open pcm device > Pcm.play(demo.wav);//set parameter and call snd_pcm_writei() to play > Pcm.close();//close pcm device > Pcm.open(); > Pcm.play(demo.wav); > Pcm.close(); > > But following codes works with pop chime > Pcm.open(); > Pcm.play(demo.wav); > Pcm.play(demo.wav); > Pcm.close(); It's not clear what "pop chime" means, so a bit hard to answer. If the pop chime means some clicking noise, it shouldn't be a problem in the second case, either. It's more likely some issues in the application side. Takashi > _______________________________________________ > Alsa-devel mailing list > Alsa-devel@alsa-project.org > https://mailman.alsa-project.org/mailman/listinfo/alsa-devel > _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel