From: Takashi Iwai <tiwai@suse.de>
To: Glenn Maynard <glenn@zewt.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: snd_pcm_wait returning EPIPE
Date: Mon, 11 Oct 2004 12:18:44 +0200 [thread overview]
Message-ID: <s5hwtxx4kxn.wl@alsa2.suse.de> (raw)
In-Reply-To: <20041007152634.GK12858@zewt.org>
At Thu, 7 Oct 2004 11:26:34 -0400,
Glenn Maynard wrote:
>
> I've disabled the underrun state, eg. setting
> snd_pcm_sw_params_set_stop_threshold to dsnd_pcm_sw_params_get_boundary,
> which results in EPIPE never being returned from snd_pcm_wait (as I wanted),
> so I can handle underruns myself. I'm opening hw:0 directly, to avoid
> resampling.
>
> However, I'm receiving a report of a system returning EPIPE:
>
> https://sourceforge.net/tracker/index.php?func=detail&aid=1035604&group_id=37892&atid=421366
> https://sourceforge.net/tracker/download.php?group_id=37892&atid=421366&file_id=103978&aid=1035604
>
> This is apparently on an x86-64 system.
>
> Is this a known problem? Am I probably doing something wrong that just
> happens to usually work? I'm treating EPIPE as an unexpected condition,
> since it's not clear why it would happen here; should I have it call
> snd_pcm_prepare() and retry anyway?
-EPIPE is usually buffer over/underrun (XRUN), so apps are supposed to
call snd_pcm_prepare() after receiving this.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-11 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 15:26 snd_pcm_wait returning EPIPE Glenn Maynard
2004-10-11 10:18 ` Takashi Iwai [this message]
2004-10-11 14:11 ` Glenn Maynard
2004-10-11 15:17 ` Takashi Iwai
2004-10-11 15:26 ` Glenn Maynard
2004-10-12 19:30 ` Glenn Maynard
2004-10-12 19:31 ` Glenn Maynard
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=s5hwtxx4kxn.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=glenn@zewt.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.