From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001548]: "alsa-play: xrun of at least 0.009 msecs. resetting stream" : inopportune small pauses while playing
Date: Sat, 7 Jan 2006 04:04:46 +0100 [thread overview]
Message-ID: <2a4b350be215896aa6af34ef503e302d@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1548>
======================================================================
Reported By: moncnam
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1548
Category: PCI - intel8x0m
Reproducibility: random
Severity: minor
Priority: normal
Status: assigned
Distribution: debian sarge 3.1
Kernel Version: 2.6.13-rc7
======================================================================
Date Submitted: 11-12-2005 10:58 CET
Last Modified: 01-07-2006 04:04 CET
======================================================================
Summary: "alsa-play: xrun of at least 0.009 msecs. resetting
stream" : inopportune small pauses while playing
Description:
whatever the player i use (alsaplayer, xmms, mplayer) i experience small
pause while playing (half of a second)
using mplayer, i can see the following message appearing when the pause
occur
<<alsa-play: xrun of at least 0.009 msecs. resetting stream>>
the playing doesn't stop, it continue well, just a small pause
i have no other messages in `dmesg` or in syslog
======================================================================
----------------------------------------------------------------------
moncnam - 01-07-06 03:58
----------------------------------------------------------------------
you write : (perdiod_size should be <= buffer_size/2 )
um
, i can add that this could be specified in the syntaxe page
to answer : no, i can't use only the default setting because it doesn't
provide mixing capability (and i want to be able to hear my
notification/alert while playing)
gosh ! nothing work ok now, esd outputs errors, wsoundserver no sound,
and...
o look, i also have a conf file in /etc
well, i erase it, put back my ~/.asoundrc and, it is better now
still a problem with esd doing scrappy sound : it doesn't like period_time
0
btw, what is period_size ? i don"t have this parameter in the syntax
page...
woaw, alsa is really a pain in the neck <smile>
... okay, i got it works :
nothing in /etc
in my home :
pcm.!dmix {
type dmix
ipc_key 1
ipc_key_add_uid true
slave {
pcm "hw:0,0"
# rate 44100
rate 48000
# period_size 1024
period_time 1024
buffer_size 4096
...
in esd.conf :
[esd]
auto_spawn=0
spawn_options=-terminate -as 5 -d default
spawn_wait_ms=100
# default options are used in spawned and non-spawned mode
default_options= -r 48000
-r 48000 in default_options, not in spawn_option neither in command line
otherwise doesn't work
and wsoundserver does work
gosh, what about artsd ?
no problem , it does work as before (one have to specify 48000 in
kcontrol)
thank you, it's enought for tonight, enjoy weekend, bye
thanks for support
----------------------------------------------------------------------
moncnam - 01-07-06 04:04
----------------------------------------------------------------------
i don't know why but :
- wsoundserver does need a period_time (now it is 1024)
- esd fail launching when period_size = 4096 and buffer_size = 16384 with
the following message :
<<
ste@station:~/tmp$ esd
- server format: sample rate = 48000 Hz
Audio device open for 44.1Khz, stereo, 16bit failed
Trying 44.1Khz, 8bit stereo.
Audio device open for 44.1Khz, stereo, 8bit failed
Trying 48Khz, 16bit stereo.
Audio device open for 48Khz, stereo,16bit failed
Trying 22.05Khz, 8bit stereo.
Audio device open for 22.05Khz, stereo, 8bit failed
Trying 44.1Khz, 16bit mono.
>>
and so one for every possibility
Issue History
Date Modified Username Field Change
======================================================================
11-12-05 10:58 moncnam New Issue
11-12-05 10:58 moncnam Distribution => debian sarge 3.1
11-12-05 10:58 moncnam Kernel Version => 2.6.13-rc7
11-21-05 23:56 sashak Note Added: 0006779
11-22-05 00:04 moncnam Note Added: 0006781
11-22-05 00:31 sashak Note Added: 0006783
11-22-05 00:31 sashak Assigned To sashak =>
11-22-05 00:43 moncnam Note Added: 0006784
01-04-06 22:38 moncnam Note Added: 0007456
01-07-06 02:14 sashak Note Added: 0007503
01-07-06 03:58 moncnam Note Added: 0007505
01-07-06 04:04 moncnam Note Added: 0007506
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-07 3:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 3:04 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-07 20:43 [ALSA - driver 0001548]: "alsa-play: xrun of at least 0.009 msecs. resetting stream" : inopportune small pauses while playing bugtrack
2006-01-07 20:38 bugtrack
2006-01-07 20:28 bugtrack
2006-01-07 20:10 bugtrack
2006-01-07 19:54 bugtrack
2006-01-07 15:57 bugtrack
2006-01-07 8:00 bugtrack
2006-01-07 2:58 bugtrack
2006-01-07 1:14 bugtrack
2006-01-04 21:38 bugtrack
2005-11-21 23:43 bugtrack
2005-11-21 23:31 bugtrack
2005-11-21 23:31 bugtrack
2005-11-21 23:04 bugtrack
2005-11-21 22:56 bugtrack
2005-11-12 9:58 bugtrack
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=2a4b350be215896aa6af34ef503e302d@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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