Bug 2643 - SB3 alarm clock only plays one track
: SB3 alarm clock only plays one track
Status: RESOLVED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Playlists
: 6.2.2
: PC Windows XP
: P2 minor (vote)
: ---
Assigned To: Chris Owens
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-11-28 05:43 UTC by William Savage
Modified: 2008-09-15 14:39 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description William Savage 2005-11-28 05:43:53 UTC
I use my two SB3 units on a daily basis as alarm clocks with the following settings:

Not synchronized
Shuffle: Songs
Repeat: Off
Slimserver version: 6.2.2

Each is set for a different playlist at a different time in the Alarm settings.

When each unit goes off, it plays one track from the assigned playlist, then stops.  While I realize that a simple work-around might be to turn Repeat on, I'd rather the alarm clock function simply play the entire playlist.  My previous SB1 units didn't have this problem, so something has apparently changed.
Comment 1 KDF 2005-11-28 09:00:35 UTC
did you look at bug 2245?
Comment 2 William Savage 2005-11-28 18:44:37 UTC
Subject: Re:  SB3 alarm clock only plays one track

Yes, I read that before writing my own bug report.  I don't see any 
relevance, but then I'm not technically oriented.  I just want it to 
work like my previous SB1 units did.  I continue to install the 
SlimServer Nightlies, but the problem persists.



>https://bugs-archive.lyrion.org/show_bug.cgi?id=2643
>
>
>
>
>
>------- Comment #1 from slim-mail@deane-freeman.com  2005-11-28 09:00 -------
>did you look at bug 2245?
>
>
>
>
>------- You are receiving this mail because: -------
>You are on the CC list for the bug, or are watching someone who is.
>You reported the bug, or are watching the reporter.

Comment 3 Dan Sully 2005-11-29 16:51:51 UTC
William - does it work when Repeat is on?

Could you attach your slimserver.pref file and an example playlist?

Thanks.
Comment 4 Dan Sully 2006-04-20 17:10:44 UTC
Ping - William- can you please attach your slimserver.pref and an example playlist if this is still happening?

Thanks
Comment 5 KDF 2006-04-25 12:29:32 UTC
Might also be useful to see the d_source log from the point the alarm triggers.  This should show at least the process by which playback halts.
Comment 6 Ross Levine 2006-06-15 18:17:01 UTC
I am struggling to reproduce this bug. Here's what I did:

XP w/ SP2, XP firewall only, no anti-virus software. 
SlimServer 6.2.2, with a Squeezebox 3. 

I loaded an album, then I created an m3u playlist WITH slim server, and saved it to my playlist directory. 
I changed my music player settings to REPEAT: OFF, SHUFFLE: SONGS. Then on SB3 -> settings -> Alarm clock 
-> Alarm Playlist -> alarm test playlist. I set the alarm to go off in 5 minutes. 
The playlist contains half the album (6 songs). 

I let the alarm go off, and it did not stop after one song, it continued to play. 

Then I deleted all the music, and the playlist. I loaded up a different album, created a new playlist in the 
same fashion as before. Made a new alarm, and this time I changed POWER: <to> OFF (Music player settings within SS)
Let the alarm go off, same thing, first song plays, followed by the next song. 

William, do your playlists work fine when playing them normally? You only see this 'one song then stop' 
behavior with the alarm feature? 

Any other ideas on how I can reproduce this? 
Comment 7 KDF 2006-06-18 02:01:50 UTC
willing to lend a hand at this one, if we have d_source logs (even a huge one can be sent to slim-mail at deane-freeman.com).

how about the playlists selected?  do they play manually?

and, just to be thorough, this is the built in alarm rather than the plugin version?
Comment 8 Chris Owens 2006-06-23 14:47:43 UTC
William, are you able to provide answers to Dean and Ross's questions?  Do you need more detailed instructions on how to find the answers?
Comment 9 Chris Owens 2006-06-30 14:52:09 UTC
Marking this as 'worksforme' at this time.  You're welcome to re-open it in the future, and we'll keep an eye out for related issues.

Thanks for the information, William.