Two guide records can appear to overlap because their times conflict, their channel mapping is wrong or the source intentionally represents several items in one slot. Inspect the actual records before assuming every overlap is a duplicate programme.
XMLTV can describe multiple programme components sharing a timeslot through its clump information. It also defines start and stop boundaries so adjacent ordinary programmes need not overlap at the shared boundary. Context and the stated fields matter.
Compare identities and intervals
A fictional listing might separate “News” and “Weather” inside a combined scheduled slot. Another pair might accidentally give an earlier programme an end time beyond the next programme’s start. These cases look similar in a grid but describe different data problems.
Check that both records belong to the same guide channel. A faulty mapping or combined view can make unrelated editions appear together. Fixing timestamps would not solve that identity error and could damage otherwise valid records.
Inspect the overlap
A programme ending at 20:00 and the next beginning at 20:00 do not necessarily overlap. Treating the shared boundary as two simultaneous programmes can produce false duplicate warnings. Use the format’s interval interpretation rather than a simplistic equality check.
- Identify the precise channel and the two dated records.
- Compare their start and stop values with offsets preserved.
- Check whether the source intentionally marks shared-slot components.
- Compare the source data with the player’s displayed interpretation.
- Request a source or importer correction only after the responsible layer is clear.
Avoid destructive automatic cleanup
Deleting the shorter record can remove a legitimate component or special segment. Trimming every end time to the next start can hide a genuine schedule revision. Automatic repair rules need a documented purpose and a preserved original, especially when the source has uncertain or optional end times.
When reporting an overlap, include the two harmless titles, channel key and exact dated intervals. State whether the overlap exists in the source or only on screen. That distinction helps the maintainer separate data generation from display layout.
The desired outcome is an understandable schedule that accurately represents the source’s intended events. A visually neat grid is not enough if cleanup has erased weather segments, combined programmes or useful timing context. Keep uncertain cases visible for review rather than inventing precise boundaries without evidence.
Useful answers
Do adjacent programmes sharing one boundary necessarily overlap?
No. The format’s interval interpretation can make them adjacent without overlap.
Can multiple records intentionally share a slot?
Yes. XMLTV has a way to represent clumped programme components.
Should every shorter overlapping record be deleted?
No. First establish whether it is a valid component or a genuine error.