EPG (Electronic Program Guide)
A scrollable 24-hour EPG with per-channel programs, import support and a program editor. Schedule ahead, import XMLTV, and publish a consistent guide across every client.
Visual grid
Per-channel horizontal 24h timeline.
Import
Bulk-import programmes from external sources.
Quick add
Add channel or single programme inline.
Live marker
Real-time now-line across the guide.
Getting guide data in
Guide data usually arrives as XMLTV from a data provider or the broadcaster, and is imported on a schedule so the grid stays populated several days ahead. Channels can also be created and individual programmes added inline for lineups that have no upstream feed, such as an in-house channel.
Imported data almost always needs mapping and clean-up: channel identifiers rarely match your internal channel IDs, genre taxonomies differ between providers, and artwork may be missing or in the wrong aspect ratio. That mapping layer is what turns a raw feed into a guide viewers can use.
Rendering a guide on a television
An EPG on TV is a demanding UI. It is a large two-dimensional grid navigated with a D-pad, on devices with limited memory and slow scrolling, so it has to virtualise aggressively - render only the visible time window and channel rows, and fetch the rest as the viewer scrolls. A grid that loads a full day for eighty channels up front will run out of memory on entry-level hardware.
A live now-line, clear focus states and prefetching of the next screen of data are what make the difference between a guide that feels instant and one that feels broken, particularly on older Tizen and webOS models.
Keeping the guide accurate
Schedules drift. Sport overruns, news specials get inserted, and a guide that still shows the planned schedule while something else is airing undermines every feature built on top of it - now-playing, start-over, recording. Handling live updates to the current and next programme matters more than having data far into the future.
The guide is also the backbone for DVR and recording features, so guide accuracy is worth monitoring as an operational metric, not treated as static reference data.
Inside the CMS
Frequently asked questions
- Do you support XMLTV?
- Yes, XMLTV import is supported, along with provider-specific feeds and manual entry for channels with no upstream data.
- How far ahead can the guide run?
- As far as your data source provides - typically seven to fourteen days. The grid itself is per-day and per-channel, so longer horizons are a data question rather than a platform limit.
- Can programme artwork come from the guide feed?
- Yes, where the feed supplies it. Feeds that do not include images, or supply them in the wrong aspect ratio, are handled by the mapping layer with fallbacks.