Manual EPG mapping can connect a player entry with the intended guide channel when automatic matching is insufficient. It should be a deliberate identity choice. Selecting a similarly named schedule merely because it produces listings can create a convincing but incorrect guide.

Before adding an override, establish the actual feed edition and the guide source. A broadcaster’s regional, language and time-shifted services can share branding while following different schedules. The correct association preserves that distinction.

A screenshot is not a compatibility test. — IPTV USA editorial illustration

Choose evidence for the match

Use a distinctive dated programme to compare the candidate schedules. A local bulletin or regional programme may distinguish editions more clearly than a widely shared network show. Check both the title and its timing in the viewer’s intended zone.

Automatic matching can already be correct for most entries. A manual exception should not become a reason to rewrite every channel key. Keep the intervention scoped to the verified mismatch and retain the original association for comparison.

Create a reversible exception

Do not use a time adjustment to disguise an identity mismatch. If the selected guide belongs to another edition, making one start time agree does not make the rest of the schedule accurate. Solve the relationship before considering timestamp interpretation.

  1. Record the current entry identity and automatic or existing guide key.
  2. Find the intended channel declaration and current events in the guide source.
  3. Compare a distinctive dated window with the actual feed edition.
  4. Apply the player’s supported manual-association control.
  5. Verify the result and record why the exception was needed.

Give the override a review point

A source update can later provide the correct identifier. The manual exception may then be unnecessary or can even block the corrected automatic mapping. Recheck it when either the playlist or guide source changes substantially.

A private maintenance note should name the source entry, selected guide identity, date and evidence. It need not include account passwords or complete source URLs. That note helps another person understand why a local exception exists and makes rollback possible.

After mapping, inspect more than one programme. A single shared event can match by coincidence. The intended result is an accurate schedule across the relevant window, with the playing source still correctly identified. If the source provides no current events for the intended edition, report that gap rather than selecting an unrelated schedule just to avoid an empty grid.

Useful answers

Is any schedule better than an empty guide?

No. Incorrect listings can mislead the viewer.

Should a manual mapping be documented?

Yes. Record the intended identity, evidence and reason so the exception can be reviewed.

Can a source update make an override obsolete?

Yes. Revisit local exceptions after relevant source corrections.