Project

General

Profile

Feature #4054

Maximum number of input streams

Added by Andreas Fornberg about 8 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
IPTV
Target version:
-
Start date:
2016-10-29
Due date:
% Done:

0%

Estimated time:

Description

When you add a network you can have Maximum number of input streams.
The problem is that it's 1 stream per m3u file so if you add more than 1 m3u file with same networkname it will use more than 1 stream on that network and that's not what i want.
I know i can have everything in 1 big m3u file but it's easier to maintain in smaller m3u files.
Option to limit to 1 stream for whole network and not only that m3u file would be nice.
Or changing behaviour so it works like that always works too.

History

#1

Updated by Jaroslav Kysela about 8 years ago

Could you retry with v4.1-2302-ge06307b ? The connection / rate limiting should be done per network.

#2

Updated by Andreas Fornberg almost 8 years ago

Jaroslav Kysela wrote:

Could you retry with v4.1-2302-ge06307b ? The connection / rate limiting should be done per network.

I tried again with latest build and still same.
I can open 2 streams if they are in different m3u files.

#3

Updated by Andreas Fornberg almost 8 years ago

Tested little more now and seems i can open 2 streams even if it's same m3u file and i have 1 as max streams.

#4

Updated by Andreas Fornberg almost 8 years ago

After more tests it seems to be a bug.
If i open 1 stream in Kodi with HTSP profile and then 1 stream in webinterface or VLC it waits until i close the stream in Kodi.
But if i open stream in VLC for example with pass profile and then open 1 stream in Kodi with HTSP profile it doesn't work and opens 2 streams.

#5

Updated by Andreas Fornberg almost 8 years ago

After more testing on 2 machines with Kodi.
If i open a channel from same m3u file on both machines it says no free adapter on the other machine.
But if open a channel from the other m3u files then it opens the stream on both machines.
This is strange.

#6

Updated by Jaroslav Kysela almost 8 years ago

I guess that this bug is about the auto-IPTV-network in TVH. One imported m3u file is one network and as I wrote in comment 1, the rate / connection limiting is handled per network.

The incremental changes are not allowed, because the auto-import allows to remove the services(muxes). If you split the information accros many m3u files, how tvh should detect the removed services?

It's quite easy to write a m3u merger (the operation on the plain text file) using a simple script or through a local web server and server-side scripting.

#7

Updated by Andreas Fornberg almost 8 years ago

Merging m3u files are no problem but i would like to be able to use more than 1 big m3u files.
I know it's per network but if i it's same network it should not be able to use more than maximum streams and i have same networkname on more than 1 m3u file so it should check for the networkname and not which m3u file.
It seems to work in some scenaries when i have an HTSP stream open so somewhere it fails.

#8

Updated by Andreas Fornberg almost 8 years ago

Detecting removed services shouldn't be a problem because it just imports from more than 1 meu files but it's still imported into same networkname etc like it was 1 big m3u file.
I don't see any difference in imported channels except the servicename has another has another name in the beginning before channelname.
Or i am missing something?

#9

Updated by Jaroslav Kysela almost 8 years ago

You miss the point. Let's say that you have m3u file A with 10 services and m3u file B with 5 services. How TVH can detect, if one service from B was removed? If you have one m3u file with 15 services, tvh will remove the service at the end of import of this big m3u file (current behaviour). It's easy, "atomic" and understandable.

#10

Updated by Andreas Fornberg almost 8 years ago

If you remove 1 service from one of the m3u files it will just delete that service from that network. When you import the channel it knows the network.
If it's a different network it will not do anything.
If current behaviour is the wanted one then it's still a bug because in some cases it works as i wanted so i don't see why it shouldn't in other cases.

#11

Updated by Jaroslav Kysela almost 8 years ago

Provide '--trace service,subscription,mpegts,iptv' log when things fails (HTTP + HTSP subscriptions). https://tvheadend.org/projects/tvheadend/wiki/Traces

Also available in: Atom PDF