YOUR STORY PLAYS HERE
Home » Categories » Cablecast

Issues Scheduling Cablecast When Daylight Savings Time Changes

Time is an Illusion. Lunchtime Doubly So

This is embarrassing, but Cablecast has a long standing bug that seems to be impacting people more and more. This short story is that the database that powers Cablecast does not store date values in such a way that supports Daylight Savings Time. In short, scheduling programming during or over Daylight Savings Time changes is likely to create an unpredictable schedule and should be avoided. For best results, leave your schedule on default source from 1:00 am to 3:00 am during Daylight Savings Time changes, which this year occurs on March 12th and November 5th.

The Nitty Gritty Details

The DST bug is not new in Cablecast. In fact, Cablecast has never properly supported DST. Before versions 6.0, the user interface was rendered on the server meaning that all times were always rendered in server time. The server rendering of the user interface was not time zone aware; therefore, it would just show a normal looking 24 hour schedule even on days where DST would start or end.

In Cablecast 6.0, the schedule moved to being created in the users web browser. This included new libraries and user interface functions that unlike the Cablecast backend, were DST aware. This creates a problem because the UI can allow you to schedule things in the extra hour that is present in the fall when DST "falls back". The new user interface also doesn't show the missing hour when DST "springs forward" in March.

This is wonderful except for the fact that Cablecast's database is still ignorantly unaware of DST. In fact, it is actually unable to differentiate between non DST values and DST values. This leads to an issue where when the schedule submits values that are valid in DST. The database will store them and then return them as a different time because the database is unable to store the required level of precision for DST. This leads to scheduling something at 3:00 am but having it saved as 2:00 am in the database. There is currently no workaround for this except to leave the schedule on a live default source.

To re-iterate this bug is not new, it just exposes itself in a more frustrating way now that the Cablecast schedule is capable of understanding the difference between DST and non DST. As our customers continue to provide a better experience for their viewers by scheduling more important, original, and local content at all times of the day, this bug has made itself more apparent. We are sorry for not identifying this issue sooner and addressing it quicker. We plan to have it addressed for the fall of 2017 when Cablecast schedules all over the country will once again "fall back", except in Arizona.

 

 

0 (0)
Article Rating (No Votes)
Rate this article
  • Icon PDFExport to PDF
  • Icon MS-WordExport to MS Word
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
Cablecast Screenweave is Released (OTT support for Apple TV & Roku)
Viewed 501 times since Thu, Jul 12, 2018
About Tightrope’s software version numbers
Viewed 3517 times since Wed, Dec 17, 2014
’A reboot will be required’ message is shown when uninstalling Cablecast
Viewed 2152 times since Mon, Sep 22, 2014
Cablecast Passthrough Feature Overview
Viewed 759 times since Tue, Aug 8, 2017
Network Requirements for Live and VOD
Viewed 2363 times since Fri, Jul 17, 2015
Cablecast - Widescreen Resolution
Viewed 222 times since Thu, Jul 12, 2018
How to configure and test my Blackmagic Videohub router with Cablecast
Viewed 2625 times since Thu, Sep 18, 2014
Identifying Your Current Version of Windows
Viewed 1582 times since Fri, Aug 21, 2015
How to link a specific video file to a show
Viewed 1983 times since Fri, Sep 19, 2014