Project

General

Profile

Actions

Bug #3912

open

SAT>IP multiple sources / networks with different tuner types

Added by Oliver Oswald almost 9 years ago. Updated over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
SAT>IP
Target version:
-
Start date:
2016-07-26
Due date:
% Done:

0%

Estimated time:
Found in version:
4.1.xxxx (most recent git clone from master)
Affected Versions:

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
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 -
405

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 1 (0 open1 closed)

Copied to Bug #3915: SAT>IP multiple sources / networks with different tuner typesInvalid2016-07-26

Actions
Actions

Also available in: Atom PDF