Bug 16798 – Napster: Getting "Audio Stream failed, skipping to next track" - more and more often now

Bug 16798 - Napster: Getting "Audio Stream failed, skipping to next track" - more and more often now

Summary:

Napster: Getting "Audio Stream failed, skipping to next track" - more and mor...

Status:	RESOLVED FIXED

Product:	MySqueezebox.com
Classification:	Unclassified
Component:	Napster
Version:	Prod
Platform:	PC Windows XP

Importance:	P3 major with 3 votes (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-01-13 09:26 UTC by stefan.gruendel
Modified:	2011-04-11 03:25 UTC (History)
CC List:	1 user (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 stefan.gruendel 2011-01-13 09:26:11 UTC

Getting the error message:

"Audio Stream failed, skipping to next track"

more and more often now. Tried a track today 17:57h German Time, it skipped 3 times, with 4th try it played. Seeing also more regularly the "buffering" messages. Obviously this has nothing to do with the track being played, but just to be complete: Today's error happened for

- Track: Smooth Operator
- Artist: Sade Tribute Band
- Album: Smooth Sax Tribute to Sade

Thanks
Stefan

Comment 1 bkev 2011-01-24 08:22:53 UTC

*** This bug has been confirmed by popular vote. ***

Comment 2 bkev 2011-01-24 08:24:46 UTC

A constant and ongoing problem with Napster. has replaced the old "timed out waiting for data" error.

Comment 3 Michael Herger 2011-03-16 06:53:54 UTC

Is this still an issue?

Comment 4 stefan.gruendel 2011-03-24 09:09:11 UTC

(In reply to comment #3)
> Is this still an issue?

I cannot test this right now because there is an issue with the Napster account. I hope this will be solved within the next days, I will check then once again.

Comment 5 stefan.gruendel 2011-04-04 06:35:59 UTC

I was able to do some more tests, and it looks as if the error has gone.

Comment 6 Michael Herger 2011-04-11 03:25:16 UTC

thanks for the feedback.