beautypg.com

Clock jump procedure – Grass Valley K2 Edge Daylight Saving Time V.4.1 User Manual

Page 4

background image

K2 Edge Version 4.1 Daylight Saving Time (DST) - 4

3.2 Clock jump procedure

Scenario 1

– Clock moves forward an hour

The weekend the daylight saving will be applied in the night of Saturday on Sunday; the clock will jump
forwards on 01:59:59 to 03:00:00 hours.

Environment

External LTC given in UTC.
Offset according to region set in

\\IP_K2Edge\delta\nexos-init-params.txt

{timecode-offset-sec} {3600} #(UTC+1H)

Main and backup K2 Edge servers are in sync.
A 23 hours schedule is loaded.

A 23 hours continuous schedule is available so the K2 Edge will play out as normal. The only change is
that the clock of the K2 Edge servers should jump with an hour. To maintain continuous playout, this is
done step by step, first the backup and later the main K2 Edge.

Main (at UTC+1) on air
Backup (at UTC+1)

 Main (at UTC+1)

Backup (at UTC+2) on air

 Main (at UTC+2) on air

Backup (at UTC+2)

For automation and scheduling, Operators and Schedule Creators should take note of the following:

The playlist should be running on both the main and backup servers and should be perfectly
synced.

Ensure that main K2Edge server is ON AIR

On the K2 Edge backup server: change the offset in Offset according to region in

\\IP_K2Edge\delta\nexos-init-params.txt

{timecode-offset-sec} {7200} #(UTC+2H)

On the K2 Edge backup server: once the playlist has synced, stop the schedule_sync process.

On K2 Edge backup server: reschedule the next event with starttime = starttime + 1h

On K2 Edge backup server: check if the SDI-outputs of the main and backup servers are in sync
while playlist start times on the main and backup servers differ 1h (the main server is behind of
the backup server).

Switch the backup K2Edge server to ON AIR.

On the K2 Edge Main server: change the offset in Offset according to region in

\\IP_K2Edge\delta\nexos-init-params.txt

{timecode-offset-sec} {7200} #(UTC+2H)

Reboot the K2 Edge main server.

On the K2 Edge main server: reschedule next event with starttime = starttime + 1h.

On the K2 Edge main server: remove already played out elements that are in overrun.

On the K2 Edge main server: check if the SDI outputs of the main and backup servers are in sync.

Switch K2 Edge main server to ON AIR.

Reboot the K2 Edge backup server.

The playlist should be running on both the main and backup servers and should be perfectly
synced.