[MPlayer-users] alsa9 + multiple files

[joy]

On Sun, Jun 30, 2002 at 10:33:33PM +0200, Arpi wrote:
> [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
> Hi,
> 
> > [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
> > On Sun, Jun 30, 2002 at 12:15:33AM +0000, jeff wrote:
> > > [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
> > > ok it works with the current cvs, mine was only a week or so old though :P
> > > all i get is... but it still works fine. : )
> > > 
> > > alsa-init: 1 soundcard found, using: hw:0,0
> > > alsa-init: WARNING! MAX_OUTBURST exceeds your available buffersize.
> > > alsa-init: MAX_OUTBURST=65536, buffersize=16384
> > > 
> > yes its cause configure sets MAX_OUTBURST to an unreasonable high
> > value, but ao_alsa9 has a mechanism to work arround this, so you can
> > ignore this warning for now.
> 
> As i've told you several times, MAX_OUTBURST is an internal thing of mplayer
you never told me...

> core, shouldn't matter for audio out. It's just used to calculate initial audio
> buffer size, but the actual size is set by teh audio out driver by
> get_space(). If get_space() returns _greater_ value than MAX_OUTBURST, it
> will be limited to MAX_OUTBURST, otherwise it has no effect.
> So, this:
> > > alsa-init: MAX_OUTBURST=65536, buffersize=16384
> is normal!
> even if buffersize>MAX_OUTBURST is ok, but in that case the buffer cannot be
> filled in single pass, it will be filled wiht multiple get_space()/play().
> 

yes i saw it, thats what i mean with internal mechanism and thats the
reason why i have this warning actually removed. its just in an
older patch i sent in. 

-- 
regards

____-
joy

________/\---------%%%___________-----------
webcast every sunday 2000 cest at pingfm.org

pgp key at: x-hkp://wwwkeys.de.pgp.net