17 Jul
2014
17 Jul
'14
8:20 a.m.
Am 02.07.2014 um 16:59 schrieb Carsten Kurz:
Carl, how is DCP-o-matic dealing with local time/GMT
when creating the KDM and during email transmission? Will it automatically convert local
machine time to GMT according to machine time settings?
Then how is $START_TIME and $END_TIME calculated and displayed?
All KDM providers we dealt with so far automatically convert to local time for Email
transmission notification text. That is because they have a location and time-zone
associated to every cinema in their database.
I can answer this myself now: DCP-o-matic is properly using and converting local time (at
least in windows) for email transmission text and KDM:
Email:
----
Im Anhang finden Sie die KDM fuer den Film
Lebensfilm_FTR-1-25_F-178_DE-XX_DE-FSK0_51_2K_AVS_20140709_AVS_SMPTE_OV.
Der Schluessel ist vom 2014-Jul-16 04:59:11 bis zum 2014-Jul-23 04:59:11 gueltig fuer:
---
KDM:
---
<ContentKeysNotValidBefore>2014-07-16T04:59:11+02:00</ContentKeysNotValidBefore>
<ContentKeysNotValidAfter>2014-07-23T04:59:11+02:00</ContentKeysNotValidAfter>
---
This is for germany, so currently +02:00 is correct for central european summer time. I
also like the '2014-Jul-23' format in the KDM email text, because it prevents the
typical 1-12-2014 and 12-1-2014 cross-country confusion.
But bear in mind, if you are sending/issuing a KDM for playout in a different time zone,
that it will be referenced typically to YOUR local time, not the playout location's
local time. If you want to be sure, temporarily set your computers time zone identical to
the playout locations time zone, create the KDM/Email, then set it back.
Even better - never issue KDM time frames that could cause prohibitive playout windows due
to time zone differences. Always allow at least 1-2 days safe margin head and tail.
- Carsten