Bug #2716
SAT>IP bad tuner type
0%
Description
I have an Octopus NET with 2 TwinTuner DVB-C/C2/T/T2 acting as SAT>IP server (10.92.40.207)
As SAT>IP client, I'm using Tvheadend 3.9.2525~g96898a6~wheezy running on a Debian 7.8
When starting the Tvheadend service, I'm getting the following error: "satip: 10.92.40.207: bad tuner type [DVBC2-2]". And I'm getting only 2 SAT>IP DVB-T tuners inside the Tvheadend tuners section.
The Octopus available tuners in the XML are:
<satip:X_SATIPCAP>DVBT2-2,DVBC2-2</satip:X_SATIPCAP>
The Octopus is running the last firmware version.
Files
History
Updated by Quentumm S over 9 years ago
I probably found which part of the code is "faulty". In tvheadend/src/input/mpegts/satip/satip.c, the following code should be added:
else if (strncmp(argv[i], "DVBC2-", 6) == 0) { type = DVB_TYPE_C; m = atoi(argv[i] + 6); }
in order to catch DVBC2 tuners which are DVBC and DVBC2 compatible.
Updated by Quentumm S over 9 years ago
I've cloned the Tvheadend git, applied the pull request #597 (SAT>IP Server Implementation #597), compiled and launched tvheadend.
I get now the 4 tuners as expected (2x DVB-T and 2x DVB-C). After the creation of the "Cablecom" network under DVB > Network and the mapping of one of the DVB-C tuner to this network, Tvheadend is unable to start the scanning of the muxes. I've got the following error:
2015-03-20 21:07:58.007 [ INFO] mpegts: 426MHz in Cablecom - tuning on SAT>IP DVB-C Tuner #3 (10.92.40.207)
2015-03-20 21:07:58.007 [ INFO] subscription: 0042: "scan" subscribing on "none", weight: 2, adapter: "SAT>IP DVB-C Tuner #3 (10.92.40.207)", network: "Cablecom", mux: "426MHz", provider: "<N/A>", service: "Raw PID Subscription"
2015-03-20 21:07:58.011 [ ERROR] satip: SAT>IP DVB-C Tuner #3 (10.92.40.207) - RTSP SETUP error -5 (Input/output error) [5-404]
2015-03-20 21:08:03.004 [ INFO] mpegts: 426MHz in Cablecom - scan no data, failed
2015-03-20 21:08:03.004 [ INFO] subscription: 0042: "scan" unsubscribing
Does anyone can help ?
Thanks
Updated by Quentumm S over 9 years ago
I've found the reason:
https://tvheadend.org/boards/5/topics/11793?r=12887
Updated by Jaroslav Kysela over 9 years ago
- Status changed from New to Fixed
Fixed in v3.9-2613-g93f3f6f .