reassign 327731 esound
thanks
Hi,
On Mon, Sep 12, 2005, Cosimo Alfarano wrote:
> The reason is becasue you want to use something that not supporting
> esound, for instance gnomemeeting (it seems that communication quality
> suffers and gets delayed using esd instead of direct ALSA).
>
> Suspending esound is a normal operation, AFAIK, and esdctl is the way
> intended for handle it without killing esd.
Thanks for the clarification, this is an interesting use case.
However, the way it is implemented is disruptive for esound clients. I
think esound should simply discard sound sent by the applications as if
playing (at the same rate), and this should have the effect of muting
all esound applications temporarily. I have my idea on why it isn't
implemented like this -- I suspect esound relies on the sound card's
buffer to have a clock, and hence discards data from the application as
fast as it is sent.
I suspect that esdsink is sending data as fast as your CPU permits, and
not at the negociated sound card / esound audio rate any more, and that
causes the high CPU usage and the "normal" jumps to the next track on
the playlist.
This looks clearly like a bug in esound to me, and I'm reassigning it
to the esound package.
Bye,
--
Loïc Minier <[EMAIL PROTECTED]>
Come, your destiny awaits!
