Re: Uninitialised storage? (no advance in playlist is a *real* bug)

On Mon, 26 May 2003, Brian Candler wrote:

> So I can only imagine that there is something which depends on a bit of
> uninitialized memory, which means that either mpg123_info->eof is not being
> set to 1 at the end of the track, or that mpg123_ip.output->buffer_playing()
> is permanently returning 1 - perhaps something in oss_playing().

I can't guarantee that there is no bug here, but I'm not aware of any, and 
this has had *a lot* of testing.

The behavior could however easily be explained by a problem with the 
soundcard driver or some kind of transiend hardware error.

When xmms reaches the end of a song it will wait until the buffer in the 
soundcard is (almost) empty.  Here it looks like the soundcard driver is 
still reporting that there is a lot of data left in the buffer, and xmms 
will never continue to the next song.

> The other strangeness was when I first installed xmms, the default output
> device selected was the DiskWriter, and so I was getting no audio and the
> track time was decrementing at about 3 times real time.

This may happen if xmms is configured to use a plugin that no longer
exist.  I can't think of any explanation for it to happen if xmms had
never been run on the computer before.  I'm quite sure it does not use any
"uninitialised storage" though.

-- 
Håvard Kvålen