Playlists are saved for a non-synced player at server shutdown and LMS will resume playing at the start of the track that was being played when shutdown was initiated. However, this doesn't work for synced players. A synced group of players will start somewhere on the playlist, usually quite a few tracks earlier than the last track playing at shutdown. This has been happening for a while, maybe since before 7.9 - I just lived with it until I saw this post http://forums.slimdevices.com/showthread.php?103755-loss-of-playlist&p=820549&viewfull=1#post820549.
It becomes very evident if the master player of a sync group is using SugarCube to queue up tracks. Resuming play after a shutdown can start days earlier in a playlist. I'm not sure what the original design aim was for playlists of synced players, but I think that if a player is synced with another player then their playlists are common. Then when a server shuts down, for a synchronised group of players the current playlist should be saved for each player. This is not an earth shattering show stopper of a bug, just a nuisance when you become aware of it. And if you do revisit synchronisation of players, maybe the message "The player can be synchronized with other players, enabling them to play the same music simultaneously. Choose the players you would like to synchronize with from the list of available synchronization groups. Choose No Synchronization to stop synchronization." could be made more clear to indicate which player becomes master and which players are slaves as I always get a surprise as usually the wrong playlist starts playing when I sync players. A camel is a racehorse designed by a committee. ------------------------------------------------------------------------ Wirrunna's Profile: http://forums.slimdevices.com/member.php?userid=3225 View this thread: http://forums.slimdevices.com/showthread.php?t=101516 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
