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

[brcarls]

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

I'm not a dev and am so confused....   I hit the API using the URL that you deleted and the response looks like this:

Code:

<?xml version="1.0" encoding="UTF-8"?>
<tv generator-info-name="Dispatcharr" generator-info-url="https://github.com/Dispatcharr/Dispatcharr">
  <channel id="121">
    <display-name>World Fishing Network (1080p)</display-name>
    <icon src="http://192.168.67.3:9191/api/channels/logos/6305/cache/" />
  </channel>
  <channel id="122">
    <display-name>30A Darcizzle Offshore (720p)</display-name>
    <icon src="http://192.168.67.3:9191/api/channels/logos/6304/cache/" />
  </channel>
  <programme start="20260113120000 +0000" stop="20260113123000 +0000" channel="121">
    <title>Connect Fishing Experiences</title>
    <sub-title>Jigging Blubber Bay</sub-title>
    <desc>It is summer, so Josh puts the downriggers away and spends a day jigging the shallow waters around the lighthouse at Blubber Bay.</desc>
    <category>Episode</category>
    <category>Series</category>
    <category>Outdoors</category>
    <category>Fishing</category>
    <episode-num system="dd_progid">EP06217771.0002</episode-num>
    <video>
      <quality>HDTV</quality>
    </video>
    <date>20260105</date>
    <icon src="https://zap2it.tmsimg.com/assets/p32055058_b_h9_aa.jpg" />
    <previously-shown />
  </programme>
xxxx  snip  xxxx

[mvallevand]

Ok that is the guide not the channel list. It seems there is a potential here for an option since Dispatcharr is using the preferred channel number as the channel id. This is not normal, it is usually a text field.

With this URL

Code:

http://server/player_api.php?username=username&password=password&action=get_live_streams"

does epg_channel_id": show that channel number. You might have trouble looking at a JSON file.

Martin

[brcarls]

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

Martin

Sorry    Just trying to figure out how to get the desired behavior and have seen repeatedly that m3u is unsecure and is a great way to have your credentials stolen.   I did more assuming that it was related to credentials in a plain text http URL

I guess what I really need is guidance on the feature request I should submit to dispatcharr so that I don't confuse them.   I just want NextPVR to use channel numbers from XC.

[mvallevand]

Check my last post, Dispatcharr is already trying to re-define too many standards but there might be a work around. In the XC world of thousands of channel numbers and many repeats for 100s's US and Canadian cities a fixed channel number doesn't make sense.

Martin1

[brcarls]

Ok that is the guide not the channel list. It seems there is a potential here for an option since Dispatcharr is using the preferred channel number as the channel id.  This is not normal, it is usually a text field.

With this URL

Code:

http://server/player_api.php?username=username&password=password&action=get_live_streams"

does  epg_channel_id": show that channel number.  You might have trouble looking at a JSON file.

Martin

Yes, it does.

Code:

[{"num": 121, "name": "World Fishing Network (1080p)", "stream_type": "live", "stream_id": 6520, "stream_icon": "http://192.168.67.3:9191/api/channels/logos/6305/cache/", "epg_channel_id": "121", "added": 1763825941, "is_adult": 0, "category_id": "2023", "category_ids": [2023], "custom_sid": null, "tv_archive": 0, "direct_source": "", "tv_archive_duration": 0}, {"num": 122, "name": "30A Darcizzle Offshore (720p)", "stream_type": "live", "stream_id": 6519, "stream_icon": "http://192.168.67.3:9191/api/channels/logos/6304/cache/", "epg_channel_id": "122", "added": 1763825727, "is_adult": 0, "category_id": "2023", "category_ids": [2023], "custom_sid": null, "tv_archive": 0, "direct_source": "", "tv_archive_duration": 0}]

[mvallevand]

So it really depends if sub wants to use that as a hacky way of forcing a channel number via a config.xml setting.

Martin

[brcarls]

Check my last post, Dispatcharr is already trying to re-define too many standards but there might be a work around.  In the XC world of thousands of channel numbers and many repeats for 100s's US and Canadian cities a fixed channel number doesn't make sense.

Martin1

I get all of that.    I don't care that much about the actual channel numbers and lived with it for a while...   But when I insert a new channel,  it gets appended instead of inserted into its "correct" spot in the lineup.    

I have to blow away all of channels because the sequential numbering doesn't leave gaps for new channels like I did when setting up the channels in Dispatcharr.    I'm probably doing something wrong there too, but I thought the correct approach would be to figure out why the channel numbers from XC get ignored.

Code:

So it really depends if sub wants to use that as a hacky way of forcing a channel number via a config.xml setting.

The last thing I want is a hack or band-aid.     If the proper fix is on the Dispatcharr side,  please help me understand what I should request?

[mvallevand]

No as I showed you the Xtream API doesn't define an equivalent to tvg-chno, there is nothing that Dispatcharr can do other than cusomizing the standard and then hoping that other programs use it. One way or another NextPVR won't support it out of the box.

Since NextPVR"s XC login doesn't current support updates right now don't you have to remove and re-add anyway? If XC updates are implemented I am hoping that Dispatcharr is able to deal with all the logic to ensure the API num: value is fixed.

Martin

[mvallevand]

Sub has added this for the next release, since it works as Dispatcharr is designed so it is less of a hack then I expected.

Martin