Duplicate Channels Missing Guide Data

Hi,

New subscriber here. I've looked through other topics but am struggling to find similar examples, apologies for any overlap.

I have some duplicate channels that share EPG data. I understand tvg-id is used to map data and does not need to be unique. The tvg-id is being mapped correctly to all channels, but I only get guide data for the first channel and not any duplicates which follow it. Am I doing something wrong?

Example

channels.m3u

#EXTINF:0 CUID="135645" tvg-name="SE| SVT1" tvg-ID="guide2go.69430.schedulesdirect.org" tvg-logo="svt1.png" group-title="Sweden",SE| SVT1
http://stream.m3u8

#EXTINF:0 CUID="135682" tvg-name="SE| SVT1 HD" tvg-ID="guide2go.69430.schedulesdirect.org" tvg-logo="svt1.png" group-title="Sweden",SE| SVT1 HD
http://stream.m3u8

#EXTINF:0 CUID="135646" tvg-name="SE| SVT2" tvg-ID="guide2go.69431.schedulesdirect.org" tvg-logo="svt2.png" group-title="Sweden",SE| SVT2
http://stream.m3u8

#EXTINF:0 CUID="135683" tvg-name="SE| SVT2 HD" tvg-ID="guide2go.69431.schedulesdirect.org" tvg-logo="svt2.png" group-title="Sweden",SE| SVT2 HD
http://stream.m3u8

guide.xml

<channel id="guide2go.69430.schedulesdirect.org">
<display-name>SVT1</display-name>
<display-name>SVT1</display-name>
</channel>

<channel id="guide2go.69431.schedulesdirect.org">
<display-name>SVT2</display-name>
<display-name>SVT2</display-name>
</channel>

Manage lineup in channels, guide data indexed and auto mapped by system

Guide view, system missing data for any duplicate instances of either channel

Is it because I have CUID in the m3u instead of channel-id? I have also seen channelID used by some programs like xTeVe.

From reading other topics here though, it seems that if CUID is ignored the system should then look at tvg-name which also seems to hold unique values in my example above.

Edit:

Replacing CUID with channel-id made no difference so I am pretty lost. Could it be a bug?

Yes it sounds like a bug

Ok thanks @tmm1 let me know if I can help with logs or anything

Just wanted to check, is there any ETA for a fix? Or do you need any more info? Thanks!

Still seeing this bug in pre-release 2023.10.10.0059.

Please try the latest prerelease:

Yes it seems to be solved, thank you very much!

1 Like