Bug 8528 - wma stream not working for Receiver release 23
: wma stream not working for Receiver release 23
Status: CLOSED WORKSFORME
Product: SB Receiver
Classification: Unclassified
Component: General
: 23
: PC Debian Linux
: -- normal (vote)
: ---
Assigned To: James Richardson
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-21 21:43 UTC by Greg Heinzinger
Modified: 2008-07-09 09:45 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Heinzinger 2008-06-21 21:43:12 UTC
Once I upgraded my squeezecenter to 7.0.1 the Squeezebox Receiver then upgraded itself to release 23 -- at this point some of my internet radio stations no longer worked.  I tried recreating the playlists for these internet radio stations (since I had trouble migrating these before).  There was no change in behavior.  The playlists work on my SqueezeBox V3, but not on the SqueezeBox Receiver.  Upon further investigation it looks like the ones that use wma do not work while others do work.

Below is information on the software & hardware versions along with the internet radio stations that work and don't.

Please let me know if additional information is required.

Thanks, Greg


Version Information:

SqueezeCenter Version: 7.0.1 - 19705 @ Wed May 14 19:53:57 PDT 2008 - Debian - EN - iso-8859-1
Server IP address: 192.168.0.90
Perl Version: 5.8.8 i486-linux-gnu-thread-multi
MySQL Version: 5.0.32-Debian_7etch3 
Platform Architecture: i686-linux

Model: Squeezebox v3
Firmware: 88

Model: receiver
Firmware: 23


BBC World Service (doesn't work)
File Format: Windows Media 
Bitrate: 32kbps CBR

KPBS -- NPR San Diego (doesn't work)
File Format: Windows Media 
Bitrate: 129kbps CBR 

KQED -- NPR San Francisco (works)
File Format: Internet Radio 
Bitrate: 32kbps CBR
Comment 1 Greg Heinzinger 2008-06-28 14:59:31 UTC
I changed the system configuration and have done more testing.  I bought a second Receiver -- reset everything -- and disconnected my SqueezeBox V1.  In this configuration I experienced no problems (ran for multiple days planning various wma internet radio streams).

I then tried an experiment -- I reconnected my SqueezeBox V1 to the network.  In a few minutes I started experiencing problems with the same wma radio streams no longer playing.  I disconnected the SqueezeBox V1 from the network and power cycled everything (including rebooting the server), but the problem persisted.

I then shut down my server (so no SqueezeCenter running) and then reset the two Receivers (pushing and holding the front button).  After configuring the Receivers (with no SqueezeBox V1 on the network) the system is working fine again -- there are no issues now planning wma radio streams.

Thus, it appears that wma radio streams do not reliably work with a Receiver and SqueezeBox V1 both connected to the system when using SqueezeCenter 7.0.1 and Receiver firmware 23.  I previously had the system set up with the Receiver and a SqueezeBox V1 connected and had no issues playing wma radio streams, this problem started when I upgraded to SqueezeCenter 7.0.1 (and the Receiver automatically upgraded itself).

Adding to the original information.  After a little while of the wma streams not working on the Receiver they stopped working on the SqueezeBox V3.

Please let me know if additional information is required.

== Greg
Comment 2 James Richardson 2008-06-30 06:35:35 UTC
Greg:

Can you also include the HTTP information for the streams you provided below.
Comment 3 Greg Heinzinger 2008-06-30 20:09:43 UTC
adding more information about the feeds

BBC World Service 
File Format: Windows Media 
Bitrate: 32kbps CBR
mms://livewmstream-ws.bbc.co.uk.edgestreams.net/reflector:38968

KPBS -- NPR San Diego 
File Format: Windows Media 
Bitrate: 129kbps CBR 
mms://media01.kpbs.org/kpbs-fm

KQED -- NPR San Francisco 
File Format: Internet Radio 
Bitrate: 32kbps CBR
http://kqedsc01.streamguys.us/
Comment 4 James Richardson 2008-07-01 11:31:51 UTC
Works for me on Vista / XP-SP3.  Steven will test on Ubuntu
Comment 5 Spies Steven 2008-07-01 14:27:26 UTC
I was not able to reproduce either on Ubuntu.

I used one controller, two receivers, one SB3 and one SB1 on the same sever without issue.  I was able to play all three stations mentioned in this bug without issue on the receivers and SB3.  I was not able to play them on the SB1 of course since it does not support wma decoding natively and SqueezeCenter does not support transcoding out of the box for linux.

I'm at a loss on this one.

SqueezeCenter Version: 7.0.1 - 19705 @ Wed May 14 19:53:57 PDT 2008 - Debian - EN - iso-8859-1
Comment 6 James Richardson 2008-07-01 21:14:05 UTC
Steven: thanks for testing that.

Greg:  Can I have you uninstall SC from your system, then install 7.1 (latest nightly) and try the streams again please.

Let us know if that still has an issue, or if we need to test in a different way.

Comment 7 Greg Heinzinger 2008-07-01 23:10:50 UTC
I saw the linux testing mentioned below.  When I have experienced the problems
I have first created a playlist for each radio stream, then I have started this
from the playlist.  I did not always have an issue the first time, but after a
few tries it would stop working.  One time a single station stopped first and
then the second station.  So to help create the problem I experienced it would
be useful to try the following test (using the setup described below):
1)  set up playlists for the three streams
2)  start a playlist on one of the boxes
3)  try a playlist on the SqueezeBox V1 (this should do nothing)
4)  stop some of the streams and switch to another stream
5)  switch back to one of the wma streams (usually had trouble first with the
KPBS one)

If this is not too much work it would be useful if this could be tried before I
try upgrading the SqueezeCenter, because I have a large collection and
upgrading and potentially downgrading will take a few hours.

thanks, Greg
Comment 8 James Richardson 2008-07-02 06:47:06 UTC
Please schedule further testing based on comments above.
Comment 9 James Richardson 2008-07-02 06:56:47 UTC
*** Bug 8629 has been marked as a duplicate of this bug. ***
Comment 10 Marc Auslander 2008-07-02 07:32:18 UTC
My bug has been marked a dup of this.

My bug reports failure both on SB3 and Receiver with todays 7.1.
Comment 11 Spies Steven 2008-07-02 15:26:41 UTC
Bug 8629 is most likely a duplicate of Bug 3383 not this bug. 
Comment 12 Spies Steven 2008-07-02 15:55:07 UTC
I am still not able to reproduce using the instructions from comment #7 running SqueezeCenter 7.01 or 7.1 on Ubuntu 8.0.4.

Greg, have you tried doing full factory resets on your Receivers?  You can do this by holding down the front button until the light blinks fast before releasing.  Takes a little over 5 seconds.  You will then have to run though setup again to connect it back to your network unfortunately.

If the issue continues perhaps some logging is in order.
Comment 13 Greg Heinzinger 2008-07-02 16:18:50 UTC
In response to comment #12.

I did do the factory reset on the Receivers -- this was the only way I could get things working again once they locked up.

When I get a few hours I will try to SqueezeCenter 7.1
Comment 14 Greg Heinzinger 2008-07-05 16:55:43 UTC
I tried again this weekend to reproduce the error.  This time I could not get the system to stop functioning, even when trying all the scenarios I had outlined previously.

The system has been working fine the past week configured as follows:
   SqueezeCenter 7.0.1
   SqueezeBox V3
   Receiver
   Receiver

During the testing I added a SqueezeBox V1, but despite repeated attempts stopping & starting various radio streams they continued to play correctly.  And if I tried them on the SBV1 it just sent a message saying it didn't understand the format, but the others kept working.

One odd thing happened this past week (which happened once before).  The first Receiver that I purchased locked up (just put out static) -- I had to do a full reset on it to get it working properly -- it had done this once before.  I am suspicious that maybe I have a bad Receiver that is causing the problems.
Comment 15 Chris Owens 2008-07-07 10:27:15 UTC
I wouldn't have expected the xilinx to have this effect, but who knows.  If anyone continues to see this, please re-open so we can have another look!