Bug 12285 - WMA playback issue Fab4 only
: WMA playback issue Fab4 only
Status: CLOSED FIXED
Product: SB Touch
Classification: Unclassified
Component: Audio
: unspecified
: PC Windows XP
: -- normal with 1 vote (vote)
: CAT
Assigned To: Richard Titmuss
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-05 10:32 UTC by James Richardson
Modified: 2009-10-06 09:22 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Richardson 2009-06-05 10:32:29 UTC
Napster playing on the Fab4 via SN will stutter and rebuffed contently.

Other IP3K players attached to fab4.sn do not have this issue.

More noticeable when you FF or RW a track
Comment 1 Rudolf Janz 2009-06-06 08:09:10 UTC
It is not only Napster. Playback of WMA files from Squeezecenter (7.4 - 26787, F4: 6026) stutters as well (mostly at the start of the song)
Network is ok, the problem did not happen before. MP3 files seem to be ok, 

One more thing, the pushup message (displaying only the song title) makes the stuttering worse. I saw this problem very often on the Squeezeplay Windows Mobile port. The decoder could not keep up at the beginning. THe display of the rebuffering message box used up so much CPU, that the stuttering repeated for a while.
Comment 2 FredFredrickson 2009-06-11 06:10:49 UTC
Same experience as Rudolf Janz, Local WMA is skipping. Rhapsody is doing the same from what I can see. Sirius is too (not sure if it's related). Local MP3 and Shoutcast are working just fine.

The little popup is having a hayday during the skipping.
Comment 3 radish 2009-06-14 12:46:09 UTC
Just wanted to add that I'm seeing this as well, with Napster. I don't have any local wma files.
Comment 4 Richard Titmuss 2009-06-17 08:17:39 UTC
Fixed in private repo r6143. Should appear in a public build > r6140. (It's confusing as both repo's have similar rev numbers at the moment).
Comment 5 James Richardson 2009-10-06 09:22:50 UTC
This bug has been fixed in the latest release of MySqueezebox.com (formally
known as SqueezeNetwork)!

If you are still experiencing this problem, feel free to reopen the bug with
your new comments and we'll have another look.