Re: [xine-devel] nasty mms stream (or cache problem?)]

[Reimar <Rei...@st...>]

Hi,

why can't stupid sf lists set the reply-to or something appropriately? I always
answer to the ppl directly instead of to the list (sorry for that btw...)!

> On Mon, 3 Jan 2005 19:03:28 +0100, Alien
> <ali...@us...> wrote:
> > i have some problems with an mms stream (or at least my daddy does)
> > 
> > xine mms://audio1.musicradio.com/classicfm
> > 
> > the problem is that it buffers, and it plays a little while and then stops
> > again...
> > 
> > sometimes it's longer, sometimes it's right after buffering.
> > 
> > since it's most of the time just a short while (a few seconds) i think it
> > might be a problem with caching or buffering:
> > 
> > you connect, you buffer, you start playing, but buffer is full, so at that
> > time, you don't request from the stream, after a while buffer is emptying,
> 
> Hmmm, no, what you call buffer is never full when you play a radio stream. 
> The demuxer thread reads data as fast as possible.
> When the fifo is full enough (let's say 3 seconds of data), the
> playback restarts.
> If the playback consumes more bytes than what is coming then the fifo
> gets empty and the engine is paused.
> 
> > one reconnects (or asks for more data) and by then, their are more people
> > connected so you don't get anymore data, after a while you reconnect and it
> > starts all over again.
> 
> why do you think there is reconnections ?
>  
> > it would be better for a stream that you constantly request data, at a lower
> > rate or higher rate depending on how empty full the buffer is... for example
> > you could start playing when the buffer is at 80%...
> 
> the engine requests data constantly.
>  
> > anyone have any ideas? this happens with rc5 and 1.0 ...
> 
> does it work with other players ?

Works perfectly with MPlayer CVS (with and without cache, with ffmpeg decoder) - even over my poor 56k Modem ;-)
Did you try http://audio1.musicradio.com/classicfm, too?

Greetings,
Reimar Döffinger