From: Gustavo da Silva Serra <gustavo.serra@tet.com.br>
To: stan <ghjeold_i_mwee@cox.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: Still have choppy audio using 1.0.17
Date: Tue, 15 Jul 2008 08:56:21 -0300 [thread overview]
Message-ID: <487C9065.9080800@tet.com.br> (raw)
In-Reply-To: <487BF452.2090301@cox.net>
stan escreveu:
> Gustavo da Silva Serra wrote:
>
>> I have discovered something else. Choppy audio occurs when
>> snd_pcm_playback_silence, in pcm_lib.c, will silence the same period
>> than the capture pointer is pointing at. I am printing this variables
>> "ofs" in snd_pcm_playback_silence and what is returned from
>> snd_card_loopback_pointer when the substream is capture.
>>
>> How snd_pcm_playback_silence is supposed to work? Must it silence the
>> next period from the playback pointer? How is ensured that this
>> situation (ofs == capture pointer) does not happen with sound cards?
>>
>> Thanks ANY help... any...
>>
>>
> The way the API docs describe it the silence function
> fills the play buffer with a set amount of silence when
> the buffer has fewer than threshold frames to play.
> So, if your playback is running close to that
> threshold, it will be continuously injecting chunks of
> silence into the stream. That would certainly sound
> choppy. From the docs it sounds like the silence is
> always injected into the existing stream at the current
> pointer.
>
> Note: this is just from reading the docs. I haven't
> actually used this.
I don't know if the silence function snd_pcm_playback_silence is the
same from alsa library. It uses the threshold, but it is not clear for
me how. It seems that this function clears the buffer for the new stream
arriving, because, from time to time, it silences a whole period.
Thanks for the attention :)
next prev parent reply other threads:[~2008-07-15 11:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 20:04 Still have choppy audio using 1.0.17 Gustavo da Silva Serra
2008-06-18 18:24 ` Gustavo da Silva Serra
2008-06-18 19:44 ` Gustavo da Silva Serra
2008-06-19 13:01 ` Gustavo da Silva Serra
2008-06-20 19:07 ` Gustavo da Silva Serra
2008-06-25 11:24 ` Gustavo da Silva Serra
2008-06-25 16:06 ` Takashi Iwai
2008-06-25 18:34 ` Gustavo da Silva Serra
2008-07-01 18:28 ` Gustavo da Silva Serra
2008-07-04 12:40 ` Gustavo da Silva Serra
2008-07-14 17:57 ` Gustavo da Silva Serra
2008-07-15 0:50 ` stan
2008-07-15 11:56 ` Gustavo da Silva Serra [this message]
2008-07-15 18:40 ` Gustavo da Silva Serra
2008-07-15 21:31 ` stan
2008-07-16 14:19 ` Gustavo da Silva Serra
2008-07-16 15:30 ` Takashi Iwai
2008-07-16 15:43 ` Gustavo da Silva Serra
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=487C9065.9080800@tet.com.br \
--to=gustavo.serra@tet.com.br \
--cc=alsa-devel@alsa-project.org \
--cc=ghjeold_i_mwee@cox.net \
/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.