Bug 17926 – Sirius stream garbled

Bug 17926 - Sirius stream garbled

Summary:

Sirius stream garbled

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Plugin
Version:	7.7.0
Platform:	PC Windows Server 2008

Importance:	-- normal (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-03-15 06:46 UTC by Denny Colvin
Modified:	2012-03-15 18:38 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Denny Colvin 2012-03-15 06:46:38 UTC

Starting yesterday (3/14/2012) the Sirius stream became unusable.  How to describe this?  Assume the stream is in 'bursts', 
i.e., 1----- 2----- 3----- 4----- 5----- 6----- 7----- 8-----
and what I'm hearing is 1----- 2----- 4----- 6----- (rebuffering) 8----- ...

This is on all Sirius channels (that I listen to)

Comment 1 Denny Colvin 2012-03-15 07:02:53 UTC

Update:

This also occurs connecting directly to mysqueezebox.com

Comment 2 Denny Colvin 2012-03-15 11:27:28 UTC

Further update:
This does NOT occur on the SirusXM website stream or the iPhone app stream,
but it DOES occur on a Sirius Stiletto 2 connected via WiFi.

I spoke to Sirius and they are aware of the problem... Ticket 632075.

So, not a Squeezebox problem.

Comment 3 Andy Grundman 2012-03-15 13:06:43 UTC

So can we close this bug you think?

Comment 4 Denny Colvin 2012-03-15 13:14:28 UTC

I'd leave it open until Sirius gets this fixed, if for no other reason than someone else might search the buglist for the problem.  And if it continues, somebody at Logitech might want to poke someone at Sirius.

I'll update when it's fixed (hard to believe it's been broken for nearly 48 hours now, without a fix).  Sirius said it also affects *their* tabletop radios.

Comment 5 Denny Colvin 2012-03-15 18:37:29 UTC

Sirius appears to have fixed it now.