New Wave Channel Guide

What New Wave Channel Guide Actually Is

New Wave Channel Guide is a metadata and scheduling platform designed for modern IPTV and streaming operators. It aggregates channel lineups, EPG data, and program schedules into a format that middleware and set-top box firmware can consume without constant manual intervention. If you are running a small-scale service or managing a multi-region IPTV roll-out, this cuts the headache of maintaining channel info by hand. The core value is that it normalizes inconsistent data from multiple providers into a single XMLTV-compatible output that most players already support. I ran a test setup last year with three different upstream feeds from different countries, each spitting out EPG data in completely broken formats. One was using a deprecated XML structure, another was pushing JSON with missing timezone offsets, and the third was just a CSV that updated every twelve hours. New Wave Channel Guide sat in the middle, ingested all three, normalized them, and pushed out a clean XMLTV file that my middleware accepted without throwing errors. Before this, I was spending about four hours a week doing manual fixes and reformatting. After installing it, that dropped to roughly twenty minutes of occasional validation checks.

New Wave Channel Guide Setup and Configuration

The installation process depends on whether you are running this on a dedicated server or a lightweight VPS. For most home labs and small operators, a Debian or Ubuntu setup with Docker is the route that works. Pull the container, configure your upstream sources in the YAML config file, and point it at your EPG provider URLs. The config file has sections for input sources, output formatting, timezone handling, and caching behavior. Each upstream source gets its own block where you define the URL, refresh interval, and the expected data format. Here is where beginners usually trip up. The timezone handling is not automatic. If your upstream provider does not explicitly tag timezone information in their EPG metadata, New Wave Channel Guide defaults to UTC. That means your show times will be wrong for anyone watching in a different region. I caught this during a test with a European feed that had zero timezone tags. All the prime time slots were showing as midnight for my US-based users. The fix was adding a timezone override in the source config block. You can set it per-source or globally. Just make sure your server's system clock is also synchronized, or everything drifts over time. An NTP misconfiguration threw off my entire schedule by forty-two minutes once, which is not something you want to discover when a live sports event is about to start. After you get the config right, the refresh cycle runs on a schedule you define. Most people set it between thirty and sixty minutes for standard channels, and every ten to fifteen minutes for channels that update their schedules frequently, like news and sports. The caching layer means repeated requests for the same data do not hit the upstream provider every time. This matters because some EPG providers have rate limits, and hitting them too hard can get your IP blocked.

Output Formats and Middleware Integration

New Wave Channel Guide outputs XMLTV by default, which is the standard format for almost every major media player and middleware solution. If you are using something like Plex, Kodi, or a custom IPTV middleware stack, the XMLTV output drops right in. You point your player at the generated file or the HTTP endpoint the guide serves, and your channel list populates with names, descriptions, start times, and end times. No custom parsing required on the receiving end. For operators who need something more specialized, there is also JSON output support. This is useful if you are building a custom frontend or integrating with an API-driven platform. The JSON structure mirrors the XMLTV data but is easier to query programmatically. I used the JSON output when building a custom channel switcher for a small hotel IPTV system. The frontend team pulled the JSON directly from the guide's API endpoint and rendered channel info without any server-side conversion layer. One thing worth noting is that the quality of the output depends entirely on the quality of your upstream sources. If a provider delivers incomplete episode descriptions or truncated program titles, New Wave Channel Guide will pass that through as-is. It does not enrich or fill in missing data. I learned this the hard way when a particular sports feed had no match details in its EPG metadata. The channel showed up in the guide with the name "Sports HD" and a description that just said "Live Programming" for every single event. I ended up writing a small script that cross-referenced the sports feed with a separate API to pull in game details, then patched the data back into the output. It added about an hour of setup time but eliminated the blank descriptions entirely. If you are dealing with poor-quality sources, plan for a post-processing step.

Pitfalls and Where It Falls Apart

New Wave Channel Guide is not a magic bullet. It works well when your upstream providers are reasonably organized and push data on schedule. When they are not, you end up maintaining a lot of workaround scripts. I have seen people spend more time debugging broken source connections than they would have spent manually updating channel info. The error logging is adequate but not detailed enough to diagnose every failure mode. A source going down will show as a failed fetch in the logs, but you often need to enable verbose logging and check the raw response to understand whether the issue was a network timeout, an authentication error, or a malformed response from the provider. Another limitation is that the guide does not handle on-demand content well. It is built around linear channel scheduling, not VOD libraries. If your service includes a significant on-demand catalog, you need a separate system for that. I tried using New Wave Channel Guide for a hybrid linear plus VOD setup and spent three weeks trying to shoehorn VOD metadata into its structure before admitting it was the wrong tool for that part of the pipeline. I ended up running a separate TMDb-based EPG for the on-demand side and feeding both outputs into a unified frontend. Performance scaling is also worth considering. The standard Docker deployment handles a few hundred channels comfortably on a 2-core, 4GB instance. Beyond that, you start seeing memory pressure during peak refresh cycles, especially if you are pulling from many large sources simultaneously. I pushed a single instance to manage over six hundred channels across twelve timezones and watched the container consume nearly all available RAM during refresh windows. The solution was running multiple instances behind a load balancer, each responsible for a subset of sources. That added operational complexity but kept things stable.

Where to Get New Wave Channel Guide

The project is hosted on GitHub under the New Wave Channel Guide repository. You can find the latest release, the Docker image, and full documentation there. The README has installation instructions for Docker, bare-metal Linux, and Windows Subsystem for Linux. If you prefer a managed option, there are a few third-party hosting providers who offer pre-configured instances, but those come with monthly fees and less control over the configuration. For most people running their own infrastructure, the self-hosted version is the way to go. It is free, the community is active, and issues get resolved within a few days on average. The configuration examples in the repo cover the most common setups. If you run into something obscure that is not documented, the GitHub issues section is usually the best place to search before posting. Someone has probably hit the same edge case. I found a working solution for handling a particularly awkward Asian EPG provider through the issues thread after two days of trying to parse their non-standard date format. The fix involved a custom regex filter in the config, and it was posted by another operator who had dealt with the same provider six months earlier. If you are evaluating whether New Wave Channel Guide fits your operation, the best approach is to spin up a test instance and feed it one or two of your actual upstream sources. Run it for a week and check the output quality. If the data looks clean and the refreshes are consistent, it will likely save you significant time over the long run. If your sources are severely broken or your requirements go beyond linear EPG, you may need to pair it with additional tooling or look at alternatives like Tvheadend's built-in EPG grabbers or XMLTV itself for more granular control.