From: Markus Korber <korbse@gmx.at>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: period_size and relation to number of samples
Date: Thu, 06 Sep 2007 16:30:17 +0200 [thread overview]
Message-ID: <46E00EF9.2070607@gmx.at> (raw)
In-Reply-To: <s5hsl5r6gwk.wl%tiwai@suse.de>
Takashi Iwai schrieb:
> At Thu, 06 Sep 2007 07:52:37 +0200,
> Markus Korber wrote:
>> [...]
>> Now, what is an application allowed to send and what not? For example,
>> could an application only send 1024 l/r samples and is the driver
>> responsible for buffering the data? Or must it obey the announced
>> period_size and *always* provide 2048 l/r samples?
>
> No, as mentioned, the app is free to send any size in general. When
> the period size is filled up, basically it's supposed to be playable.
> But, the procedure "fill the whole buffer then start" is the most
> robust way.
>
> The period size is the minimal chunk size that controls the poll
> frequency. So, it's natural to send in this size. It's no
> requirement but a common use case.
Thus, is it possible to buffer the data in ALSA before sending them to
the driver, in such a way, that the driver always receives period_size
samples, regardless of what the application sends to ALSA? And how
would I configure ALSA for such a setup?
Regards,
Markus Korber
next prev parent reply other threads:[~2007-09-06 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 5:52 period_size and relation to number of samples Markus Korber
2007-09-06 13:51 ` Takashi Iwai
2007-09-06 14:30 ` Markus Korber [this message]
2007-09-06 14:48 ` Takashi Iwai
2007-09-10 8:28 ` Markus Korber
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=46E00EF9.2070607@gmx.at \
--to=korbse@gmx.at \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.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.