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 21:28:56 +0100 [thread overview]
Message-ID: <14394c699c36fcb0868de024a699702d@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 21:28 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 21:10
----------------------------------------------------------------------
okay, thanx for the trick
here is the output you ask for :
<<
$ grep -l dmix /usr/share/alsa/cards/*
/usr/share/alsa/cards/Azalia.conf
/usr/share/alsa/cards/ICH4.conf
/usr/share/alsa/cards/ICH.conf
/usr/share/alsa/cards/NFORCE.conf
>>
, plus one extra output, under debian, tells what alsa package is install
in which version :
<<
<code>
$ dlocate -l alsa | grep ii
ii alsa-base 1.0.8-7 ALSA driver configuration
files
ii alsa-oss 1.0.8-1 ALSA wrapper for OSS
applications
ii alsa-utils 1.0.8-4 ALSA utilities
ii alsamixergui 0.9.0rc2-1-7 graphical soundcard mixer for
ALSA soundcard driver
ii alsaplayer 0.99.76-0.3 PCM player designed for ALSA
ii alsaplayer-alsa 0.99.76-0.3 PCM player designed for ALSA
(ALSA output module)
ii alsaplayer-common 0.99.76-0.3 PCM player designed for ALSA
(common files)
ii alsaplayer-esd 0.99.76-0.3 PCM player designed for ALSA
(ESD output module)
ii alsaplayer-gtk 0.99.76-0.3 PCM player designed for ALSA
(GTK version)
ii alsaplayer-oss 0.99.76-0.3 PCM player designed for ALSA
(OSS output module)
ii alsaplayer-text 0.99.76-0.3 PCM player designed for ALSA
(text version)
ii alsaplayer-xosd 0.99.76-0.3 PCM player designed for ALSA
(osd version)
ii gnome-alsamixer 0.9.6-1 ALSA sound mixer for GNOME
ii gstreamer0.8-alsa 0.8.8-2 ALSA plugin for GStreamer
ii libesd-alsa0 0.2.35-2 Enlightened Sound Daemon
(ALSA) - Shared libraries
</code>
>>
with this output, i can guess i am using alsa 1.0.8 (-7 is only a debian
revision add)
when i check my card :
<<
$ cat /proc/asound/cards
0 [ICH6 ]: ICH4 - Intel ICH6
Intel ICH6 with STAC9750,51 at 0xdffffe00, irq 169
1 [Modem ]: ICH-MODEM - Intel ICH Modem
Intel ICH Modem at 0xee00, irq 201
>>
i guess my card ICH6 should be managed by /usr/share/alsa/cards/ICH4.conf
file
i like debian because it aim to be stable,
i won't install alsa-lib 109 now - i don't have time meanwhile i would
love to play with all that stuff
if you mind :)
my last ~/.asoundrc file
<<
ste@station:~$ cat /home/ste/.asoundrc
pcm.!default { type plug slave.pcm "dmix" }
pcm.!dmix {
type dmix
ipc_key 1
# ipc_perm 0660
ipc_key_add_uid true
slave {
pcm "hw:0,0"
format S16_LE
# rate 48000
rate 44100
channels 2
period_time 0
period_time 1024
# buffer_size 4096
# buffer_size 1024
# periods 1024
# periods 4096
# periods 2048
# buffer_size 4096
buffer_size 2048
# buffer_size 8192
# buffer_size 16384
# periods 16384
# period_size 2048
period_size 1024
}
bindings { 0 0 1 1 }
}
# ctl.mixer0 { type hw card 0 }
>>
this is the only way i can make works : xmms, wmsoundserver, esd, artsd,
thunderbird notification sound
the last step i would love to would be to output a copy of my sound to a
special device in order to being able to record it without recording my
system sounds, but i would need to become an alsahacker, - around july
perhaps
you can still ask me things if you like
see you
----------------------------------------------------------------------
rlrevell - 01-07-06 21:28
----------------------------------------------------------------------
Yeah I'm afraid you may have to choose between stability and functionality
here. Many, many dmix bugs have been fixed since ALSA 1.0.8.
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
01-07-06 09:00 rlrevell Note Added: 0007509
01-07-06 16:57 moncnam Note Added: 0007516
01-07-06 20:54 rlrevell Note Added: 0007519
01-07-06 21:10 moncnam Note Added: 0007521
01-07-06 21:28 rlrevell Note Added: 0007522
======================================================================
-------------------------------------------------------
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 20:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 20:28 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:10 bugtrack
2006-01-07 19:54 bugtrack
2006-01-07 15:57 bugtrack
2006-01-07 8:00 bugtrack
2006-01-07 3:04 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=14394c699c36fcb0868de024a699702d@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