[alsa-devel] Which project to choose?

[Raymond Yau]

2010/7/20 Chris <cpollock at embarqmail.com>

> On Mon, 2010-07-19 at 08:53 +0100, Colin Guthrie wrote:
> > 'Twas brillig, and Raymond Yau at 19/07/10 07:35 did gyre and gimble:
> > > 2010/7/19 Chris <cpollock at embarqmail.com>
> > >
> > >> On Mon, 2010-07-19 at 09:44 +0800, Raymond Yau wrote:
> > >>
> > >>>>
> > >>> Refer to https://qa.mandriva.com/show_bug.cgi?id=56473#c10
> > >>>
> > >>> I have installed mandriva 2010 on virtual box
> > >>>
> > >>> when using xmms and libao output plugin to play system sound
> startup3.wav
> > >>>
> > >>> xmms hang at the end of the playback only when enable buffering in
> libao
> > >>> output plugin.(configure output plugin in xmms, unfortunately default
> is
> > >>> enable buffering buffer size 3000 chunk size 1000)  ,
> > >>>
> > >>> xmms does not hang when you disable the buffer or using
> liboss/libALSA
> > >>> output plugin
> > >>>
> > >>> The last message in the pulseaudio server is
> > >>> D: protocol-native.c  'underrun on libao[xmms] playback stream' , 0
> bytes
> > >> in
> > >>> queue.
> > >>>
> > >>> The sound card seem running since hw_ptr and appl_ptr are increasing
> when
> > >>> cat /proc/asound/card0/pcm0p/sub0/status
> > >>>
> > >>> After a while , the following message appear
> > >>>
> > >>> E:alsa-sink.c : ALSA woke us up to write new data , but there was
> > >> actually
> > >>> nothing to write!
> > >> The above is exactly what I see periodically Raymond, so, what, if
> any,
> > >> is the fix?
> > >>
> > >> Chris
> > >>
> > >>
> > > Do you mean that you cannot reproduce the xmms hang bug on your ens1371
> or
> > > via8237 ?
> > >
> > > xmms always hang/freeze at 4 second as xmms display the total length of
> > > startup3.wav is 5 seconds
> > >
> > > you have to ask mandriva 's maintainer why enable buffering is the
> default
> > > option since xmms did not hang when I disable buffering in libao plugin
> > >
> > > For fefora 10 and 13 , they only provide liboss, libALSA and libpulse
> plugin
> > > for xmms
> > > I have no idea about the chunk size in libao plugin
> >
> >
> > With a clean user account, I could not reproduce either problem with the
> > default settings.
> >
> > FWIW, running PA under virtualbox is quite different to running it under
> > a real system. For example PA will enable the non-timer based mode
> > automatically when under a virtual machine.
> >
> > Col
> >
> >
>
> Colin, I've just re-enabled PA using the Ensoniq/Creative AudioPCI
> ES1371+ driver, this is according to the Mandriva Control Center sound
> setup. However, it also shows the VIA VT82xx audio driver when initially
> loaded, when I click on 'ok' it shows the Ensoniq driver. I've again run
> pulseaudio -k ; pulseaudio -vvvvv while playing a cd with mplayer. I've
> uploaded the output here:
>
> http://ez-files.net/953712
>
> Does this have any meaning?
>
> Thanks for any assistance.
>
> Chris
>
>

Please note that alsaplayer is not aplay

you can easily make underrun/overrun occur on pulse device by specify a
buffer size which is smaller than PA server used

aplay -Dpulse -v --buffer-size=128 /usr/share/sounds/*.wav

arecord -v -Dpulse -f cd -d 60 --buffer-size=128 test.wav

can you provide pulseaudio log  for the underrun/overrun by aplay/arecord ?

mandriva 2010 seem still support ALSA OSS emulation

unless you have a hardware mixing sound card , you have to configure your
gmplayer to use alsa or pulse

more .mplayer/gui.conf
ao_driver = "oss"   <--------pulse or alsa
ao_alsa_device = "hw:0,0"    <----- pulse or default