From: Stefan Schoenleitner <dev.c0debabe@gmail.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: "Resource temporarily unavailable" while reading although poll returns POLLIN event
Date: Thu, 22 Apr 2010 12:09:37 +0200 [thread overview]
Message-ID: <4BD02061.2010204@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1004211917120.16336@eeebox2.perex-int.cz>
Jaroslav Kysela wrote:
> On Wed, 21 Apr 2010, Stefan Schoenleitner wrote:
>> I suspect that this is a bug in ALSA ?
>
> It might be. Could you post snd_pcm_dump() when you read less frames?
Sure, here's the output:
-----------------------------------------------------------------
snd_pcm_avail_update(capture): 11
demangled poll: POLLIN on capture device
could not read from capture device: Resource temporarily unavailable
ALSA <-> PulseAudio PCM I/O Plugin
Its setup is:
stream : CAPTURE
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 1
rate : 8000
exact rate : 8000 (8000/1)
msbits : 16
buffer_size : 640
period_size : 160
period_time : 20000
tstamp_mode : NONE
period_step : 1
avail_min : 160
period_event : 0
start_threshold : 160
stop_threshold : 320
silence_threshold: 0
silence_size : 0
boundary : 5764607523034234880
-----------------------------------------------------------------
As you can see I'm using pulseaudio.
The version I'm using is 1:0.9.14-0ubuntu20 (on ubuntu jaunty).
For testing purposes I increased the period size to 320 so that the
program works on my hardware sound card "hw".
It turned out that the program is working fine there and the poll()
behavior is as it should be.
cheers,
stefan
next prev parent reply other threads:[~2010-04-22 10:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 11:28 "Resource temporarily unavailable" while reading although poll returns POLLIN event Stefan Schoenleitner
2010-04-21 16:15 ` Stefan Schoenleitner
2010-04-21 17:18 ` Jaroslav Kysela
2010-04-22 10:09 ` Stefan Schoenleitner [this message]
2010-04-23 4:10 ` Raymond Yau
2010-04-24 1:32 ` Raymond Yau
2010-04-24 14:38 ` Stefan Schoenleitner
2010-04-24 23:43 ` Raymond Yau
2010-04-26 7:52 ` Stefan Schoenleitner
2010-04-27 0:35 ` Raymond Yau
2010-04-26 1:46 ` Raymond Yau
2010-04-26 8:19 ` Stefan Schoenleitner
2010-04-26 11:10 ` Raymond Yau
2010-04-22 4:28 ` Raymond Yau
2010-04-22 10:49 ` Stefan Schoenleitner
2010-04-23 7:45 ` Raymond Yau
2010-04-23 11:16 ` Stefan Schoenleitner
2010-04-22 2:41 ` Raymond Yau
2010-04-22 10:15 ` Stefan Schoenleitner
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=4BD02061.2010204@gmail.com \
--to=dev.c0debabe@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
/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).