Dolby/Doremi DCP2K4 and Daylight Savings Time

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Ryan Gallagher
    Film God
    • Nov 2022
    • 2912
    • Austin, Texas, USA

    #1

    Dolby/Doremi DCP2K4 and Daylight Savings Time

    Here is a head scratcher, maybe someone else with a DCP2K can report if we are alone in this anomaly.

    Our up to date DCP2K4 appears to have applied the Daylight Savings Time correction EARLY (Nov 1st this year). I'm not in the building but can check tomorrow. My co-projectionist reported this. We are suddenly an hour out of real-time and somewhere they were able to see that it is reporting the "Next" time-change to be April 2027.

    Our server has never had a TMS or used a local or internet time server for sync other than during intentional corrections. It does drift. We applied a big correction not too long ago and still have correction quota available. But is having a NTP server configured necessary to keep it picking the correct DST change dates too?

    Most of this festival is unencrypted. During prep yesterday I noted one tech window KDM that was 15 min after the scheduled hour venue window, but I did NOT catch that it appeared to be due to our server time having bonked itself out by a full hour!! Honestly I was too busy dealing with moving all their festival features and content off the delivered ExFAT drives so that we did not fall behind on ingesting on Day 1.

    The logical follow up is does it have the correct DATE! lol. I'll have to investigate tomorrow.
    But I think I can rule that out from home. The festival keys were extremely tight, within the day/hour. So they would have been way out in terms of validity window if the server date was wrong too.

    Due to some serendipitous tech window schedule shifting by the festival anyway, this issue did not bite us day 1. But it may as we get the outstanding keys. I'm tempted to do the NTP time correction steps first thing in the morning.
    Last edited by Ryan Gallagher; 10-29-2026, 07:54 PM.
  • Ryan Gallagher
    Film God
    • Nov 2022
    • 2912
    • Austin, Texas, USA

    #2
    Afterthought... we do have a deluxe e-deliver server now. Are they configured to be a suitable authority time server on the media network? I could point it at that if so.

    Otherwise I'll just put eth1 on the LAN temporarily like I did before and perform a one time re-sync.

    After After Thought (Edit): This can't be DST related can it? Cause KDMs are in UTC from what I know, and checked against UTC. So it has to be drift! But less than a couple weeks ago it was only a few minutes out.
    Last edited by Ryan Gallagher; 10-29-2026, 09:07 PM.

    Comment

    • Ryan Gallagher
      Film God
      • Nov 2022
      • 2912
      • Austin, Texas, USA

      #3
      Regardless of cause... none of our remaining festival keys were tight enough to justify poking it mid-festival. I'll do a NTP resync after the fest and see where it lands. Ideally I try it before the 4th and see if it's still an hour out? Our last NTP resync on that server was maybe a year ago.

      Comment

      • Ryan Gallagher
        Film God
        • Nov 2022
        • 2912
        • Austin, Texas, USA

        #4
        That will re-teach me to gut check AI search responses, which initially got the DST date wrong for 2026. It’s not the 4th! It is 1st Sunday in November. AKA tonight/tomorrow at 2am.

        Bonus. Extra hour of Halloween night! (That feels somewhat rare alignment). Every 7-11 years apparently.

        Comment

        • Ryan Gallagher
          Film God
          • Nov 2022
          • 2912
          • Austin, Texas, USA

          #5
          To close this loop... it was indeed an early DST "fall back" adjustment on our air-gapped Doremi server. Today it caught up... not because it did anything, but because the time caught up with it!

          Boy that would have really been a KDM disaster if we had a higher profile festival with more encrypted content. Only 4 of our titles had KDMs, and only one provided tight tech and show keys.

          I'm not sure how to prevent this going forward other than to give it an NTP source that is permanent? Doesn't feel like a bug or surely others would have run into it?

          Comment

          • Dave Macaulay
            Pro Film Handler
            • Jan 2020
            • 464
            • Toronto, Ontario, Canada

            #6
            KDMs are on UTC. The real window does not change. Your scheduling will be off, yes. The usual quick fix is to change your location to somewhere, anywhere, that is on the same time as yours really is. The confusion is real, a lot of jurisdictions are changing how their timezones work. Hopefully Dolby and the others will spend a few hogsheads of coffee and late nights getting an update together that corrects it. Here in Ontario, it's pretty weird. We have two time zones, Eastern and Central. From what I can figure out, part of the Central zone is staying on daylight time, but not all of it.

            Comment

            • Ryan Gallagher
              Film God
              • Nov 2022
              • 2912
              • Austin, Texas, USA

              #7
              Originally posted by Dave Macaulay
              KDMs are on UTC. The real window does not change. Your scheduling will be off, yes. The usual quick fix is to change your location to somewhere, anywhere, that is on the same time as yours really is. The confusion is real, a lot of jurisdictions are changing how their timezones work. Hopefully Dolby and the others will spend a few hogsheads of coffee and late nights getting an update together that corrects it. Here in Ontario, it's pretty weird. We have two time zones, Eastern and Central. From what I can figure out, part of the Central zone is staying on daylight time, but not all of it.
              yeah a friend is in BC, where large parts of the province are getting rid of it (but not all). But nothing has changed here in Texas so can’t even blame that.

              Comment

              • Frank Cox
                Film God
                • Jan 2020
                • 2337
                • Melville Saskatchewan

                #8
                Have you tried telling it you're in Bogota?



                Microsoft's temporary fix involves pretending you're somewhere else entirely. Depending on the product and province, that could mean Saskatchewan, Arizona or, for Manitobans, Bogota. Because apparently time zones weren't confusing enough already.


                When I was a kid it seemed that every town had its own time zone. The town where we lived was on a different time zone than the city 60 miles away and the difference changed twice a year. Which made it confusing for people who made an appointment in the city for doctor/dentist/lawyer/whatever.

                I remember that we were always calculating time differences for the television schedule that was printed in the paper (from the city), as well.

                Then in 1966 the provincial government finally decided that this was silly and put the whole province on one single time zone, and we've been on Central Standard Time ever since. No changing for daylight saving time either.

                The Linux time zone data is stored in /usr/share/zoneinfo and it's updated several times a year, so worldwide time zones seem to change on a regular basis.

                Comment

                • Leo Enticknap
                  Film God
                  • Jan 2020
                  • 3629
                  • Loma Linda, CA

                  #9
                  The same thing happened in the US. This book is well worth a read: it explores the history of how time zones and DST became the political hot potato that they are. A federal law made here at around the same time (late '60s) tried to bring order to the chaos by splitting the lower 48 into three time zones only, and allowing states to decide if they want to do DST or not. But it they do, it has to be statewide (no cities or counties doing their own thing), the offset has to be one hour, and the change has to be on the same day nationwide. Before this law came in, it was possible to travel through 20-30 time zones in the course of a one-day road trip! A particular irritant near here was that Palm Springs (only within that city's limits) had its own time zone for a few years. This was 30 minutes offset from the rest of California, in order to squeeze just that little bit extra daylight before the sun disappeared behind a large mountain to the west.

                  Comment

                  • Tj Hopland
                    Pro Film Handler
                    • Jun 2025
                    • 270
                    • Minneapolis, MN

                    #10
                    I don't remember the exact DCI spec, maybe someone else knows for sure but key only has to be valid to start the playback and then there is like a 4 (or 6?) hour window for the show to complete. So key expires at 1300 if you start the show at 1259 and its finished by 17000 you are fine. If you stop it after 1300 you won't be able to re start it but it won't just quit at 1300.

                    Comment

                    Working...