search

tellytv / telly

An IPTV proxy
MIT License
769 stars 107 forks source link

telly 1.5 beta, m3u from tvheadend #210

Open alturismo opened 6 years ago

alturismo commented 6 years ago

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

Unable to process M3U track, continuing http://192.168.1.2:9981/stream/channelid/1688975059?ticket=e88f4689547cde2aee361366a58275ac82f5627f&profile=pass

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

EXTM3U

EXTINF:-1 logo="http://192.168.1.2:9981/imagecache/919" tvg-id="7cb7d7652fbe4577641f9c87409bcdc0" tvg-chno="10",Das Erste HD

http://192.168.1.2:9981/stream/channelid/1708636028?ticket=8fb399b1d3e7a2a16bdc8a29ef7d0b16940b6d50&profile=pass

EXTINF:-1 logo="http://192.168.1.2:9981/imagecache/920" tvg-id="f2b7a6d3243d1aa60179bf7cee17a43d" tvg-chno="15",ZDF HD

http://192.168.1.2:9981/stream/channelid/1403434994?ticket=255665d3eeff03245b988119e35ae80b011064aa&profile=pass

xFilosofx commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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.