From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: tomasz motylewski <T.Motylewski@bfad.de>
Cc: Jaroslav Kysela <perex@suse.cz>,
Paul Davis <paul@linuxaudiosystems.com>,
Florian Bomers <Florian.Bomers@sun.com>,
"alsa-devel@lists.sourceforge.net"
<alsa-devel@lists.sourceforge.net>
Subject: Re: smix plugin available?
Date: Thu, 28 Nov 2002 00:21:15 +1100 [thread overview]
Message-ID: <3DE4C6CB.8020407@superbug.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0211271149000.2146-100000@mailserver.intern.bfad.de>
tomasz motylewski wrote:
>Please stop the complication of "available/delay" etc. Just the raw pointer.
>Each application knows where its application pointer is, so it can easily
>calculate delay/available and decide for itself whether there was an overrun or
>not.
>
>
>
I use the delay() function.
I help write a multi media application that needs to sync audio to video.
So the question I ask alsa-lib is "If I write() now, how long will it be
before those samples come out of the speakers?"
So, I very much need delay(), but I also use available so that I can
program alsa when to exit the snd_pcm_wait() poll. I.E. Only exit the
snd_pcm_wait when there are enough free space in the buffer for me to
bother with a new write() call.
Cheers
James
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
next prev parent reply other threads:[~2002-11-27 13:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 1:16 smix plugin available? Mark Swanson
2002-11-26 3:19 ` Paul Davis
2002-11-26 3:54 ` Mark Swanson
2002-11-26 4:13 ` Paul Davis
2002-11-26 8:13 ` Frans Ketelaars
2002-11-26 12:33 ` Mark Swanson
2002-11-26 19:32 ` Florian Bomers
2002-11-26 23:11 ` Paul Davis
2002-11-27 0:54 ` Florian Bomers
2002-11-27 1:06 ` James Courtier-Dutton
2002-11-27 9:29 ` Jaroslav Kysela
2002-11-27 11:36 ` tomasz motylewski
2002-11-27 13:21 ` James Courtier-Dutton [this message]
2002-11-27 13:53 ` Paul Davis
2002-11-27 14:24 ` Jaroslav Kysela
2002-11-27 13:07 ` Avoiding xruns... was " James Courtier-Dutton
2002-11-27 13:55 ` Paul Davis
2002-11-27 13:42 ` Paul Davis
2002-11-27 15:21 ` Kai Vehmanen
2002-11-27 16:26 ` Jaroslav Kysela
2002-11-27 13:45 ` Paul Davis
2002-11-27 14:39 ` Jaroslav Kysela
[not found] <20021127135012.7B5A559D353@kerberos.suse.cz>
2002-11-27 14:43 ` Jaroslav Kysela
2002-11-27 15:04 ` Paul Davis
[not found] <200211271350.OAA22613@mail.bodensee.com>
2002-11-27 15:47 ` tomasz motylewski
2002-11-28 13:50 ` Paul Davis
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=3DE4C6CB.8020407@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=Florian.Bomers@sun.com \
--cc=T.Motylewski@bfad.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.com \
--cc=perex@suse.cz \
/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