M3U Guide Data Missing

Channels DVR Server
#1

I'm supplying live TV from Dispatcharr into Channels DVR using an M3U link. I noticed yesterday that my guide information is no longer present. I downloaded the guide data directly using the M3U link, and all of the information is present. I'm also supplying live TV from the same Dispatcharr instance into Emby, and the guide data is present there.

I believe this started after updating to a more recent Channels DVR Server beta version. Is anyone else seeing the same issue, or does anyone know how to resolve it?

Version: 2026.08.06.2335
CDVR Docker

CDVR Guide

image
image1016×639 92.9 KB

Emby Guide

image
image1040×426 50.4 KB

CDVR Beta App

image
image1020×383 106 KB

#2

I use other sources with M3U guide data and am not having issues. Try setting your guide data update to every 1 hour and also upgrade to the latest beta.

Good luck

#3

Version 2026.08.06.2335 is the latest beta at this time. I performed a manual update before making this post, so adjusting the update interval won't resolve the issue.

I've also tried the following troubleshooting steps:

  • Live TV & DVR → Guide Data → Maintenance → Re-Downloaded Entire Guide
  • Live TV & DVR → Guide Data → Maintenance → Delete and Recreate Database

Neither of those resolved the problem.

Live TV & DVR → Guide Data → Maintenance → Delete and Recreate Database Logs

2026/08/07 08:21:39.862018 [DVR] Fetched guide data for XMLTV-Dispatcharr in 787ms
2026/08/07 08:21:41.853410 [DVR] Indexed 7668 airings into XMLTV-Dispatcharr (426 channels over 72h0m0s) + 0 skipped [2s index]
2026/08/07 08:21:47.354031 [DVR] Indexed 98 channels (32928 airings + 0 replaced) with placeholders [5s index]
2026/08/07 08:21:47.354127 [IDX] Pruned 0 expired groups from XMLTV-Dispatcharr in 49µs.
2026/08/07 08:21:47.367972 [IDX] Pruned 784 expired airings from XMLTV-Dispatcharr in 11ms.

Live TV & DVR → Guide Data → Maintenance → Re-Downloaded Entire Guide Logs

2026/08/07 08:23:23.340747 [DVR] Fetched guide data for XMLTV-Dispatcharr in 79ms
2026/08/07 08:23:25.270794 [DVR] Indexed 7668 airings into XMLTV-Dispatcharr (426 channels over 72h0m0s) + 0 skipped [2s index]
2026/08/07 08:23:25.335370 [DVR]   pruned 7056 replaced airings in 65ms.
2026/08/07 08:23:31.278944 [DVR] Indexed 98 channels (32928 airings + 0 replaced) with placeholders [6s index]
2026/08/07 08:23:31.279044 [IDX] Pruned 0 expired groups from XMLTV-Dispatcharr in 50µs.
2026/08/07 08:23:31.296628 [IDX] Pruned 784 expired airings from XMLTV-Dispatcharr in 14ms.

Logs have been submitted as d4f2f82d-e02f-44c2-9791-3e73ecba6374.

#4

You could try deleting the source and recreating it.

#5

Good idea. I just tried that but it didn't make a difference. :face_with_diagonal_mouth:

1 Like
#6

I'm out of ideas. You submitted diagnostics. If you did not submit a support request you should to get the developers attention.

#7

Support request means sending them an email, right?

#8

yes, to [email protected]

1 Like
#9

Thanks for the suggestions. I sent an email to them.

#10

For what it's worth, I setup a new Channels DVR docker container and it has the same issue.

#11

What's with your thumbs down @billmich? The issue is fixed after reaching out to support. Are you having the same problem?

#12

you post said:
For what it's worth, I setup a new Channels DVR docker container and it has the same issue.

i was reacting that your issue wasnt solved and thats bad - maybe i should have done unhappy face

#13
#14
#15

The issue was on my end. Below is what the developer found. After a few quick changes on my end, all was back to normal.

Supports Reply:

We took a look at your XMLTV file, and the issue is that its channel ids don't match the tvg-ids in your M3U.

Your M3U identifies channels by their guide data id, e.g. tvg-id="10614" for ABC KOCO. But your XMLTV file declares that channel as <channel id="1"> (the channel number), and its guide entries as <programme channel="1">. Channels DVR maps guide data by matching the M3U tvg-id against the XMLTV channel id, so none of those channels match and they fall back to placeholder guide entries.

To make the mapping work, the two files need to agree — either:

  • the XMLTV <channel id> should be the same value as the M3U's tvg-id (e.g. 10614), or
  • the M3U's tvg-id should be the channel number to match the XMLTV (it looks like your M3U URL uses a custom Dispatcharr output profile, which may be why they differ)

Your 24/7 channels still work because their tvg-id happens to be the channel number, which matches the XMLTV. The rest of the guide data is all present in your XMLTV — it's just keyed by ids Channels can't associate with your M3U channels.

1 Like