telly 1.5 beta, m3u from tvheadend #210

alturismo · 2018-10-01T20:15:07Z

version 1.5 beta, tested on unraid docker and windows

last working version is 1.1 dev branch (not ffmpeg)

issue, unable to parse ... sample from log

sample from m3u playlist (tested as file loaded or http grab)

xFilosofx · 2018-12-12T05:32:38Z

I have same issue with 1.5 beta on my windows server. I used UDPtoHTTP Proxy service on my router for translate IPTV from my ISP to telly server.
m3u example:
#EXTM3U
#EXTINF:-1 tvg-name="Первый", Perv
http://192.168.1.1:4022/udp/238.1.1.32:1234
#EXTINF:-1 tvg-name="Россия 1", Ros
http://192.168.1.1:4022/udp/238.1.1.33:1234
#EXTINF:-1 tvg-name="МАТЧ!", Match
http://192.168.1.1:4022/udp/238.1.1.34:1234
#EXTINF:-1 tvg-name="НТВ", NTV
http://192.168.1.1:4022/udp/238.1.1.35:1234
Telly Log:
Unable to process M3U track, continuing http://192.168.1.1:4022/udp/238.1.1.32:1234
Unable to process M3U track, continuing http://192.168.1.1:4022/udp/238.1.1.33:1234
Unable to process M3U track, continuing http://192.168.1.1:4022/udp/238.1.1.34:1234
Unable to process M3U track, continuing http://192.168.1.1:4022/udp/238.1.1.35:1234

rafuz · 2019-02-17T19:42:49Z

I have checked on the latest build and I still can't import an m3u directly from Tvheadend.
It works on 1.1 dev

chazlarson · 2019-02-17T22:14:21Z

In 1.5 the M3U handling seems to contain some assumptions about how the stream URLs will be formatted. URLs like the ones above will challenge it.

1.1 just reads in and stores the URL as it is in the M3U, so seems like for non-standard cases like this 1.1 is the better choice at this time.

Provide feedback