Bug #5850
Tvheadend don't switch to the next service after timeout
0%
Description
Hi,
I have 2 IPTV network providers with each has 2 instances for each channel (HD and FHD). So for 1 channel i have 4 instances i can use (for example:)
- Provider 1 - Channel 1 HD (priority: 10)
- Provider 1 - Channel 1 HD2 (priority: 8)
- Provider 2 - Channel 1 HD (priority: 1)
- Provider 2 - Channel 1 HD2 (priority: 1)
What i noticed is that when i ran Channel 1 today it starts with Provider 1 - Channel 1 HD it was down, it tries HD2 too but it doesn't try the other 2.
I'm using PASS and "Switch to another service is enabled".
I added some logging and replaced some things (username, ID's etc.).
Maybe it is because i am using different names in the playlist files for the same stremas? HD, HD2 etc. But at Configuration > Channels/EPG > Channels the HD and HD2 variants are selected.
Anyone? :-)
Thank you.
Files
History
Updated by MJ Derksen almost 5 years ago
Updated by Did some more testing. Could even reproduce the same issue within Docker with the latest tvheadend release.
I got it working using the following:
At DVB Inputs > Networks i did a combination of (streaming) priority and max timeout.
OLD SITUATION - does not work
Provider 1:
Priority: 1
Streaming Priority: 1
Maximum timeouts (sec): 3
Provider 2:
Priority: 1
Streaming Priority: 1
Maximum timeouts (sec): 3
NEW SITUATION - does work
Provider 1:
Priority: 1
Streaming Priority: 10
Maximum timeouts (sec): 6
Provider 2:
Priority: 1
Streaming Priority: 8
Maximum timeouts (sec): 6
When changing the maximum time-out to 10 seconds it doesn't work. That doesn't make sense. I want to keep this number as low as possible because when some channels are down it will take some long time to start a channel.