Identify which clock is wrong
A guide can show the wrong programme while the media itself plays smoothly. A device can display an incorrect local time while the source's timestamp is valid. A live session can also sit behind the current edge after a pause. These are distinct observations.
Record the date, named time zone, selected channel edition and actual picture. A bare “8 pm” is ambiguous across Canada and international sources. Do not convert a schedule problem into a media-timestamp claim without relevant diagnostics.
Read offsets explicitly
A timestamp with a UTC offset identifies a particular time context. Converting it to the viewer's local time requires the applicable date and zone rules. A fixed offset remembered from another season can be wrong where daylight rules apply.
An illustrative 20:00 at UTC−05:00 corresponds to 01:00 UTC on the next day. That arithmetic does not identify the correct local zone for every Canadian city or establish that a broadcaster intended that timestamp. Keep the source value alongside the converted observation.
Use timing metadata as supporting evidence
If the player exposes programme date-time, note the actual field and media position. Do not infer it from a segment filename or sequence number. A number that resembles a date can serve another internal purpose.
Compare the intended programme with the current official schedule separately. If the media timestamp and guide disagree, report both values and their sources. The operator can then inspect source timing, guide mapping and client display rather than receiving a broad “EPG broken” claim.
Keep a correction scoped to its layer
Changing a guide offset does not rewrite source timestamps. Changing the device clock to force a match can create secure-connection and other application problems. Use accurate device time and the player's documented guide controls only where evidence supports them.
After a supported correction, retest the original edition and date. Confirm the visible programme as well as the displayed time. A successful clock conversion cannot establish catch-up retention, live-delay guarantees or account access; those remain separate facts.
Related questions
Is programme date-time the same as the channel's advertised schedule?
No. It is media timing metadata. A schedule describes planned programme times and requires its own source and edition context.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- RFC 8216: HTTP Live Streaming — HLS playlist and delivery mechanisms; examples are illustrative, not service measurements.
- Apple Developer: HLS authoring specification for Apple devices — Relevant HLS publication mechanism; illustrative household comparisons are editorial, not a service test.
