From: Clemens Ladisch <clemens@ladisch.de>
To: alsa-devel@alsa-project.org
Subject: Re: Interleaved or Non-interleaved?
Date: Thu, 18 Oct 2012 11:11:47 +0200 [thread overview]
Message-ID: <507FC7D3.4050200@ladisch.de> (raw)
In-Reply-To: <CAA2DH4sexxhLRRZzA6_-nFbY2P+VBLXX_aqcb6u5=13NJAKTaQ@mail.gmail.com>
Prasant J wrote:
> My sound hardware supports only interleaved audio.
>
> I'm writing an alsa application. Which access method will be more
> performing : interleaved or non-interleaved?
With interleaved, samples can be copied from/to your application's
buffer in one big block. With non-interleaved, samples must be
copied individually.
Regards,
Clemens
next prev parent reply other threads:[~2012-10-18 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 8:34 Interleaved or Non-interleaved? Prasant J
2012-10-18 9:11 ` Clemens Ladisch [this message]
2012-10-18 9:57 ` Prasant J
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=507FC7D3.4050200@ladisch.de \
--to=clemens@ladisch.de \
--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.