In this guide
Record one concrete mismatchVerify the candidate identityChange one mapping and verify across timeA guide can be populated and still belong to the wrong feed. Similar channel names make this especially easy with regional editions, delayed versions and services that share branding.
Treat a name match as a candidate association. Verify the schedule identity using actual identifiers and more than one programme before changing the player mapping.
Record one concrete mismatch
Choose a time where the displayed schedule clearly differs from the programme being shown. Record the channel entry, programme title, local time zone and the guide identifier currently associated with it. A schedule change at the source is also possible, so one mismatch alone does not prove a permanently wrong mapping.
In an original hypothetical example, two entries called City News use news.east and news.west in the guide. The player maps both to news.east. The western stream shows a local programme while the guide lists the eastern bulletin. The similar names explain why the association looked plausible, not why it was correct.
Verify the candidate identity
Inspect the available guide definitions and programme records for the relevant interval. Compare regional or delayed-feed clues where supplied, and verify several known positions rather than one shared programme. Preserve the source’s exact identifiers; do not assume punctuation in the display name carries authoritative identity.
A logo can be shared across feeds and cannot establish the schedule relationship. Likewise, a channel number is a player organization choice in many contexts, not a universal XMLTV identity.
Change one mapping and verify across time
If the player provides a documented guide-association control, record the old value and select the supported candidate. Refresh only as needed, then check multiple programmes in the intended time range. If no correct schedule identity exists in the file, report missing coverage rather than forcing a nearby name.
A useful support note includes the playable entry label, old/new or candidate identifiers, mismatching examples and observation times. It should distinguish an incorrect mapping from a source schedule change or a timezone-display error. This prevents a global time offset from being used to compensate for a guide that belongs to another regional feed.
- Capture a specific schedule mismatch with time zone.
- Inspect the exact current guide identifier.
- Compare candidate records across multiple programmes.
- Make one reversible association change and verify it.