On Monday 04 February 2008, Eddy Petrișor wrote: > Currently I am listening (trying to) to Lu_beck's Radio Station. I am > 995 sure the songs can be identified from the log (snapshot made after > listening one sone and a little from the second) ;-) .
Thanks for the log file. That second song shows that it took a while (3 seconds) for your buffer to initially fill up enough to play, then it emptied a couple of times in the first 6 seconds. Wow. That does look bad. > Ok, I went back to that version, then even further, now I have ended up > using the ancient 1:1.1.3.0-1 which doesn't stop in an annoying fashion. > It plays without interrupts. > > Maybe there was a protocol change recently? It is interesting that 1:1.1.3.0-1 works, because last.fm did indeed change the protocol. The old protocol delivers all of a station's songs as a single stream. The current protocol streams each song individually (i.e. there is a new HTTP GET request for each song). It's not a recent change though. That happened with 1:1.3.0.58-1 back in June 2007! I think that last-exit also uses the old protocol, so that's probably why it doesn't give you buffering problems: neither last-exit nor 1.1.3.0 send a new request on each new song. Shell-fm in testing/unstable uses the new protocol. Do you have buffering problems when you use that? (Check Last.fm's conf file for a url to use.) If so, then I suspect a problem between your box and their servers. Maybe wireshark could shed some light on this. If not, then... > I am confused... Me too. John
