From: Nilhcraiv <nilhcraiv@gmail.com>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Clemens Ladisch <clemens@ladisch.de>
Subject: Re: Playback - Overwrite buffer with silence
Date: Wed, 22 Apr 2015 20:13:48 +0200 [thread overview]
Message-ID: <5537E4DC.4020708@gmail.com> (raw)
In-Reply-To: <CAN8cciasebtivM-4pD=G_MpfwvvLtDckeRq1KKwnbCsKHeX+Cw@mail.gmail.com>
Raymind wrote:
> Pulseaudio is a sound server which mix several playback streams,
> silence size may has no effect since the alsa sink may use different
> period size/buffer size or disable period wakeup when using timer
> scheduling
Then, How I can avoid under-run? I mean, If I attempt to write data in a
buffer and the under-run occurs, It takes a long time to recover the pcm
and the data must be lost. ¿how I can put silence in buffer instead of
lost data?
I have set the snd_pcm_sw_params_set_stop_threshold() to the boundary
value also, but the under-run occurs
My Playback PCM now:
INFO: Using "default" device.
ALSA <-> PulseAudio PCM I/O Plugin
Its setup is:
stream : PLAYBACK
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 16
buffer_size : 720
period_size : 240
period_time : 5000
tstamp_mode : NONE
period_step : 1
avail_min : 240
period_event : 0
start_threshold : 720
stop_threshold : 6485183463413514240
silence_threshold: 0
silence_size : 6485183463413514240
boundary : 6485183463413514240
Regards,
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2015-04-22 18:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 15:47 Playback - Overwrite buffer with silence Nilhcraiv
2015-04-11 20:05 ` Clemens Ladisch
[not found] ` <14caab5d6d0.2759.f6cded7c48a54b1428bcde82a72ee7d7@gmail.com>
2015-04-11 23:15 ` Nilhcraiv
2015-04-12 5:58 ` Clemens Ladisch
[not found] ` <14cb331e1c8.2759.f6cded7c48a54b1428bcde82a72ee7d7@gmail.com>
2015-04-13 14:45 ` Nilhcraiv
2015-04-14 12:37 ` Clemens Ladisch
2015-04-14 17:29 ` Nilhcraiv
2015-04-14 19:46 ` Clemens Ladisch
2015-04-15 3:14 ` Raymond Yau
[not found] ` <552EBB90.8040707@gmail.com>
2015-04-15 19:40 ` Clemens Ladisch
2015-04-16 18:32 ` Nilhcraiv
2015-04-16 20:16 ` Clemens Ladisch
2015-04-17 0:57 ` Raymond Yau
2015-04-22 18:13 ` Nilhcraiv [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=5537E4DC.4020708@gmail.com \
--to=nilhcraiv@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=superquad.vortex2@gmail.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