XMLTV troubleshooting
Two guide sources disagree because one omits the offset
Use explicit offsets when comparing sources that may apply different clock defaults.
Use explicit offsets when comparing sources that may apply different clock defaults.
Reproduce the condition
The XMLTV sample below is a small synthetic file. It carries no active media source or account data.
<tv>
<channel id="news.example"><display-name>Example News</display-name></channel>
<programme start="20250715180000" stop="20250715190000 +0000" channel="news.example"><title>Evening test</title></programme>
</tv>What the local check found
| Expected signal | Observed signal |
|---|---|
| Start needs a full valid date and numeric offset for this check | Start needs a full valid date and numeric offset for this check |
What to do next
Check how each exporter and importer treats timestamps without an offset. Add the documented offset in the source system for reliable comparison.
What to share if the problem continues
- The exact parser result and version of the importer or player.
- A minimal redacted sample with dates, IDs or segment names retained as needed.
- The output after checking the source export separately from the viewer app.