Posts: 3,101
Joined: Apr 2014
Reputation:
270
Post an example EXTINF line from your m3u with a Belgium channel with non-ascii characters.
Posts: 3,101
Joined: Apr 2014
Reputation:
270
2018-04-15, 13:29
(This post was last modified: 2018-04-15, 13:54 by primaeval.)
You have explicitly set tvg-ID="" so all your tvg_id's are not null but the empty string.
If you either fill them in with the ids that match channel id in the xmltv or remove the tvg-ID="" completely it should work.
Posts: 3,101
Joined: Apr 2014
Reputation:
270
If you're lucky 0.0.23 will match your streams to the channels.
Give it a try.
Posts: 61
Joined: May 2015
Reputation:
15
Version 0.0.21 working perfect here mate. What an awesome addon.
Posts: 13
Joined: Mar 2014
Reputation:
1
wigee
Junior Member
Posts: 13
Thx will check later...
XML list is provided by my provider so i do not know the id's...
Posts: 3,101
Joined: Apr 2014
Reputation:
270
I've put some code in to handle multiline <title> fields in 0.0.27.
See if that was the problem.
Posts: 3,101
Joined: Apr 2014
Reputation:
270
0.0.28 might fix it. There was a double utf8 encoding of xmltv program titles.
If not post or pm me a link to your xmltv file.
It might need a file encoding detection call.
Posts: 3,101
Joined: Apr 2014
Reputation:
270
I've added the same file encoding detection in for xmltv as for the m3u files in 0.0.29.
Let's see if that detects the proper encoding.
What does the first line of your xmltv file say? The one starting with <?xml
Posts: 27
Joined: Aug 2014
Reputation:
4
Working for me now, it takes like 5 times longer to make the xmltv.db so I just have to be patient each time it is created