From: Raymond Yau <superquad.vortex2@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: safe support for rewind in ALSA
Date: Thu, 11 Feb 2010 14:52:52 +0800 [thread overview]
Message-ID: <4f3252891002102252vb6d7a94l76fb78e33da37775@mail.gmail.com> (raw)
In-Reply-To: <4B72B665.3060903@ladisch.de>
2010/2/10 Clemens Ladisch <clemens@ladisch.de>
> Raymond Yau wrote:
> > ...
> > The rest of those sound cards which have period_mins = 1 are regarded as
> > broken by PA developer (e.g. intel8x0 ,emu10k1 , ens1371 , ... ) and
> aplay
> > did not work with one period per buffer too.
> >
> > what is the hardware requirement for the driver to support one period per
> > buffer ?
>
> That the hardware can be programmed to generate only one interrupt per
> buffer.
>
> > if none of the those driver can be fixed
> > why don't we change the period_min of all those broken drivers from 1 to
> 2
> > ?
>
> Because period_min has nothing to do with the brokenness. PA wants to
> use as few periods as possible because it does not use period interrupts
> but the DMA pointer, and it's the latter that is broken.
>
>
> Regards,
> Clemens
>
Are the one period per buffer designed for specific purpose such as
playing/looping the pre-loaded soundfont ?
Other than pulseaudio , are there any application use this mode properly
without glitch ?
Do you mean that PA only wake up once when configure sound card to use two
periods per buffer ?
if sound card only support non-interleaved mode and exactly two periods ,
even if you limit the rewind of application pointer to the period boundary
is not 100% safe if the sound card pre-fetch audio using DMA
Most sound cards hardware register only provide the number of sample
processed
next prev parent reply other threads:[~2010-02-11 6:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 17:20 safe support for rewind in ALSA pl bossart
2010-02-01 18:00 ` Jaroslav Kysela
2010-02-01 22:40 ` pl bossart
2010-02-03 2:20 ` Raymond Yau
2010-02-03 18:03 ` Kai Vehmanen
2010-02-03 20:52 ` Kai Vehmanen
2010-02-03 22:57 ` pl bossart
2010-02-08 1:22 ` Raymond Yau
2010-02-02 2:53 ` Raymond Yau
2010-02-06 11:59 ` Raymond Yau
2010-02-17 15:30 ` Lennart Poettering
2010-02-18 1:31 ` Raymond Yau
2010-02-18 2:33 ` Lennart Poettering
2010-02-18 3:21 ` Raymond Yau
2010-02-01 18:01 ` Mark Brown
2010-02-01 18:05 ` Jaroslav Kysela
2010-02-01 21:28 ` Kai Vehmanen
2010-02-01 21:54 ` Kai Vehmanen
2010-02-08 22:59 ` Raymond Yau
2010-02-09 20:54 ` Kai Vehmanen
2010-02-10 13:19 ` Raymond Yau
2010-02-10 13:36 ` Clemens Ladisch
2010-02-11 6:52 ` Raymond Yau [this message]
2010-02-11 7:20 ` Clemens Ladisch
2010-02-11 7:27 ` Jaroslav Kysela
2010-02-15 3:03 ` Raymond Yau
2010-02-17 15:46 ` Lennart Poettering
2010-02-21 10:35 ` Kai Vehmanen
2010-02-22 9:07 ` Raymond Yau
[not found] ` <20100221203500.GH31800@tango.0pointer.de>
2010-02-22 19:15 ` semantics of SNDRV_PCM_INFO_BATCH (was: Re: safe support for rewind in ALSA) Kai Vehmanen
2010-02-23 7:02 ` Raymond Yau
2010-02-23 2:37 ` safe support for rewind in ALSA Raymond Yau
2010-02-23 2:44 ` Raymond Yau
2010-02-17 15:42 ` Lennart Poettering
2010-02-21 10:06 ` Kai Vehmanen
[not found] ` <20100221202144.GG31800@tango.0pointer.de>
2010-05-04 2:31 ` Raymond Yau
2010-02-17 15:39 ` Lennart Poettering
2010-02-17 15:36 ` Lennart Poettering
2010-02-17 15:35 ` Lennart Poettering
2010-02-01 22:10 ` Kai Vehmanen
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=4f3252891002102252vb6d7a94l76fb78e33da37775@mail.gmail.com \
--to=superquad.vortex2@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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).