Bug 9339 - Alarm clock remembers previous time after change
: Alarm clock remembers previous time after change
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Plugin
: 7.3.0
: Macintosh MacOS X 10.5
: -- normal (vote)
: 7.x
Assigned To: James Richardson
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-29 19:14 UTC by Jason Snell
Modified: 2009-07-31 10:28 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Snell 2008-08-29 19:14:52 UTC
Here's the situation.

I have an alarm for the week. It's set to, let's say, 7:30 a.m. M-F.

My daughter's first day of 2nd grade, my wife needs to get up earlier. I edit the alarm on the Boom, setting it to 7:00.

The next morning, the alarm goes off at 7. And then again at 7:30.

That night I set the alarm to 7:15.

The next morning, the alarm goes off at 7:15. And then again at 7:30.

In other words, it appears the alarm is triggering TWICE -- once for the current setting and once for the previous time setting, even though it's been changed.

I'm running Nightly Build 8/28 of 7.3.
Comment 1 Jason Snell 2008-08-29 19:16:36 UTC
Forgive me, in the above example the second morning would have gone off (and, indeed, DID go off) at 7 (the previous day's time) and 7:15 (the current day's time). The behavior is definitely the previous alarm time plus the current alarm time, regardless of which one happens first. 
 
(Since I have alarms set to fade in, I can tell when the alarm is re-engaging, because the volume drops to zero and then fades in again.)
Comment 2 James Richardson 2008-09-02 08:58:14 UTC
Jason:

1) What Time Format did you select for SC.  Settings > Interface > Time Format

2) Please set player.alarmclock to debug, then shutdown SC, clear the log files. Restart SC and edit your alarms as described above again.  Then attach the log file to this report.

I attempted to replicate your error, but ran into other problems with the alarm code in 7.3 which prevented me from continuing.
Comment 3 Max Spicer 2008-09-02 09:28:08 UTC
Alarm in 7.3 is probably pretty unstable.  There were known problems with the new streaming code and the alarm code.  I haven't looked at 7.3 yet.  That said, I wouldn't expect the described behaviour - it sounds pretty odd!
Comment 4 Max Spicer 2008-09-28 14:38:38 UTC
More info needed.
Comment 5 Jason Snell 2008-09-28 15:04:40 UTC
Due to future builds breaking AAC support, I'm still running the daily from August 28. I can give you more details if you want but I fear that they might not be useful given the "other problems with the Alarm Clock code."
Comment 6 Dana Tak 2008-09-30 23:57:42 UTC
I have been fooling around with the volume control for the alarms and I cant find a way to set the alarm to one volume setting and the player to another.  Also I have set the alarm volume and then backed out of the screen to set it, then went back to check to make sure that the volume is set the volume is set at the orignal setting(before I altered it).  If you could press the center button on the duet to set the volume it would be nice.  I am using the latest release of 7.2.
Comment 7 James Richardson 2008-10-30 14:11:44 UTC
Please test with the latest 7.3 nightly build to verify if this issue still exists.  There were a few fixes checked in that may address this issue.
Comment 8 James Richardson 2008-11-10 16:31:16 UTC
I have not been able to repoduce the orgianl reported error with 7.3

Marking bug as fixed, if you still see this issue please reopen and attach a log from player.alarmclock

As for the other issue, please open or search for already open bugs.  Make sure to do 1 bug per issue.
Comment 9 James Richardson 2008-12-15 12:06:39 UTC
This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Comment 10 Chris Owens 2009-07-31 10:28:28 UTC
Reduce number of active targets for SC