Setting Up the Cinevault Classics Tv Guide for Your IPTV System

The Cinevault Classics TV Guide is an XMLTV-format electronic program guide covering the Cinevault Classics channel lineup, which focuses on classic and heritage cinema. Getting it to populate correctly in your viewer takes a bit of hands-on adjustment because the guide source uses a slightly non-standard channel ID scheme that many EPG parsers don't recognize out of the box. I spent about six hours last month cleaning this up after switching from a larger aggregator to something lighter, and I'm going to walk through exactly how it works and what breaks along the way. First, you need the XMLTV feed URL. Cinevault publishes theirs at epg.cinevault.com/guide.xml, though they sometimes rotate endpoints during maintenance windows. If the URL stops resolving, check their community Discord before assuming the service is dead — it was down for about forty-eight hours in March 2025 due to a DNS issue, and I had no idea until someone posted the status page link there. Your IPTV application needs to accept XMLTV input. Most do. TiviMate, XCIPTV, IPTV Smarters Pro, and Televizo all support it. The basic configuration flow is straightforward: open the EPG or guide settings, select "add XMLTV source," paste the URL, and trigger a refresh. Wait. The full Cinevault guide spans roughly 1,800 program entries across about 60 hours of scheduled content. A fresh pull on a decent connection takes around 90 seconds. On a slow or congested network it can drag to four or five minutes, and some lower-end set-top boxes will time out before finishing.

Here's where things get messy. The channel IDs in Cinevault's XMLTV file don't match the standard tv_grab_* naming conventions. They use IDs like cinevault-classics-us and cinevault-horror-channel, which most default mappings won't catch. You have to either create a custom channel mapping table in your viewer or use a bridge script to rewrite the IDs before they reach the application. I wrote a quick Python parser using the xmltv library that remaps those IDs to whatever my provider uses internally, and it runs as a cron job every six hours. The script itself is under 120 lines and handles both the mapping and the timezone normalization in one pass. I ran into a specific edge case that took me a while to track down. Certain older Cinevault listings — programs from the 1980s and earlier that the channel sometimes replays — were stored with start times that lacked a timezone attribute in the XML. When my parser hit one of these, the entire EPG shifted forward by three hours for all subsequent entries. I caught it by comparing the XML output against the actual on-screen guide and noticing the mismatch started around the 2 AM block. The workaround was to add a pre-processing step that detects any start tag missing a tz attribute and appends utc by default. It's a crude fix but it holds. I haven't seen Cinevault correct the underlying data issue as of this writing. There are also a couple of things beginners miss about how this guide actually behaves in production. For one, the Cinevault feed does not update in real time. Schedule changes — cancellations, replacements, special event overrides — typically appear in the XML within 12 to 24 hours of the change being made. If you're watching for a one-time classic film airing and it's not showing up yet, don't panic. Refresh the guide manually and wait. Second, the guide includes a lot of metadata that most viewers discard — synopsis text, episode numbers, content rating codes — which means the raw XML file is heavier than a lean sports or news EPG. This isn't a problem for most modern hardware but it will noticeably slow down a refresh on older equipment.

The other counter-intuitive thing is that having a more complete guide isn't always better. The Cinevault Classics feed contains some legacy programming blocks that span multiple days without clear end markers. When loaded directly into certain viewers, these cause the guide UI to render a single massive block that you can't scroll past. The fix is to run the XML through a pre-filter that breaks entries longer than 180 minutes into 90-minute segments with a "Part 1" / "Part 2" suffix. This is standard practice in EPG management and is worth doing before feeding the data to your viewer, regardless of whether you're using Cinevault or any other source. What works well: The Cinevault Classics catalog is genuinely well-curated. The film metadata is accurate, the scheduling is consistent, and the XML structure is clean enough that a basic parser handles it fine. If you're building a dedicated classic film guide, this is one of the more reliable free sources available. What doesn't: The guide has no fallback when the primary XML host is unreachable. There's no secondary mirror, no CDN cache, and no API endpoint for on-demand queries. If the server goes down, your EPG goes dark until it comes back. I've seen this happen 2 to 3 times per quarter, usually on weekends. There's also no way to subscribe to just a subset of the Cinevault channels — you get the full XML or nothing. If you only care about one or two channels from the feed, you'll need to run it through a filter first, which adds another step to your setup.

Get the Full Details

Watch CINEVAULT: Classics - Free Live TV | Tubi
Watch CINEVAULT: Classics - Free Live TV | Tubi

If you want the feed without the headache, there are paid middleware services that ingest the Cinevault XML, normalize the IDs, handle timezone correction, and serve a cleaned version through a stable endpoint. They charge anywhere from $3 to $8 per month depending on how many viewers you're feeding. Whether that's worth it depends on how much time you want to spend maintaining your own bridge scripts. For a single-setup household it's probably fine to keep it local. For a multi-user environment with different device types, the paid route saves you the recurring maintenance. The Cinevault Classics TV Guide itself is free to access. You pull the XML, map the channels, and load it. The process usually takes about 20 to 30 minutes the first time if you're familiar with XMLTV workflows and another 5 minutes per refresh afterward. If you're new to this, budget an afternoon. The documentation is sparse but the format is standard enough that any XMLTV tutorial will get you most of the way there. Just don't skip the timezone check — that one caught me twice.