Channel Mapping empty

[slwtx1983]

I have had NPVR working with MC2XML.exe for a while now. I use the newer paid version that pulls the correct EPG data. Anyway, I noticed that I was missing a couple of recent recordings, and noticed my Guide was completely gone. Now, for some reason, when I go into NPVR to map channels, the Devicess show up just fine. The Scan reveals the proper channels, but when I go to map my XMLTV EPG, the Mappings drop down is completely blank. Just empty with no options. I reinstalled the entire operating system and reinstalled it all fresh after updating Windows 7 and I have the exact same issue.

I can watch live TV, and I have every channel that I need. My MC2XML hasn't change at all, except that the EPG data is up to date. My concern is not really my actual guide data though, more so that the channel mappings aren't working for some reason.

NPVR 3.4.8
EPG: XML MC2XML.exe
OS: Windows 7

[sub]

It's most likely a case of the channel id's having changed in the xmltv files from the old mc2xml.com. If you go into the settings of a single channel (not Bulk Map), and browse and select your xmltv file, does the channel names show up? If not, zip and attach your xml file and I'll take a look.

[slwtx1983]

Yeah, unfortunately in bulk and single, the mappings are not there. I also cannot attach the full channel data bacause it is 33MB when zipped. I posted a small piece below from the channel mappings part of the XML file that I think you'll need.

Thank you very much for the quick response.

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE tv SYSTEM "xmltv.dtd">

<tv source-info-name="Rovi" generator-info-name="mc2xml" generator-info-url="mailto:mc2xml@gmail.com">
<channel id="I2.28455553.microsoft.com">
<display-name>2 DAYSTAR</display-name>
<display-name>2</display-name>
<display-name>DAYSTAR</display-name>
<display-name>KDTN Daystar Television</display-name>
<display-name>DSTAR</display-name>
</channel>
<channel id="I3.260170707.microsoft.com">
<display-name>3 KAZDDT3</display-name>
<display-name>3</display-name>
<display-name>KAZDDT3</display-name>
<display-name>KAZD Saigon TV</display-name>
<display-name>IND</display-name>
</channel>
<programme start="20150824190000 -0500" stop="20150824193000 -0500" channel="I2.28455553.microsoft.com">
<title lang="en">Pastor Rod Parsley</title>
<desc lang="en">Pastor Rod Parsley discusses matters of faith.</desc>
<category lang="en">Other</category>
<category lang="en">religion</category>
<episode-num system="ms_progid">1.309351612250000</episode-num>
<previously-shown />
</programme>
<programme start="20150824193000 -0500" stop="20150824200000 -0500" channel="I2.28455553.microsoft.com">
<title lang="en">Joni Table Talk</title>
<desc lang="en">A talk show featuring lifestyle segments, controversial topics and news.</desc>
<category lang="en">Other</category>
<category lang="en">local</category>
<episode-num system="ms_progid">1.309354053250030</episode-num>
<previously-shown />
</programme>
</tv>

[sub]

You'll need to a put the file somewhere I can download it. ie, drop box or onedrive or google drive etc.

[mvallevand]

Rovi doesn't use Zap2it/Tribune data so you really shouldn't expect channel number or unique_ids to match.

Martin

[slwtx1983]

It has been resolved. I also sent an email to the developer of MC2XML. It turns out that Microsoft updated Rovi and added some characters into the name field and they weren't being encoded properly. It is all fixed now.

[reedlabarge]

It has been resolved. I also sent an email to the developer of MC2XML. It turns out that Microsoft updated Rovi and added some characters into the name field and they weren't being encoded properly. It is all fixed now.

It appears that I am having this exact same problem. What was the resolution? Was there an update to MC2XML? Not resolved for me.

[slwtx1983]

It appears that I am having this exact same problem. What was the resolution? Was there an update to MC2XML? Not resolved for me.

Yes, there was actually an update to ROVI, and therefore a subsequent update to MC2XML. Contact the MC2XML guy and ask him for an update to the app. He said that ROVI added some sort of symbol to the display name field, and as he pulls from it, he had to update to compensate for that symbol.

[reedlabarge]

Yes, there was actually an update to ROVI, and therefore a subsequent update to MC2XML. Contact the MC2XML guy and ask him for an update to the app. He said that ROVI added some sort of symbol to the display name field, and as he pulls from it, he had to update to compensate for that symbol.

Awesome, thanks. I just emailed him. Thanks for the quick reply too, always appreciated when trying to troubleshoot