From: Clemens Ladisch <clemens@ladisch.de>
To: Till Crueger <Till.Crueger@gmx.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: Which transfer mode to use
Date: Wed, 14 Oct 2009 16:44:44 +0200 [thread overview]
Message-ID: <4AD5E3DC.5070701@ladisch.de> (raw)
In-Reply-To: <op.u1setrz8soui26@mail.gmx.net>
Till Crueger wrote:
> 1. Asynchronous callback:
> This method seems to be the best explained by all the tutorials I could
> find, so I am guessing this is the best choice for audio applications.
It's the worst choice; it isn't available on many devices, and the
asynchronous callback cannot do much because it might have interrupted
some non-reentrant function.
> 2. read/write:
> So far this seems the best choice.
Use it.
> For this however I would have to figure out after each polling, how
> much data can be written.
snd_pcm_avail()
> I found some concerns about differences in lattency between these
> three methods.
Those concerned have not measured; the latency is _exactly_ the same.
HTH
Clemens
prev parent reply other threads:[~2009-10-14 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 11:14 Which transfer mode to use Till Crueger
2009-10-14 14:44 ` Clemens Ladisch [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=4AD5E3DC.5070701@ladisch.de \
--to=clemens@ladisch.de \
--cc=Till.Crueger@gmx.net \
--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 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.