Bug 10956 - Rebuffering at every track change
: Rebuffering at every track change
Status: RESOLVED INVALID
Product: SB Touch
Classification: Unclassified
Component: Audio
: unspecified
: PC Windows Home Server
: -- normal (vote)
: ---
Assigned To: Alan Young
http://forums.slimdevices.com/showthr...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-04 10:04 UTC by Sue Chastain
Modified: 2009-09-08 09:19 UTC (History)
0 users

See Also:
Category: ---


Attachments
log file (235.05 KB, application/zip)
2009-02-04 10:04 UTC, Sue Chastain
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sue Chastain 2009-02-04 10:04:00 UTC
Created attachment 4764 [details]
log file

I am frequently getting a "rebuffering" popup at every track change on both Fab4 and SqueezePlay desktop. The rebuffering message appears just as a new song has begun to play. A log of this from the Fab4 (not synced) is attached. There are three track changes in this log and the rebuffering happened on all of them. These were normal track changes, not manual skips.
Comment 1 Alan Young 2009-02-04 11:49:19 UTC
Sue, something looks well-iffy with the network connection between your SB and the player. The log show 6s between the player being sent the stream command and SC getting the acknowledgement (STMc). This should be more like 100ms. And even after establishing the stream connection back to SC, it takes a few seconds for the data to start flowing.

More evidence of this comes from the latency reports: (13.5, 16, 8, 13, 17.5, 14.5, 6, 346.5, 37, 140.5). Those are milliseconds and they should all be about the same. It is ok to have the occasional outlier (that is why SC tracks a series of them) but you seem to get them very frequently.

I know that you say that the same thing happens with desktop SP. Is it running on the same system as SC? Even if it is, then the cause could be different.
Comment 2 Sue Chastain 2009-02-05 16:13:18 UTC
I'm closing this bug, as it was caused by a plugin I was using and I have found a workaround.