Bugzilla – Bug 12404
Problem with Ogg streaming internet radio stations
Last modified: 2009-06-17 12:01:46 UTC
I have a problem with Ogg streaming internet radio stations. If I begin to play one of this stations, all seems to be working fine. The problem starts, when the current tune ends (you really have to wait for the tune to end). Then the receiver stops playing at all (although the signal light at the front indicates that it is still playing). Now I'm not able to change the station in the remote control or do anything else to rectify the situation. The only thing that now helps is to power cycle the receiver. Its not necessary or helpful to reboot the remote, so I assume that the error lies within the receiver. Some examples for radio stations to check with: "Gone Country": http://dir.xiph.org/listen/10073985/listen.m3u "MyRadio Acid Jazz": http://myradio.com.ua/alias/newjazz128.m3u "MyRadio Lounge": http://myradio.com.ua/alias/LOUNGE128.m3u Other stations are playing just fine, it seems that only Ogg stations make problems. The problem occurs regardless if I use the SqueezeNetwork or the newest SqueezeCenter software. I've tried various releases of the remote firmware. The receiver is on firmware 58. The online support couldn't help here, see Incident: 090603-001518. Regards Joachim
Confirmed, error is "Ran out of decoder PRAM!"
Verified 7.3.3 IP3K firmware has an issue with the 3 streams listed here, but works fine with the streams listed in bug 4418 Players with a display will time out after a time with 'Ran out of decoder PRAM' error message
I can't reproduce this. Tested both Jazz and Lounge (Country was 404) through many song changes. Tested on SB2 and Transporter.
(In reply to comment #2) > Verified 7.3.3 IP3K firmware has an issue with the 3 streams listed here, but > works fine with the streams listed in bug 4418 > > Players with a display will time out after a time with 'Ran out of decoder > PRAM' error message My mistake, I was still on 7.3.2 which confirms the error. Moving to 7.3.3 (with new player firmware) fix's the issue.
*** This bug has been marked as a duplicate of bug 4418 ***