An XMLTV guide relates programme records to channel declarations through identifiers. The channel’s readable display name helps people recognize it; the identifier connects the records. A guide can therefore contain both the channel and programmes yet still show an empty grid if the relationships do not match the player’s entry.
Inspect the relationship rather than renaming everything to the visible channel name. That approach preserves regional and language editions and avoids creating a superficial match to the wrong schedule.
Trace three separate values
A fictional channel declaration can define an identifier such as harbor.east. Programme records then name that identifier in their channel attribute. The player’s playlist or manual association must connect the intended source entry to the same guide identity through its documented matching process.
The display name can differ from the key without being wrong. A readable name may contain spaces, branding or translated text that the internal identifier does not. Treat the key as a relationship value, not a slogan that needs stylistic improvement.
Check the join in order
A mismatch found at one stage should not lead to changes at every stage. If the guide’s own records disagree, that source needs correction. If the guide is internally consistent but the player points elsewhere, the local mapping is the relevant layer.
- Identify the precise feed edition the viewer intends to use.
- Find its channel declaration in the actual guide source.
- Confirm that the relevant dated programme records reference that declaration’s identifier.
- Compare the player’s explicit key or manual mapping with that value.
- Verify a known programme window after the supported refresh operation.
Do not confuse a key with a URL
A channel identifier can resemble a domain name without being an address to open. Its role in the guide is to identify the channel record. Pasting it into a browser or adding a scheme does not validate the relationship and can lead to an unrelated destination.
Case and character handling depend on the importer’s documented rules. Preserve exact values during the initial check. A player with an optional case-insensitive matching setting is evidence about that application, not a reason to assume every importer ignores case.
For a support example, provide the harmless identifier values and dated programme reference needed to show the mismatch. Exclude private source endpoints. Report whether the guide is internally inconsistent, the local association differs or the required events are absent. That distinction leads to a targeted correction and avoids a global reset that would disturb channels already displaying correctly.
Useful answers
Must an XMLTV channel key be the same as its visible display name?
No. They serve different roles.
Does a domain-like channel ID need to open as a website?
No. It can function simply as an identifier in the guide.
Can an importer’s case-handling setting matter?
Yes. Check that application’s documented rules rather than assuming universal behaviour.