Feature #4082
IPTV Automatic Network
0%
Description
Hello,
I would like to ask you whether it is possible to add a button to force update of all muxes(streams) from m3u. There is an option "re-fetch period", but it only looks for new muxes(streams) in file, but it doesn't update already existing one.
Also second request, but it is about the same m3u file... so i put it there... whether it is possible to add special TAGS for every stream, so it can be automatically added when mapping the stream to channel.
for example:
#EXTM3U
#EXTINF:0,STV1
#EXTTAGS:movies,slovak
rtp://232.232.64.1:5004
Thx
History
Updated by Jaroslav Kysela almost 8 years ago
There is an option "re-fetch period", but it only looks for new muxes(streams) in file, but it doesn't update already existing one.
The muxes should be always updated unless the URL changes. Then it's handled like a new mux and the old mux is deleted.
Updated by Emil Halko almost 8 years ago
I have tested it once more, but it doesn't work... I have changed the name of few muxes/streams, but no updates... I'm using HTS Tvheadend 4.1.2309
m3u parser has been running few times but without changing anything ...
2016-11-15 23:00:28.925 iptv: m3u parse: 0 new mux(es) in network 'Antik IPTV' (total 254)
2016-11-15 23:01:28.924 iptv: m3u parse: 0 new mux(es) in network 'Antik IPTV' (total 254)
2016-11-15 23:02:28.924 iptv: m3u parse: 0 new mux(es) in network 'Antik IPTV' (total 254)
2016-11-15 23:03:28.924 iptv: m3u parse: 0 new mux(es) in network 'Antik IPTV' (total 254)
2016-11-15 23:04:28.925 iptv: m3u parse: 0 new mux(es) in network 'Antik IPTV' (total 254)
2016-11-15 23:05:28.925 iptv: m3u parse: 0 new mux(es) in network 'Antik IPTV' (total 254)
Updated by Jaroslav Kysela almost 8 years ago
Do you see changes in webui for those muxes / services ?
Updated by Emil Halko almost 8 years ago
No changes... I only see changes when there is new mux added into file...
Updated by Emil Halko almost 8 years ago
I have done some more tests... Created another network and add some muxes there... When I moved mux/stream from network to network it works perfectly... removed in one and added to second... but when I just renamed mux/strem it doesn't work....
Updated by Jaroslav Kysela almost 8 years ago
OK, The mux name is changed only when it's empty. If it's already set, the old value is used. But the service name in the mux should be changed so the channel name should be updated, too (if you didn't override it manually). I just tried and it works.
Updated by Jaroslav Kysela almost 8 years ago
Tags are already supported using 'tvh-tags':
#EXTIF:-1 tvh-tags="tag1|tag2",Service name
Updated by Emil Halko almost 8 years ago
Yeah, you are right.... It changed service name in the mux... little bit tricky, but enough for me as channel mapping use service name
note: but maybe it would be better to update both value as it will be more straight forward for everybody
anyway thanks for you support/help also for last update regarding tagging, because I was searching for this information everywhere but without success
Updated by Andreas Fornberg almost 8 years ago
I would like support for "group-title"
For example
#EXTINF:-1 tvg-id="example" tvg-name="example" tvg-logo="examplechannel.jpg" group-title="Entertainment",Example Channel
Updated by Andreas Fornberg almost 8 years ago
I would like support for "group-title"
For example
#EXTINF:-1 tvg-id="example" tvg-name="example" tvg-logo="examplechannel.jpg" group-title="Entertainment",Example Channel
In this case that channel should be added to channeltag group "Entertainment"
Updated by Jaroslav Kysela almost 8 years ago
Jaroslav Kysela wrote:
andreas öman: See my answer in comment 7 .
Sorry, group-title appears to be a new valid attribute. I added support for this to v4.1-2332-g38c9e89 .
Updated by Andreas Fornberg almost 8 years ago
Jaroslav Kysela wrote:
Jaroslav Kysela wrote:
andreas öman: See my answer in comment 7 .
Sorry, group-title appears to be a new valid attribute. I added support for this to v4.1-2332-g38c9e89 .
Thx! You can close this as fixed https://www.tvheadend.org/issues/4070