Bug 2742 - Playback freezes in several cases
: Playback freezes in several cases
Status: RESOLVED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Audio
: 28
: PC Linux (other)
: P2 major with 1 vote (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-12-22 14:31 UTC by Daniel I. Applebaum
Modified: 2006-04-21 16:46 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel I. Applebaum 2005-12-22 14:31:29 UTC
I have two recently purchased SB2 units running firmware 28.  They are connected to a Linux (2.6 kernel) machine (1.5GB RAM, 700MHz) running SlimServer 6.2.1 - 5194.  Every once in a while, especially while running synchronized, the playback of FLAC encoded music will halt at the end of a file, and not resume automatically.  I have left the units for up to ten minutes in this state.

The user interface remains responsive, I can get playback to continue immediately by pressing Play or otherwise affecting the transport.

The network between the SB2s and the Linux machine are pairs of ViewSonic wireless bridges that work flawlessly for other network nodes.

This seems related to bug 1595.

I have had other issues: sometimes playback halts in mid-song, and sometime when starting to play while synchronized, one unit will output several loud crashing noises, then cease playback entirely until power cycled.  I do not know if these are related.
Comment 1 Jason 2006-02-27 20:52:42 UTC
I experience FLAC encoded music halting at the end of a file as well. Although it seems to be repeatable with the same files. I have no trouble with mp3 files. Manually skipping to the next song resumes playback.

I am running Slimserver 6.2.2 on Linux and using a Squeezebox 1.
Comment 2 Blackketter Dean 2006-04-21 16:46:42 UTC
Please update to the latest 6.2.2 prerelease, a number of bugs where the player would spontaneously stop have been addressed.  If you are still having the issue, please reopen the bug.  If you find it fixes your issue, please confirm. Thanks!