Hi,
On Mon, Sep 12, 2005, Cosimo Alfarano wrote:
> In all this stuff what underlies is that some sort of bad behaviour is
> detected. Don't know if it's a architectuarl problem or not.
As I said, I don't expect apps to be able to deal with every invention
sound daemons can make; I find Rhythmbox behavior quite acceptable with
respect to this, and you should simply press pause to ... pause!
> The bug in rhythmbox, for which I filed a report, is that he cannot
> detect that gst exited _not_ because track was ended _but_ because
> of an external event (esdctl off) occurred that prevents gst to go on,
> and jumps to the next track.
I think you didn't understand my explanation with respect to GStreamer
and Rhythmbox behavior when in esdctl off mode:
I think GStreamer and Rhythmbox TRULY think they're outputting sound.
Instead of playing your 3 minutes song in 3 minutes, they're playing it
in 5 seconds because they rely on esound's clock to measure how far the
sound card has output the audio.
Rhythmbox and GStreamer did their job: they played the audio at
whatever bitrates esound permits, and since there's no limit beside
your CPU, this means the tracks end in 5 seconds and your CPU is highly
used.
Bye,
--
Loïc Minier <[EMAIL PROTECTED]>
Come, your destiny awaits!
