search

xteve-project / xTeVe

M3U Proxy for Plex DVR and Emby Live TV
MIT License
1.72k stars 227 forks source link

xteve.m3u produces tons of duplicates/wrong channels #253

Open asdproton opened 2 years ago

asdproton commented 2 years ago

Hi,

I created a m3u from enigma and imported this in xteve. I mapped an EPG XML. Everything is fine. A few days later however I notice that in Plex I choose channel A it display video of channel B.

When I look into the xteve GUI I see that the channel name is correct (A) but directly below it shows the name of the wrong channel (B). xteve.m3u also shows this. While the first line is correct

EXTINF:0 channelID="x-ID.8" tvg-chno="1008" tvg-name="VOX HD" tvg-id="1008" tvg-logo="" group-title="enigma",VOX HD

the second line reflects the stream ID of the wrong channel. After time this wrong channel (the last one in my channel list) is duplicating itself on top of other channels and it seems to get worse day after day.

When I delete the M3U, reenter it and redo the mapping all is well for a certain period. But this is a PITA for 60+ channels every few days. Any idea where to look?

xteve 2.2.0.

asdproton commented 2 years ago

Just happened once more. Strangely enough the duplicates are always duplicates to the last channel of the m3u list I have (which is N24 DOKU). Any idea where to look? The only fix is to kill the m3u and redo the entire matching. This is terribly annoying.

isusac commented 2 years ago

I'm having the exact same issue. I use two lists one is from enigma2 receiver and the other one is regular IPTV list.

MCTyler commented 2 years ago

Sounds like a issue coming from the Provider, but we will look into it.

isusac commented 2 years ago

I think this is the same issue as https://github.com/xteve-project/xTeVe/issues/230

I tried the beta version and it seams it is fixed in beta.

asdproton commented 2 years ago

Thanks. What version number should I look for? 2.2.0 is what my docker image provides. Starting with what number this should be fixed? Sorry if this is a dumb question.

isusac commented 2 years ago

It is fixed in 2.2.0 beta version. I downloaded beta and I'm using that version now.

asdproton commented 2 years ago

I switched my docker to "beta" with a setting in settings.json (at least the web interface reads beta now). Let's see what happens.

MCTyler commented 2 years ago

Beta and Release are the same Build now for over a year.

isusac commented 2 years ago

I don't know what to tell you. With regular release I have the issue, but with beta I don't.

2fst4u commented 1 year ago

I'm just now running into this issue. Has any progress on this occurred? Does running the beta branch still resolve this?

MCTyler commented 1 year ago

There is no Beta branch. All releases are the same.

2fst4u commented 7 months ago

There is no Beta branch. All releases are the same.

How do we overcome it then? I still seem to be getting this issue.

isusac commented 7 months ago

Make sure you have a distinct channel ID. I have the same issue and it was resolved when I fixed this.

On Sun, Nov 26, 2023 at 9:36 AM 2fst4u @.***> wrote:

There is no Beta branch. All releases are the same.

How do we overcome it then? I still seem to be getting this issue.

— Reply to this email directly, view it on GitHub https://github.com/xteve-project/xTeVe/issues/253#issuecomment-1826723206, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB6ZZCTCXA24RWWLG5TGLSLYGL5QLAVCNFSM5BXZON22U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBSGY3TEMZSGA3A . You are receiving this because you commented.Message ID: @.***>