Bug #4526
service instance is bad, reason: No input detected with TVH 4.3-322~g0960791 SAT>IP servers
100%
Description
I have a central installation with version 4.3-210~g7644886-dirty (on a QNAP NAS) that acts as a SAT>IP client which connects to multiple TVH SAT>IP servers.
Up to version 4.3-295~ga9dffb7 on the servers all worked fine.
Today I tested version 4.3-322~g0960791 on the TVH SAT>IP servers and was unable to record on the central client (4.3-210~g7644886-dirty):
2017-08-10 10:55:57.287 dvr: entry 670e6af3ad0215377bc4eb4104f74091 "..." on "..." starting at 2017-08-10 10:26:30, scheduled for recording by "192.168.1...." 2017-08-10 10:55:57.287 dvr: "..." on "..." recorder starting 2017-08-10 10:55:57.287 mpegts: ... in DVB-S Hotbird 13E - tuning on SAT>IP DVB-S Tuner #1 (192.168.1.xxx:9983) 2017-08-10 10:55:57.287 subscription: 05E3: "DVR: ..." subscribing on channel "...", weight: 100, adapter: "SAT>IP DVB-S Tuner #1 (192.168.1.xxx:9983)", network: "DVB-S Hotbird 13E", mux: "...", provider: "...", service: "...", profile="pass" 2017-08-10 10:56:07.287 subscription: 05E3: service instance is bad, reason: No input detected 2017-08-10 10:56:07.287 mpegts: ... in DVB-S Hotbird 13E - tuning on SAT>IP DVB-S Tuner #1 (192.168.1.xxy:9983) 2017-08-10 10:56:07.287 subscription: 05E3: "DVR: ..." subscribing on channel "...", weight: 100, adapter: "SAT>IP DVB-S Tuner #1 (192.168.1.xxy:9983)", network: "DVB-S Hotbird 13E", mux: "...", provider: "...", service: "...", profile="pass" 2017-08-10 10:56:17.287 subscription: 05E3: service instance is bad, reason: No input detected 2017-08-10 10:56:19.287 subscription: 05E3: No input source available for subscription "DVR: The Good Wife" to channel "..." 2017-08-10 10:56:19.288 dvr: Recording unable to start: "...": No input detected
If I revert to version 4.3-295~ga9dffb7 all is working fine again.
What am I missing?
History
Updated by Jeroen Hendriks about 7 years ago
Updated by I can confirm this.
It only effects my DVB-S TVHeadend SAT/IP server. My TVHeadend SAT/IP server with DVB-C tuners works just fine. (both are running on a Rapsberry 3). I am running SAT/IP in TCP mode
Updated by Jeroen Hendriks about 7 years ago
Hmm just tested again with 4.3-326~g3021698. Some SAT Muxes do work.
For example 23.5°E 12109.50H DVB-S2 8PSK 27500 3/4 doesn't work, but 28.2°E 11127.00V DVB-S QPSK 22000 5/6 does clean the channels just fine.
Can't test more at this moment, running a another test :-)
But would be good if we test if it's 8PSK/QPSK or DVB-S/DVB-S2 releated issue.
Can you check if your DVB-S transponders work while using 4.3-322~g0960791 or the current master version? Maybe it only effect DVB-S2 transponders.
Will test tomorrow what it does on my server/client setup...
Updated by Jeroen Hendriks about 7 years ago
Tested with 4.3-330~g1c6c915
DVB-S channels work just fine
DVB-S2 channels give a "service instance is bad, reason: No input detected" error
Something is broken in the SAT/IP server code effecting DVB-S2.
Updated by Jaroslav Kysela about 7 years ago
Updated by Could you test this simple change?
diff --git a/src/satip/rtsp.c b/src/satip/rtsp.c index 3c0baf9a8..41743ae4b 100644 --- a/src/satip/rtsp.c +++ b/src/satip/rtsp.c @@ -1123,7 +1123,7 @@ rtsp_parse_cmd dmc->dmc_fe_freq = freq; dmc->dmc_fe_modulation = mtype; - dmc->dmc_fe_delsys = delsys; + dmc->dmc_fe_delsys = msys; rs->delsys = delsys; rs->frontend = fe;
Updated by Jeroen Hendriks about 7 years ago
Jaroslav Kysela wrote:
Could you test this simple change?
Did a quick complile without ffmpeg/libav (raspberry is slow) but now the channels on DVB-S2 transponders work just fine again.
Thanks 
Updated by Jaroslav Kysela about 7 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset commit:tvheadend|08c4069ba87194c22afe42320ca7cb8c4fbc9007.
Updated by g siviero about 7 years ago
Updated by I also confirm that all is working again with 4.3-333~g08c4069.
Thanks.