tvg-chno - m3u channel numbers seem to be ignored when "Import using XC"

[brcarls]

I just did a fresh install of NextPVR on Unraid/Docker

I added an IPTV device using "Import using XC"

My m3u has tvg-chno fields which should be all unique.  Example:  

Code:

#EXTINF:-1 tvg-id="112" tvg-name="30A Darcizzle Offshore (720p)" tvg-logo="http://192.168.67.3:9191/api/channels/logos/6304/cache/" tvg-chno="112" group-title="Dispatcharr",30A Darcizzle Offshore (720p)

Expected behavior:   Channels appear in NextPVR with the tvg-cho channel numbers
Observed behavior:  Channel numbers in NextPVR start at one and increment sequentially instead of using the tvg-cho numbers.  They do appear to be sorted by tvg-cho (or maybe just the order they appear in the m3u?)

I have attached logs, though I'm not certain if this is a bug or working as designed.   I had assumed the channel numbers would show up because IIRC HDHR channels numbers were mapped correctly when I did that in the past.

[mvallevand]

Could you capture the web page on the scan, it looks ok here.

Martin

[brcarls]

Still starts at 1 for me when I use "Import using XC", but I guessed that you loaded that m3u snippet with the "Import using m3u" button...   So I tried that and it worked as expected with the  tvg-chno channel numbers.

(edit: that's not a great fix though because I lose features from my backend when using m3u rather than XC not to mention m3us are so insecure )

[brcarls]

Is there a debug setting to have NextPVR echo the m3u it downloaded via XC API? Still not convinced it's a NextPVR bug so would like to confirm if tvg-cho is actually present when using XC instead of M3U.

[mvallevand]

I made a mistake so deleted my last post sinc XC login doesn't use an m3u file and any m3u tags are irrelevant.

Does Dispatcharr support the XC standard m3u?

Code:

http://server/get.php?username=username&password=password&type=m3u&output=m3u8

Martin

[brcarls]

I pulled the xml from the XC API and don't see any "tvg-cho" fields. I do see " <channel id="121">"

No idea what is correct.... I just wish NextPVR would use the channel numbers from XC. What does NextPVR expect to see?

[brcarls]

I made a mistake so deleted my last post XC login doesn't use an m3u file so any m3u tags are irrelevant.

Does Dispatcharr support XC m3u files typically with a URL like  If so just use m3u login.

Code:

http://server/get.php?username=username&password=password&type=m3u&output=m3u8

Martin

Thanks.    I had always assumed that XC just securely downloaded the .m3u and .xml.gz.  So apologies for the wild goose chase.  As you can see, I don't even know what questions to ask, but we got there  anyway.

What does NextPVR expect to see for a channel number field in XC?  I'll submit a Dispatcharr feature request.

[mvallevand]

The XC API is JSON. so I don't understand your comment about XML. A typical XC livestream JSON response is shown here https://stackoverflow.com/questions/7884...-codes-api and there is no channel number in there.

Martin

[brcarls]

Also, dispatcharr does produce .m3u files that make NextPVR happy, but I migrated to XC because I started using it over the internet and don't want to send credentials in the URL.

[mvallevand]

I am confused since XC credentials are in the URL too.

Martin