[alsa-devel] Which project to choose?

[Chris]

On Fri, 2010-07-16 at 07:15 +0800, Raymond Yau wrote:
> 2010/7/16 Chris <cpollock at embarqmail.com>
> 
> > On Thu, 2010-07-15 at 16:07 +0200, Jaroslav Kysela wrote:
> > > On Thu, 15 Jul 2010, Colin Guthrie wrote:
> > >
> > > > 'Twas brillig, and Chris at 15/07/10 02:38 did gyre and gimble:
> > > >> On Thu, 2010-07-15 at 08:08 +0800, Raymond Yau wrote:
> > > >>
> > > >>>> I posted both of those bug reports. Honestly, I just want it to work
> > > >>>> without all the error output to syslog and thrashing of my HD for
> > > >>>> minutes at a time. As I said, I've got the output of pulseaudio
> > -vvvvv
> > > >>>> if anyone would like to look at it and tell me what I need to do to
> > fix
> > > >>>> the problem.
> > > >>>>
> > > >>>> Chris
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>> Just upload your current pulseaudio.log and output of alsa-info.sh to
> > > >>> mandriva 's bugzilla
> > > >>>
> > > >>> Cannot obtain any conclusion based on the log which you have posted
> > last
> > > >>> year ( xmms)
> > > >>>
> > > >>> as Jaroslav Kysela said , need the real system time between I/O
> > operations
> > > >>> and you'll see if it's issue in the ALSA driver or a task scheduling
> > > >>> problem.
> > > >>
> > > >> Here is the bug report with the outputs uploaded.
> > > >>
> > > >> https://qa.mandriva.com/show_bug.cgi?id=60169
> > > >
> > > > Well seeing as my process when getting such a bug is to report it here
> > > > on behalf of the user, I suspect that this has reached a stalemate....
> > >
> > > Please, provide also /var/log/messages output for xrun_debug=11 - see
> > > http://www.alsa-project.org/main/index.php/XRUN_Debug for more details.
> > We
> > > can detect the ALSA ring buffer issues in this way, too.
> > >
> > >                                               Jaroslav
> > >
> > See pastebin file http://pastebin.com/MdENbSNd
> > Hopefully I did this correctly.
> >
> >
> You have to provide the  PA server log since we just want to know how PA
> server handle the underrun condition  when the PA client use small buffer
> size
> 
> Did "aplay -Dhw:0,0 --buffer-size=128 any.wav" get underrun ?

[chris at localhost ~]$ aplay -Dhw:0,0
--buffer-size=128 /home/chris/Documents/gotmail.wav
aplay: main:654: audio open error: Device or resource busy

Frankly I'm ready to just say the heck with it. I'm totally lost with
about 99.9% of what every one is talking about on this thread. 

Chris


-- 
Chris
KeyID 0xE372A7DA98E6705C

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20100715/f6a7f9bf/attachment.sig