All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: VDR User <user.vdr@gmail.com>
Cc: alsa-devel@alsa-project.org, John Lindgren <john.lindgren@tds.net>
Subject: Re: [PATCH] alsa-lib: snd_pcm_delay and friends do not account for a write being currently in progress
Date: Fri, 04 Jun 2010 08:50:56 +0200	[thread overview]
Message-ID: <4C08A250.3020308@ladisch.de> (raw)
In-Reply-To: <AANLkTil3VZiQe5wSezaDRXtekheR6d_hs7wKK6Ku7puX@mail.gmail.com>

VDR User wrote:
> I've been getting "pcm_hw.c: snd_pcm_hw_delay() SNDRV_PCM_IOCTL_DELAY
> failed." in my xine log

The actual error (code) is missing.

> and after some talks with one of the devs, he suggested that alsa was
> not getting data fast enough in some cases (iirc).

That would be an underrun.  This has nothing to do with the
interpretation of snd_pcm_delay's return value; this function just
appears in the log because it happend to be the first one that detected
this error condition.  An underrung cannot be prevented by any change
in alsa-lib; xine needs to use a larger buffer, or the scheduling needs
to be improved so that some other thread or program doesn't prevent xine
from being executed.


Regards,
Clemens

      parent reply	other threads:[~2010-06-04  6:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 21:29 [PATCH] alsa-lib: snd_pcm_delay and friends do not account for a write being currently in progress John Lindgren
2010-06-03  6:40 ` Clemens Ladisch
2010-06-03 14:00   ` John Lindgren
2010-06-03 14:48     ` Clemens Ladisch
2010-06-03 16:16       ` John Lindgren
2010-06-03 17:03         ` Clemens Ladisch
2010-06-03 17:51           ` John Lindgren
2010-06-03 14:40 ` [PATCH] " James Courtier-Dutton
2010-06-03 16:10   ` John Lindgren
2010-06-03 16:34     ` James Courtier-Dutton
2010-06-03 18:06       ` John Lindgren
2010-06-03 17:40 ` VDR User
2010-06-03 18:08   ` John Lindgren
2010-06-04  6:50   ` Clemens Ladisch [this message]

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=4C08A250.3020308@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=john.lindgren@tds.net \
    --cc=user.vdr@gmail.com \
    /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.