From: Rene Herman <rene.herman@keyaccess.nl>
To: van der Linden <ejvanderlinden@hetnet.nl>
Cc: alsa-devel@alsa-project.org
Subject: Re: arecord | aplay expected delay
Date: Sun, 16 Mar 2008 22:36:20 +0100 [thread overview]
Message-ID: <47DD92D4.3010102@keyaccess.nl> (raw)
In-Reply-To: <00d301c8874d$51773ea0$0202a8c0@uw4b58d8528225>
On 16-03-08 11:05, van der Linden wrote:
> I'm running arecord and aplay under uCLinux on a Blackfin DSP.
>
> In this way I loopback my audio.
>
> Does anyone know what delay I can expect between audio input and audio output?
Not me, but you just want to loop without doing anything to it? An analogue
input? Every card I know can just loop it's own inputs out again. That is,
In -> Out, while you have In -> ADC -> bus -> cpu/memory -> bus -> DAC -> Out.
> I measure at my test board 50ms. I want to have about 1ms!
You'd need a pretty fast system I suppose. Why does your card not loop
directly itself? You can still record it as well...
Rene
next prev parent reply other threads:[~2008-03-16 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 10:05 arecord | aplay expected delay van der Linden
2008-03-16 21:36 ` Rene Herman [this message]
2008-03-18 18:08 ` van der Linden
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=47DD92D4.3010102@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=ejvanderlinden@hetnet.nl \
/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