alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Yang, Xiaotao (X.)" <xyang25@visteon.com>
Cc: mailing list <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] about pop chime on pcm api
Date: Mon, 09 Sep 2019 19:47:58 +0200	[thread overview]
Message-ID: <s5hwoeh9x9t.wl-tiwai@suse.de> (raw)
In-Reply-To: <AM6PR06MB49462A448954E689F9F87D37A7BD0@AM6PR06MB4946.eurprd06.prod.outlook.com>

On Fri, 30 Aug 2019 10:31:25 +0200,
Yang, Xiaotao (X.) wrote:
> 
> Hi:
>                Why should I call api<snd_pcm_close()> 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

      reply	other threads:[~2019-09-09 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30  8:31 [alsa-devel] about pop chime on pcm api Yang, Xiaotao (X.)
2019-09-09 17:47 ` Takashi Iwai [this message]

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=s5hwoeh9x9t.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=xyang25@visteon.com \
    /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;
as well as URLs for NNTP newsgroup(s).