Re: EsounD / wait_for_tcp_memory / xanim

[Bibek Sahu <scorpio dodds net>]

	DOH!  My mistake.  In my first message, I went into detail... then
pine crashed. :-(

	Anyhow, EsounD is an audio program / library to mix multiple
streams.  Similar in concept to NAS but much simpler and, in my
experience, works much better.

	I use it so that I can use multiple sound programs simultaneously
(e.g., mpg123 to play mp3s and, here, xanim to play video _and_ audio...
until it xanim stops writing, anyhow).  It has a few other handy features
as well, but those are the biggies. And it's much easier to implement than
NAS.

	The problem seems to be related to timing in xanim, but it doesn't
occur until it (apparently) saturates the pipe.  It shovels data into the
pipe much more quickly than the daemon at the other end reads it.  If I
tell the daemon that it's getting sound at 13000Hz (instead of the 11127
that it's really being sent) then everything functions.  Except that
everbody's voice is very high pitched. ;-}

	When the pipe get saturated, the end that xanim is writing to
blocks (as it should).  However, at that point esd stops receiving data as
well (which should NOT be the case...).  The wait_for_tcp_memory function
loops continuously until it either gets a signal or there's memory
available.  However, since the pipe ... effectively stops ... esd never
reads more from the pipe (it uses select), hence the memory never gets
freed and the loop never exits unless it gets a signal.

	Any ideas?  Any more questions I can answer?

Thanks!
- Bob

On Fri, 4 Sep 1998, David Alan Gilbert wrote:

> Bibek Sahu wrote:
> 
> >         The attached patch provides EsounD support in xanim27070.  It's
> > created off of esound 0.2.4, with support for falling back to OSS if esd
> > (the esound daemon) isn't running.
> 
> Just remind those of us who are ignorant; what exactly is 'EsounD'.
> 
> Dave