Grass Valley K2 Edge Daylight Saving Time V.4.1 - Manual (Page 3)

K2 Edge Version 4.1 Daylight Saving Time (DST) - 3
1 About this document
This document describes Daylight Saving Time (DST) expected behavior and recommendations for K2
Edge Version 4.1.
2 Expected Behavior
For all systems that experience a time change, the effects described below can be expected:

Systems syncing time to a NTP-server will follow daylight saving automatically as it is served by
the server. Automatic time change by the NTP-server implies that the playlist must be set properly
around the time jump. An event should be started before 2am and the next event should be fixed
and calculated after 3am. That is difficult and not recommended.
Note: only if configured in a timezone.

Systems running on GMT without an offset will continue as normal.

Free running systems will not automatically participate in daylight saving and will continue with no
time change unless the system is set to a time zone, but this is not recommended (the default for
K2Edge is Etc/Universal).
Note: configure in a timezone is not supported.

Systems synced to a LTC will continue as normal unless the LTC-clock is participating in daylight
saving as well.
3 Recommendations
3.1 Systems synced with LTC and running with an offset from UTC
For instance, a system in Paris runs at UTC+2 during the summer and at UTC+1 during the winter. In this
situation LTC is running on UTC, so without an automatic clock change.
o When the clock moves forward, a schedule of 23 hours is loaded.
When a normal schedule is from 6am till 6am the following day, it should now be from
6am till 5am the following day.
o When the clock moves backwards, a schedule of 25 hours is loaded.
When a normal schedule is from 6am till 6am the following day, it should now be from
6am till 7am the following day