NPVR choosing incorrect xml guide display-name after reboot

[drlava]

Hi, Longtime user of the program.  The one pain I've consistently had is the babysitting of OTA channel tuning updates and remapping these when they frequently change, and the playback loosing its place to seek around when watching live TV that isn't being 'recorded'.

Now, there's a new issue and I'm stumped: after rebooting my computer, the TV Guid can't find any of my channels guide information from the xml file from zap2xml.  Looking at the problem in more detail, it looks like NPVR is only seeing the numeric display-names from the XML file, when it used to capture and display the first display-name for each channel.

I've searched the settings and can't find one which lets me specify whether it uses fir first or last display-name entry for each channel.  Can anyone describe exactly how NPVR chooses which display-name to use, and how I can get deterministic control over this?

Examplea channel entry:
<channel id="I2.2.206506510.microsoft.com">
<display-name>102 MeTV</display-name>
<display-name>2.2 KATUDT2</display-name>
<display-name>2.2</display-name>
<icon src="https://zap2it.tmsimg.com/h3/NowShowing/62792/s70436_h3_aa.png" />
</channel>


it should be seeing and using 102 MeTV, but now, after no apparent changes that I've done, it's using 2.2 instead.

[Graham]

Does this help ... https://forums.nextpvr.com/showthread.ph...#pid550753

[drlava]

Hi Graham, thanks for the link. The guide is downloading OK before and after adding the zip code according to that post it's still downloading OK.. It just appears NPVR is not able to find the set up mapping, the dropdown list still shows all only channel numbers, not the named entries which I've previously mapped to the channels.

[Graham]

It just appears NPVR is not able to find the set up mapping, the dropdown list still shows all only channel numbers, not the named entries which I've previously mapped to the channels.

Zip and attach the xmltv file to a post (the zip needs to be less than 2MB).  I expect that someone will be able to tell you if there is anything odd about it.

[sub]

Hi Graham, thanks for the link.  The guide is downloading OK before and after adding the zip code according to that post it's still downloading OK..  It just appears NPVR is not able to find the set up mapping, the dropdown list still shows all only channel numbers, not the named entries which I've previously mapped to the channels.

In most places in the world an xmltv file would only have one <display-name> in each <channel>. These multiple <display-name> is something that can happen in North America.

Ultimately, NextPVR is mapped to the channel id, not the display name. ie "I2.2.206506510.microsoft.com" in the example above, so the mapping itself should be fine, but I understand it could be confusing if you have to view/change the mapping (because it didn't know which of the display-name's to use, so it just showed one of them. Effectively, all of the display-names lead to the same result.

In v5 there were some improvements around this, and it should show a more appropriate display name.

[drlava]

Thanks for taking a look sub, I'm attaching the log as well.

[drlava]

The loaded data appears to have been resolved. For me it was a matter of clearing the cache files from the zap2xml working folder,and re - generating the xml. In the end it's working again, but the XMLTV file is still being loaded, only showing the numbers rather than the manually created channel number + name, which is the first entry display-name.
In the future, if there's a setting which allows us to specify the display-name selection algorithm (first, last, auto) which chooses the entries for the mapping drop-down, that would help greatly with mapping.

[sub]

In the future, if there's a setting which allows us to specify the display-name selection algorithm (first, last, auto) which chooses the entries for the mapping drop-down, that would help greatly with mapping.

There has already been improvements in this. You should see the full display-name in v5.