Bug 6539 - Sync via player UI breaks sometimes
: Sync via player UI breaks sometimes
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Sync
: 7.0
: Macintosh Other
: P2 major (vote)
: ---
Assigned To: Alan Young
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-04 07:44 UTC by Andy Grundman
Modified: 2008-12-18 11:12 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Grundman 2008-01-04 07:44:32 UTC
Play around with syncing/unsyncing 2 players using the player UI.  Sometimes it will fail, I've seen it fail 2 different ways:

After syncing:
Slim::Player::Source::readNextChunk (2328) 00:04:20:10:01:6a: No filehandle to read from, returning no chunk.

On this line in Source.pm, streamformat was undef:

if ($client->streamBytes() == 0 && $client->masterOrSelf->streamformat() eq 'mp3') {

I also see duplicate player names listed in the "can sync with" list in the player UI.
Comment 1 Alan Young 2008-01-06 04:51:10 UTC
What kind of source were you streaming when streamformat was undef?
Comment 2 Andy Grundman 2008-01-06 10:58:44 UTC
Don't remember, actually this problem may have been caused by the bad patch in bug 6528.
Comment 3 Alan Young 2008-01-08 01:29:39 UTC
I doubt that the bad patch was (or should have been responsible) as it would just have reversed the sense of the sync association (master/slave). It should still have worked.
Comment 4 Alan Young 2008-01-11 03:27:07 UTC
It is not just with the player-UI. Basically, if the new slave is already playing, then these kinds of effects can happen.

Change 16147 fixes these specific errors but there is still a need to agree the correct semantics in some cases.
Comment 5 Chris Owens 2008-03-07 09:03:36 UTC
This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.