Bugzilla – Bug 15241
Internet Radio->Music->Classical->Stations (50+)->WCPE doesn't play
Last modified: 2010-05-14 16:32:46 UTC
Trying to play WCPE, and the player (Boom) stops. Info reported is: File Format: Ogg Vorbis Bitrate: 56kbps CBR URL: http://opml.radiotime.com/Tune.ashx?id=s27997&formats=aac,mp3,wma,wmpro,wmvoice,wmvideo,ogg&partnerid=16 This also occurs on 7.4.2. Support tells me that the same sequence (Internet Radio->Music->Classical->Stations (50+)->WCPE) works with mysqueezebox.com I have forced it to work by creating a favorite with the URL: http://opml.radiotime.com/Tune.ashx?id=s27997&partnerid=16
Created attachment 6353 [details] Server log for WCPE failure Logitech phone support confirmed failure on their SBS
Same sequence through mysqueezebox.com results in: File Format: MP3 Bitrate: 96kbps CBR URL: http://opml.radiotime.com/Tune.ashx?id=s27997&partnerid=16
I have connected a Touch, a SB Radio and a Boom at the same time to the same 7.4.2 server on Win7. I can use the Web remote to play the WCPE station to the Touch and the SB Radio, but when I tell the Server to play thru the Boom it buffers and then kicks back to the Stations (49+)> menu. The same happens when I try to play WCPE thru the Boom menu. Other stations play fine on all 3 devices, but WCPE will not play on the Boom.
Denny, how long does it play before it stops?
It doesn't play at all. My assumption is that the Radiotime url lists Ogg Vorbis as a codec, and THAT gets selected, but 56kbps Ogg Vorbis isn't supported (I think I read that somewhere), so it fails. Forcing it to mp3 works fine, so it's only the Radiotime url giving the ogg option that's a problem.
Chris to run through Andy's radio logging suggestions
Note to self: scan.scanner -> debug, player.streaming.direct -> debug, player.source -> info, and trying to wget the file is often useful.
Moving P3 and lower bugs to next release target
This locks up my Boom, so it would appear to be a decoder crash rather than some kind of playlist-scanner problem. *** This bug has been marked as a duplicate of bug 14773 ***