IPTVGuides.net

Programme guides

Read, test and repair an extended M3U playlist

Follow the channel label, metadata and next-line address. Use a small fictional fixture to learn the structure, then diagnose your own authorised playlist with a working control.

5,054 words · About 23 min

Archived sample player screen showing the TV programme grid
Archived UI example. Menus may differ in current versions.Image source

Work from a small copy you can understand

An extended M3U playlist is plain text. For a typical IPTV player's channel list, the header introduces the file, each information line describes a channel entry, and the next address supplies something the player can request. The file gives the client choices. The video still comes from the service or storage you are allowed to use. You can work through the playlist's shape without sending any viewing credentials to a website.

Start by opening the fictional three-channel list as text. All three addresses use the reserved example.invalid domain. Use the text to see how entries fit together. For a real playback test choose a separate, authorised source that your player and provider document. The source and addresses in the fixture are for reading and parsing exercises.

The first line is #EXTM3U. Below it there are three pairs of entry lines and addresses. Read the first pair all the way through before moving on. The channel has an identifier, a group label, a displayed name and a location on the following line. Start by matching the name to the address line that belongs with it. Then read the metadata that may be used by an app to add a guide or organise a list.

An actual provider may send an approved URL rather than a saved file. The text available at that URL could change when the provider refreshes it. Use the provider's documented import method and preserve a current reference privately. When you want a static review exercise, use a redacted example or copy only the information permitted by your agreement. Treat signatures and access parameters as credentials from the moment you receive them.

A first reading exercise has a clear endpoint. Identify how many labelled entries you see, recognise the two editions of Harbour News and find the unusual name with a comma. Then compare them with the expected titles. The third entry's label is “Atelier, Arts.” It is meant to show why you should preserve the exact entry syntax and inspect what your particular player displays. Splitting every comma in a row into fields would break that label in a simple parser.

Keep the original supplied copy until you can reproduce and undo every change to your working one. If a test fails, you want to be able to open the older file under a neutral name and check whether it ever worked. Set up a private test folder for credentials and a separate set of fictional lines for public discussion. That makes it much easier to ask for help without forwarding the live list.

Separate the record label, the channel ID and the source address

Open the Harbour News East row. The friendly name appears after the metadata, and a different label is inside the tvg-id attribute. The next line holds the URL. These three details perform different jobs and you can test each separately. Two channels may have very similar names while supplying different local editions at different times.

PartValue in the fictional exampleWhat you can verify
Identifierharbour.news.eastA programme-guide mapping can use this exact value where the player supports it.
Group labelLocalThe entry may appear under Local if the player uses the group-title attribute.
Display labelHarbour News EastThis name should describe the edition the viewer is choosing.
Addressexample.invalid with the harbour-news-east pathThe line belongs to the East entry. The reserved domain is used only for this exercise.

Read the next entry using the same steps. The West edition has a different identifier and a different address. Its label contains the word West. Distinguishing all three properties can prevent a common mistake. If the East and West entries are swapped in the guide, duplicating the group-text label will not restore the underlying relationship. Check which metadata and address still belong to each record first.

Try a controlled edit of a fictional file. Change only the user-facing label on one line. Leave the identifier and URL untouched and save to a new local copy. Import or inspect that copy through a supported tool and look for the new label. If the guide can use the same identifier, the two versions can still refer to the same programme ID. This observation gives you one test for a naming change that avoids touching playback data.

Another edit changes just the identifier on one neutral example. Leave the visible label and following address as they were. Compare the changed ID with the guide fixture. Now the front label didn't move, but the precise string the guide may use no longer agrees. A viewer could see the same channel name and still lose its next programme. Focus a support question on the changed identifier and result.

The conventional attributes aren't guaranteed across clients. A player might accept group-title, show only the final label or use a different mapping rule when it sees no tvg-id. Find the relevant section in the publisher's documentation and keep a note of the version you tested. A result from one desktop client is partial evidence about file structure. It becomes clearer when you repeat the small example with the TV app you plan to support.

Keep the identity source in your notes. Renaming an item to match a broadcaster's expected label can help you find it, but the statement that the approved stream really carries that edition belongs with the issuer and the lawful broadcaster. Use the official schedule for a particular market or event. The visual reference library helps you recognise marks and their source context. It does not determine what a provider's current list carries.

Identify a channel list and an HLS manifest by their role

Both can arrive with a familiar playlist extension. A TV channel list usually offers several different stations or programmes as entries. An HLS manifest describes delivery of a stream and uses tags defined by the relevant specification. It may point to available variants or to media segments for one viewing choice. Read how the URL was introduced by the provider and look for the file's purpose rather than relying only on the ending.

One kind of HLS playlist describes different representations of the same stream. They can vary in supported characteristics, such as rate or resolution. Another kind describes the media available for playback segments. Adding each representation to a TV channel list as though it were a separate station creates confusing duplicates. Keep the actual authorised viewing URL in the form the supported player expects. Allow the player and service to handle valid stream selection according to their documented behavior.

When you inspect an example, note whether each entry has a channel name and group or whether you are reading stream delivery tags. Seeing #EXTM3U at the top doesn't identify the rest of the file. The right question is what the app asks for at that stage. Its list-management screen expects a catalogue of choices. Its HLS playback path may expect to follow the stream recipe it receives as the result of choosing an entry.

A provider can put an HLS address on the source line of a normal M3U channel list. The relationship is straightforward if you read from outside to inside. The user picks a channel. The player requests the channel's address. The service may respond with a manifest. The supported player then follows that manifest to obtain the video. A successful outer list import can coexist with a failed inner stream request.

Look at one redacted example if the list appears to contain only a single unexpected entry. Ask whether the service supplied a broadcaster's viewing address, a documented list URL or a response from another part of a sign-in flow. Ask the issuer for the exact supported input. A renamed file and a manually added filename extension do not change what the receiving application can parse.

You can describe this distinction using a sentence without exposing any URL. “The provider gave a channel list. My client parsed the stations. A single station fails when its playback address is fetched.” Or, “The supplied link gives an HLS manifest for one programme. The app's channel-list import rejects it.” Those descriptions help the provider decide which interface or input type you need. The channel-list and HLS guide covers the formats as a shorter reference.

Run a filename, line and encoding check

Use a plain text editor on a private copy. Check the actual file extension and whether the editor saved additional formatting or an extra extension. If a document editor quietly saves a proprietary format, the file may show an M3U-looking filename while holding different bytes. Reopen it as text to confirm. Work with an unedited backup in case the first editor changes quoting or line endings.

Start with UTF-8 when your documented player supports it. Look at the import result for labels with accent marks and non-English characters. If names turn into replacement symbols or the first line is misread, compare the app's encoding guidance with the exact saved file. Newlines and a byte-order mark can be handled differently across tools. Use the smallest safe fixture that reproduces the mismatch.

Keep each metadata line and its following address together. A missing or wrapped URL can shift the next information line into the wrong position for a strict parser. Long URLs may soft-wrap visually in an editor. The underlying line still needs to remain the correct record. Turn on line numbering if available and check whether the apparent wrap is just display formatting or a real break.

Check the first and last pairs. Copying part of a list can accidentally stop after an information line without its address. The player may silently skip the incomplete row. In a generated sample, compare before and after a single deletion. Remove the final fictional address from a copy, then observe how your supported test parser responds. Restore it and test again. This is more specific than testing a whole large list and guessing which entry caused an import failure.

Preserve ordinary ASCII quotes for the metadata syntax in the fixture. Text processors can substitute curly quotation marks that look right at a glance. The resulting list may still contain the display text while some attributes disappear. If only the groups or guide IDs are missing, inspect the affected attribute before rewriting every entry. Check which app version interpreted the same file successfully.

Give a dated working sample a name you can recognise, such as a fixture name with a change number. Save only the safe example in a shared report. If your real playlist contains a signed access URL, do not copy it into app bug trackers or cloud paste services. Describe the encoding, line count and exact neutral label for the affected record. The publisher can ask for additional evidence through its approved channel if it needs it.

Verify group names and duplicates without throwing away an edition

An entry may carry a group-title the client uses to build a channel category. A different app may show a flat list first or organise entries according to an imported favourite or account setting. Read the published feature description and test two entries that belong to different groups. If they appear in one view, make sure the filter or guide display is actually the one you intended to use.

A duplicated display name does not necessarily identify a duplicate stream. It can be a local edition, language, audio variant or different quality path. Compare the documented identity and whether the source says both channels are intentional before removing anything. A useful local note can distinguish two similar names using their supported public region labels and the exact identifier in the working file.

The fixture's Harbour News East and Harbour News West demonstrate a deliberate pair. Give both the same visible name in a disposable copy and test what the player shows. Now they can appear identical in one list while their IDs remain distinct in the text. Restore their displayed names, then confirm whether the group view and guide still show two separate programmes. You have isolated a naming issue without changing the guide.

Try a second comparison with locales. A public station can be branded similarly in two markets and broadcast at a different local time. Changing the visible language description in the playlist does not translate an audio track. Confirm the actual track and edition using the documented playback source. If only a category title looks wrong, trace whether it came from the file or from the player's own group settings.

Some users want to shorten a list for the living room. If the app has a documented favourite grouping, use it to keep a working provider list intact. Where permitted by the source agreement, an edited local file can be useful, provided you maintain what will happen when the publisher updates addresses or schedules. Record who is responsible for future changes. A copied file can go stale while the original remote list continues to update.

When comparing two files, start with a small table of entries. Give each row an expected source, ID, visible name and group and mark what the app displays. If the app shows two unexpectedly identical rows, determine whether both exist in the text, whether the app composed them from two configured inputs or whether an older import is still active. Diagnose the cause before removing an entire configuration.

Match the schedule through the tiny XMLTV example

Download the companion fictional XMLTV schedule and open it as text. Each channel entry has an id attribute. Each programme has a channel attribute that refers to one of those channel IDs. Both files agree on Harbour News East and West. A source date and a UTC offset appear in the programme times. The date in this exercise helps you inspect mappings. Its content and programme names are fictional.

Put the two fixture texts into the local checker on the EPG repair guide, following the labels on its inputs. It compares the supplied identifiers in the browser. Read the result for the three exact matches. The exercise shows structural mapping and the presence of records. Your player still determines whether its own guide loads, applies the intended offset and displays the expected time window.

Change just the West ID in the disposable M3U copy to harbour.news.west-old. Run the comparison again. The guide still holds a channel and programme for harbour.news.west, while the changed list points at another value. A record count and display name can both look plausible. The mismatch appears when you evaluate the specific ID. Restore the original ID and compare the resulting table again.

Try removing one programme row from a disposable XMLTV copy while leaving the channel entry present. The ID can still match, but there will be no programme row for that ID in your small sample. That is a different result from a missing channel ID. In ordinary viewing, a useful check uses the date and timezone you care about plus the official station schedule. Your XMLTV source may contain data that exists but lies outside your player's requested guide period.

Check both sources at the smallest useful scope. A working stream can still have a mismatched ID. An exact ID pair can still have no usable programmes or show a shifted time. If one regional feed stays blank, inspect its exact identifiers, programme dates and the app's mapping. If everything shifts by the same number of hours, check the reported times and offsets before applying a blanket correction. The guide time offset reference gives a separate troubleshooting sequence.

Keep configuration changes reversible. Some players derive IDs from station text or allow preferred manual assignment. Follow their documented process. Write the old and new safe identifier in your local test notes before changing an authorised list. Confirm one working and one previously broken example after a refresh. If the device still chooses an older cached schedule, record the field the app uses to show refresh status and ask the publisher which supported action clears it.

Reproduce a remote import failure without exposing a signed URL

Start from the documented account owner path, where a provider can tell you whether a list remains active. Look for the app's plain message and the point at which it appears. A request refused before the app shows any entries is different from a channel that refuses playback after an otherwise successful import. A generic message might combine multiple underlying results. Describe which surface you actually saw.

If a remote URL was involved, keep its full text in a private note. A signed query string or a path segment can confer access even without the word “password.” In a public report, use the format “HTTPS playlist URL from service account, issued in the current term” and the app's redacted message. For the issuer, use its own authenticated help route and send private evidence only as its support policy requires.

A valid address can still lead to a document that the player can't import, such as a regular help page or an account prompt. Check the expected content type or published download workflow with the authorised issuer. An HTML landing page, file list and media manifest are different things as supplied to a player. A browser showing something readable is a useful first observation and does not determine whether the player had access to the expected bytes.

If the player reports a status for one address, note the address role, time zone, app version and exact safe words. HTTP status descriptions give broad meaning. A 403 may represent a refused request. A 404 may apply to a particular current path, list or asset. Ask the issuer to check the authorised record. Don't guess replacement paths, rotate credentials through unrelated servers or share a session link as a shortcut to help.

Test a control file locally if the app supports one. Import the fictional text only to inspect parse behaviour and names. Use a distinct approved source when you need to prove playback. If the app parses a local fixture and rejects only a service URL, you have evidence about two separate paths. It might help the publisher see whether you need a browser-export route, a different input screen or support for a current network response.

Make one observation about the difference between a hosted list and an export. A remote list fetched on demand can follow approved updates. A downloaded copy typically preserves exactly what was present when you saved it. A working local sample and a later refresh can therefore show different dates or lineups. Record the input type and when you obtained the data so support can compare the same edition rather than fixing an old copy.

Plan a refresh you can verify in the guide and on the screen

Set a deliberate order. Open the existing channel list and verify one working reference before you refresh. Record the date, expected channel name and the programme shown. Keep an authorised older copy or supported recovery option where the provider permits it. Then use the app's documented command to refresh the relevant data.

If the provider changed lineup IDs, refresh the channel list first if that's the app's documented order. Check whether the new ID is present before running the guide update. The guide refresh could otherwise attach programme data to entries that the app has not loaded yet. Some players automatically combine the steps or allow manual mappings. Read how the specific app reports completion and confirm both visible results.

Choose a second channel whose schedule should remain stable and compare it after the update. This control can help you see whether one station or the entire data set changed. Ask whether the expected result changed with the new channel lineup, the source's schedule or a local timezone adjustment. Write only the observed result before you decide which source to ask for help.

A screenshot can show two lines from a small fixture that remain safe to share. Crop to the label, local time and redacted observation. Close account panels, usernames, network identifiers and full private URLs before recording anything. An exact neutral text record is often easier to compare than a photo that shows several screens at once.

Add a source note if you amended your own labels. When the remote source changes, your edited local file may be overtaken and player favourites can take a different form. Decide which part of the setup you can rebuild using the authorised publisher's route. Record whether you are keeping its standard list, an allowed edited local copy or only a set of favourites inside the app.

Finish by testing from the sofa. Open the expected EPG row, read the programme at the right local time, select the entry and confirm the intended video plays through the authorised arrangement. This is the simplest end-to-end check. If one step still fails, your dated notes let someone else test that step without learning private credentials or changing a working playback path.

Ask for help with the smallest test that still fails

Name the app and platform, list type and exact stage. “The third metadata entry appears without a group” and “the list never imports from a permitted hosted address” are different questions. Include an example with neutral titles and invented endpoints. If the app offers an import log, extract only the portion that explains the message after removing live URLs, tokens and private names.

Use an explicit comparison. “Both fiction entries appear in my desktop player. The TV app shows one and skips the next when the preceding URL line is missing.” That tells the reader which rules you are testing. If you cannot reproduce it on a neutral file, describe the visible conditions and contact the provider through its supported private path for specifics. A public thread can still explain the method without revealing the file.

For guide trouble, give one fictionalised pair from your comparison with the source's real local time represented safely. Be clear which details are replaced or simulated. The direct sample in this guide lets people reproduce the general format without the original source. It also gives you a way to show a matching ID with missing programme rows and ask which processing rule the app applies.

If someone suggests deleting the app or the full profile, ask whether a small test can identify the failure first. Preserve the documented recovery route and explain which controls still work. A polished support answer should propose one observable change and let you return to the known working arrangement. A long list of random options makes it harder to know which setting mattered.

Use the EPG and playlists discussion area for identifiers, dates, listings and import problems. Use the app source guide when the question is where the TV app comes from. A playlist remains meaningful only alongside the app that reads it, the authorisation that permits playback and the schedule data you intend to display.

Inspect optional metadata before you change a whole library

The extended channel-list convention allows descriptive metadata that clients interpret in their own ways. A tvg-id is handy if both the app and XMLTV source use that exact value. A group-title can decide which category a viewer sees. Some players support a separate logo reference or a human-readable channel name attribute. Choose the ones your documented client reads and observe how the list behaves when one is absent.

You can build a small local experiment from the fictional three-entry file. Duplicate the file under an experiment name. Remove the group-title from the Atelier entry, keeping its address and label. Check whether the player assigns it to an ordinary group, keeps it in a flat list or presents the original group from an existing import. Each outcome can inform a different next step. A result that remains unchanged might indicate the client is still showing an older import or a preferred group saved elsewhere.

To test the label, keep the attribute values as written and change only the ordinary text after the first separator comma. Make it something easy to see from across the room. Try an accented spelling in the temporary example when encoding is part of the question. Record whether the visible title follows the last field or a different documented metadata attribute. If there are several possible labels, use the one the publisher actually reads rather than duplicating all names in the file.

The next check looks for a metadata boundary. In the ordinary fixture, “Atelier, Arts” includes a comma inside the intended visible name. A plain text tool that blindly divides on commas might show “Atelier” as a field and “Arts” as an extra unexpected field. An appropriate parser preserves the visible title according to the file's supported syntax. If you are preparing hand-edited entries, compare the output with one small known sample before changing dozens.

Use a logo only when you understand what it represents and where the player obtains it. A decorative mark can remain visible even when the actual feed changes. A remote image can fail independently of both the stream and the schedule. If a name, group and video work but the mark is blank, check the publisher's image support and current source rather than editing IDs or accounts. Neutral test patterns can help an app developer reproduce an image issue without a live channel reference.

Save your findings in a brief input policy. It could say the household player reads the entry label and known guide ID, puts missing groups into its default category, and relies on a separately approved logo setting. The policy comes from the exact software release you tested. When you change devices, run the same small file again. That is a useful way to keep a household library legible across different interfaces without asking the provider to rename everything.

Find out which update belongs to the publisher and which belongs to you

A hosted list and a manually edited one can diverge quickly. The provider may change a station's address, organise groups differently or adjust the guide while you are selecting favourites on the TV. Decide how your client should receive the official changes before you make a working copy the only install. Map the publisher-supported refresh to one private record. The record does not need to hold a credential in a place other viewers can read.

Work through a realistic case. A new approved public schedule still uses the same East station and identifier, but the source's viewing address has changed. People who refresh a supported remote list may receive the new value. Someone who manually edited an old exported file still has the older candidate address. Avoid guessing the new value or testing another person's signed link. Return to the current authorised publication and update the record through the documented method.

A naming-only change has a different scope. Suppose you changed an entry to read “Local news” and the issuer later amends its category. Read where your app stored the favourites and whether a refresh keeps or replaces a preferred title. If your personal notes matter, preserve them through the player's documented export. Keep the stable publisher identity and app configuration separate so you can recreate the minimum useful setup if an import is replaced.

Check unresolved changes against a calendar. If an app imports only when first launched, entering a Sunday list and viewing on Tuesday may produce outdated programme labels. Some documented clients allow background refresh or manual refresh. Test what the version you use actually does while the TV is open and after the device returns from its normal standby. A visible date in the grid and a recorded refresh time can explain which set you are viewing.

Turn that into a small handover. List the approved remote source, the app and model, the rule for updating it, and the one station to check afterward. Store account details privately. If someone else maintains the room, give them the visible action they can repeat when a guide is outdated. Include who to contact if the approved playlist only works on one documented device after a provider change.

Compare a single known entry across two supported players

The cleanest comparison begins with the same file and an observation you can repeat. Open its neutral copy in two supported clients, perhaps a desktop tool for text structure and the TV app for household use. Start by checking labels and groups. Add a known lawful playback control separately where the source terms permit it. A desktop parser and a television decoding pipeline can succeed at different parts of the job.

Write what each client reports at the first visible milestone. “The desktop app lists all three fictional channels; the TV app lists two and skips the comma-containing label.” Check which client and version produced each result. Then change only the neutral label syntax and repeat. This is more useful to a publisher than blaming the player for a large file it has never seen. It also creates a fixture you can share without risk.

Test the agreement side separately when comparing real sources. Confirm whether your account permits another device or session. Close the first client before opening the second if the authorised access requires that. Make sure both clients request the same current station and use their supported input method. A difference that follows simultaneous access may say more about the agreement than either parser.

Track captions and guide mapping as separate parts of the result. One TV client may preserve the correct station ID and still hide a caption track. Another may report the title but leave the local schedule blank. If your two tests differ on the supported metadata, capture a precise small example. Read the publisher's feature descriptions for the platform rather than general descriptions for every version.

Choose a final client after it passes the ordinary tasks. Ask a viewer to find the local station, start the authorised programme, confirm schedule time and return to the list. If a repaired file works only in a test harness, you have established one useful fact about its structure. Finish the real-device test before giving the house a new regular setup. Record which dated copy you used, where the exact published app came from and how to return to the previous working profile.

Sources and scope

Publisher documentation and editorial analysis. Hardware and subscriptions were not purchased or tested for these guides.