Bug #3912
SAT>IP multiple sources / networks with different tuner types
0%
Description
It seems that there is an issue when you combine multiple tuner types
for sat>ip services in tvheadend.
Tuners:
4x DVB-C tuners (local on system) -> PCTV 292e with em28xx driver
4x DVB-S+DVB-S2 tuners (remote via sat>ip) -> TSS 400 MKII SAT>IP server
Networks:
DVB-C -> SAT>IP SourceID: 1
DVB-S -> SAT>IP SourceID: 2
SAT>IP Settings:
Port: 9983 (to run without root priveleges)
Client:
DVBViewer Pro 5.6.4
Reproduce Issue:
Connecting with a SAT>IP client (in my example DVBViewer) seems to work flawlessly when using the network
that got the SAT>IP SourceID 1 in TVH:
tvheadend2554: mpegts: 586MHz in DVB-C - tuning on Silicon Labs Si2168 : DVB-C #0
tvheadend2554: subscription: 000B: "SAT>IP" subscribing to mux "586MHz", weight: 100, adapter: "Silicon Labs Si2168 : DVB-C #0", network: "DVB-C", service: "Raw PID Subscription", hostname="172.16.0.1"
tvheadend2554: subscription: 000C: "SAT>IP Slave/DVB-C/586MHz/PULS 4 Austria" subscribing to service "DVB-C/586MHz/PULS 4 Austria", weight: 100, adapter: "Silicon Labs Si2168 : DVB-C #0", network: "DVB-C", mux: "586MHz", provider: "DVB-C", client="SAT>IP Slave/DVB-C/586MHz/PULS 4 Austria"
When tuning with the same SAT>IP client (but settings changed to DVB-S2) to the second network (SAT>IP SourceID 2)
following error is logged:
tvheadend2554: satips: 0/37F4EFAA/7: unable to create mux DVB-S2 freq 11671000 H sym 22000000 fec 2/3 mod PSK/8 roff 35 is_id 1 pls_mode ROOT pls_code 0 405
tvheadend2554: http: 172.16.0.1: RTSP/1.0 SETUP rtsp://172.31.255.190:9983/?src=1&freq=11671&msys=dvbs2&plts=off&fec=23&pol=h&ro=0.35&sr=22000&mtype=8psk&pids=0 -
When changing the SAT>IP SourceID for the networks (1 is now 2 and 2 is now 1) the DVB-S2 connection starts working:
tvheadend2551: mpegts: 11670.75H in DVB-S - tuning on SAT>IP DVB-S Tuner #1 (172.31.255.191)
tvheadend2551: subscription: 0004: "SAT>IP" subscribing to mux "11670.75H", weight: 100, adapter: "SAT>IP DVB-S Tuner #1 (172.31.255.191)", network: "DVB-S", service: "Raw PID Subscription", hostname="172.16.0.1"
But the second network fails now:
tvheadend2551: satips: 0/ABAC9280/3: unable to create mux DVB-C freq 586000000 sym 6900000 mod QAM/256 fec AUTO
tvheadend2551: http: 172.16.0.1: RTSP/1.0 SETUP rtsp://172.31.255.190:9983/?freq=586&msys=dvbc&sr=6900&specinv=0&mtype=256qam&pids=0 -- 405
As I am not really that pro linux guy I am now really out of options on my side. It seems that the SAT>IP server is trying to use the wrong tuner for the second SAT>IP SourceID.
If you need more information - just drop a line and i'll try to get some more data out of it.
Related issues
History
Updated by saen acro over 8 years ago
Updated by Use temporary Kodi as TVH client to solve problem.
error 405 in your log = bad api communication.
Updated by Oliver Oswald over 8 years ago
Updated by Found a possible workaround - it seems that the SourceID settings is pretty good described in the tvheadend manual:
http://docs.tvheadend.org/webui/config_networks/
SAT>IP Source Number : This field is matched through the “src” parameter asked from the SAT>IP client. Usually (and
by default) this value is 1. For satellite tuners, this value determines the satellite source (dish). By specification
position 1 = DiseqC AA, 2 = DiseqC AB, 3 = DiseqC BA, 4 = DiseqC BB, but any numbers may be used - depends on the
SAT>IP client. Note that if you use same number for multiple networks, the first matched network containing the mux
with requested parameters will win (also for unknown mux). If this field is set to zero, the network cannot be used
by the SAT>IP server.
Somehow - when setting both Networks (DVB-C and DVB-S) to SourceID "1" both start working (without any error messages).
But nevertheless it seems bugged when e.g. setting DVB-S to "1" and DVB-C to "2" (which number to use when DVB-S contains
all of the DiseqC zones ?).
Updated by saen acro over 8 years ago
So bug in TVH configuration, with not check itself for duplicating values.
Updated by Oliver Oswald over 8 years ago
- Copied to Bug #3915: SAT>IP multiple sources / networks with different tuner types added
Updated by Oliver Oswald over 8 years ago
Not really - configuration was correct - it seems with invalid configuration
e.g. sourceids 1 and 1 (instead of the correct sourceids 1 and 2 ) it works as
it is intended with correct configuration.
So yes - there seems to be a bug - or at a minimum a documentation lack regarding
the usage of sourceid with different tuner types.
Updated by Jaroslav Kysela over 8 years ago
Updated by Perhaps, there's just a misunderstanding what 'src' parameter means in SAT>IP. For DVB-C and DVB-T this value must be 1 (because only one input source is available usually - no cable / antenna switch or so). For satellite, this value means the diseqc position which is defined on the server. So, it's extra information for the tuning. The source IDs should be unique only for the same tuner type.
Updated by Oliver Oswald over 8 years ago
Ok - thanks for your input Jaroslav - so it seems my "workaround" seems to be the intended usage ^^.
So I think we're done here - no bug at all now 
Updated by g siviero almost 6 years ago
Updated by Could you please add this note to the Help pages (DVB Inputs - Networks)?
For DVB-C and DVB-T this value must be 1 (because only one input source is available usually - no cable / antenna switch or so).
Now the Help reads:
SAT>IP source number : The SAT>IP source number.
I think it would be useful for example:
SAT>IP source number : The SAT>IP source number. (For DVB-C and DVB-T this value should be set to 1)
So if mixed tuners (SAT + DVB-T ) are used people (like me ) would remember to set this value to 1 for DVB-T (and not for example 5 when the previous networks are 1,2,3,4 from a diseqc switch).
Thanks