From: Mark Hills <mark@xwax.org>
To: alsa-devel@alsa-project.org
Subject: Audio artefacts but no xruns
Date: Sun, 2 Feb 2014 12:04:00 +0000 (GMT) [thread overview]
Message-ID: <1402021138000.29544@localhost> (raw)
Hi,
I have several applications for realtime processing of audio in/out, using
small buffer sizes.
I often find that I can get audible time-based distoritions, yet no xrun
is reported, and the application is unaware.
This problem is something I have, for a long time, taken for granted with
ALSA. But it doesn't seem right and I would like to understand what's
going on here.
I am testing using different USB audio devices; snd-usb-audio and
snd-usb-caiaq. Often using plughw or hw.
Is this some fundamental limitation of USB, that it is unaware of problems
nearer to the hardware?
Or is this some bug where it's worth me narrowing down a specific test
case and trying to fix it?
Or some limitation of the use of intermediate processing like plughw?
The effects range from occasional subtle clicks through ringing or
noticable gaps in the audio, on record or playback.
At very least I would like to guarantee a notification in userland that
the integrity of the recording or playback is affected.
This is particularly prevalent on, eg. Raspberry Pi. My other tests are on
x86 platforms.
Thanks
--
Mark
reply other threads:[~2014-02-02 12:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1402021138000.29544@localhost \
--to=mark@xwax.org \
--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.