A supported playlist can include a tvg-name attribute as well as the visible entry label. These values may look the same, but their purposes need not be identical. The application’s matching rules determine whether an optional name helps associate the entry with guide data.
Do not treat every name-like field as an interchangeable channel identifier. A display label can be chosen for viewers, while a matching label follows the guide publisher’s naming convention. A stable explicit guide key can carry a more precise relationship than a familiar phrase.
Compare fields before editing
Imagine a channel displayed as “Harbor News East HD” while an optional guide name reads “Harbor News East.” The difference might be deliberate, not evidence of a typo. A resolution suffix in the browsing label can help users distinguish entries even when the guide describes one programme schedule.
The reverse is also possible: similarly named regional editions can require separate schedules. Removing an edition suffix because it seems untidy can encourage the wrong match. Establish the actual feed and guide source before simplifying metadata.
Work through a name mismatch
If the application does not use tvg-name in the way the file author expects, copying names between fields may not help. A manual association or a correctly supplied guide identifier can be the supported route. Avoid announcing a universal rule based on one player’s behaviour.
- Record the displayed label, optional matching name and explicit guide key separately.
- Check the receiving player’s documented matching priority.
- Compare the intended guide channel, including region and edition.
- Change only the field that is actually causing the mismatch.
- Confirm a dated programme rather than accepting any newly populated listing.
Keep language and identity separate
A translated display label can improve household navigation while the guide publisher retains an original-language channel name. That difference does not automatically require replacing one with the other. Preserve useful alternate naming context where the application supports it.
When switching guide providers, old matching names may stop working even though playback entries remain valid. Treat that as a metadata migration. Compare a small representative sample, note the new identifier scheme, and make deliberate corrections instead of renaming the whole catalogue in one pass.
A useful support example contains the three relevant field values with private access information removed. State whether the problem is the visible name, the selected guide or a missing event window. This avoids turning a guide-mapping question into an unnecessary account reset, and it gives the maintainer a clear correction to evaluate.
Useful answers
Is tvg-name always the text shown in the channel list?
No. The visible label and optional matching attributes can be separate.
Should translated display labels replace guide keys?
No. Preserve the relationship required by the actual guide and importer.
Can changing guide sources require new matching metadata?
Yes. Compare the new source’s naming and identifier scheme.