From: Takashi Iwai <tiwai@suse.de>
To: alsa-devel@lists.sourceforge.net
Cc: Tim Goetze <tim@quitte.de>
Subject: pcm_drain() behavior (Re: snd_pcm_close hangs)
Date: Mon, 24 Jun 2002 15:39:53 +0200 [thread overview]
Message-ID: <s5hlm9494nq.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0206181957020.820-100000@summer.quitte>
At Tue, 18 Jun 2002 20:23:50 +0200 (CEST),
Tim Goetze wrote:
>
> Takashi Iwai wrote:
>
> >well, draing samples at close corresponds to flushing the buffered
> >data to disk at fclose. then it sounds normal, doesn't it?
>
> i'm still not convinced -- if the stream is running when you close it,
> you're right, obviously.
>
> but when it's not running, starting and stopping it usually produces a
> click that will ruin the audible effect of the few msec worth of sound
> 'drained' (that nobody cares about anyway since the stream is about to
> be closed).
>
> right?
this is a question of behavior.
i don't think it's absolutely "wrong" that the driver processes the
rest of samples at stop status if drain() is called.
but.. from my feeling, i agree with you. it doesn't matter if the
samples are simply dropped at close() when its stream was already
stopped. so i myself would like to change this behavior.
the fix must be quite easy.
however, we need a consensus about this.
any comments (or objections)?
Takashi
-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
next parent reply other threads:[~2002-06-24 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s5h7kkwh5o2.wl@alsa2.suse.de>
[not found] ` <Pine.LNX.4.21.0206181957020.820-100000@summer.quitte>
2002-06-24 13:39 ` Takashi Iwai [this message]
2002-06-24 14:14 ` pcm_drain() behavior (Re: snd_pcm_close hangs) Paul Davis
2002-06-26 15:55 ` Jaroslav Kysela
2002-06-26 17:11 ` Takashi Iwai
2002-06-26 17:23 ` Jaroslav Kysela
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=s5hlm9494nq.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tim@quitte.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.