From: Christian Gruber <christian.gruber@voiceinterconnect.de>
To: alsa-devel@alsa-project.org
Subject: Buffer underrun in a not empty playback buffer
Date: Wed, 25 Jul 2012 08:33:05 +0200 [thread overview]
Message-ID: <500F9321.30305@voiceinterconnect.de> (raw)
I had a problem with an ALSA-driver, which causes an underrun in the playback stream
before the playback buffer was completely empty (snd_pcm_avail() < playback buffer size).
The driver developer told me, that this is correct, since for correct DMA transfer a
minimum buffer filling level is required.
Is this an allowed ALSA-driver behaviour or does the ALSA-driver developer has to hide all
DMA internals to the application developer so that an underrun just occurs, when the
playback buffer is empty? If yes, how can I get to know about the required minimum buffer
filling level before an underrun occurs?
Regards,
Christian
--
---------------------------------------------------------------
Dipl.-Ing. Christian Gruber
voiceINTERconnect GmbH
Ammonstraße 35
01067 Dresden
Germany
Tel.: +49 (0) 351 - 407 526 67
Fax.: +49 (0) 351 - 407 526 55
---------------------------------------------------------------
www.voiceinterconnect.de
... smart signal processing for electronic devices
Geschäftsführung: Eingetragen im Handelsregister:
Dr.-Ing. Diane Hirschfeld, Amtsgericht Dresden HRB 19466
Ludwig Linkenheil
next reply other threads:[~2012-07-25 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 6:33 Christian Gruber [this message]
2012-07-25 7:01 ` Buffer underrun in a not empty playback buffer Clemens Ladisch
2012-07-25 10:13 ` Christian Gruber
2012-07-25 10:41 ` Clemens Ladisch
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=500F9321.30305@voiceinterconnect.de \
--to=christian.gruber@voiceinterconnect.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.