alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Radivoje Jovanovic <radivojejovanovic@gmail.com>
To: alsa-devel@alsa-project.org
Subject: trigger_stop and buffer overrun
Date: Thu, 18 Nov 2010 08:59:07 -0800	[thread overview]
Message-ID: <AANLkTi=vVFDbeLgoy-wRWtzOQanmBTLDLkoaxrUciJj9@mail.gmail.com> (raw)

Is there anu way to tell what is the last position in the buffer filled by
ALSA during the trigger stop callback? The hardware I have is playing sound
but if I turn the DMA off when trigger_stop is executed I will not hear the
end of the file at all. It seems to me that I would have to setup the
hardware to stop playing at the specific address.
On the other hand if I play longer sounds or a song I notice that the song
is skipping a lot and 1 minute sample is over in 20 seconds so it seems to
me that the buffer is overflowing. the pointer callback reads correctly the
current DMA position from the hardware so I am confused how the overflow
happens. Is there any other way ALSA tracks the position where to write the
data?
cheers

                 reply	other threads:[~2010-11-18 16:59 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='AANLkTi=vVFDbeLgoy-wRWtzOQanmBTLDLkoaxrUciJj9@mail.gmail.com' \
    --to=radivojejovanovic@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).