Hi all,
I'm trying to consolidate my stuff a bit and got a 4Sat these days. I'm trying
to run VDR-2.6.0 with the satip plugin connecting to the Satip device. 4
receivers, 2x S19.2E, 2x S13.0E. So far, the LNB ran on a DD Cine PCI-E card
just fine. (but I want to get rid of the server). (Tuner #4 is a Fritzbox
cable receiver).
Initially, all seems to look good:
Mar 29 15:20:55 seneca vdr: [4921] initializing plugin: satip (2.4.1): SAT>IP Geräte
Mar 29 15:20:55 seneca vdr: [4924] SATIP poller thread started (pid=4921, tid=4924, prio=high)
Mar 29 15:20:55 seneca vdr: [4921] cTimeMs: using monotonic clock (resolution is 1 ns)
Mar 29 15:20:55 seneca vdr: [4921] new device number 1 (card index 1)
Mar 29 15:20:55 seneca vdr: [4925] SATIP discover thread started (pid=4921, tid=4925, prio=high)
Mar 29 15:20:55 seneca vdr: [4921] SATIP: Creating device CardIndex=0 DeviceNumber=0 [device 0]
Mar 29 15:20:55 seneca vdr: [4927] SATIP#0 section handler thread started (pid=4921, tid=4927, prio=high)
Mar 29 15:20:55 seneca vdr: [4921] new device number 2 (card index 2)
Mar 29 15:20:55 seneca vdr: [4928] device 1 section handler thread started (pid=4921, tid=4928, prio=low)
Mar 29 15:20:55 seneca vdr: [4921] SATIP: Creating device CardIndex=1 DeviceNumber=1 [device 1]
Mar 29 15:20:55 seneca vdr: [4929] SATIP#1 tuner thread started (pid=4921, tid=4929, prio=high)
Mar 29 15:20:55 seneca vdr: [4930] SATIP#1 section handler thread started (pid=4921, tid=4930, prio=high)
Mar 29 15:20:55 seneca vdr: [4926] SATIP#0 tuner thread started (pid=4921, tid=4926, prio=high)
Mar 29 15:20:55 seneca vdr: [4931] device 2 section handler thread started (pid=4921, tid=4931, prio=low)
Mar 29 15:20:55 seneca vdr: [4921] new device number 3 (card index 3)
Mar 29 15:20:55 seneca vdr: [4921] SATIP: Creating device CardIndex=2 DeviceNumber=2 [device 2]
Mar 29 15:20:55 seneca vdr: [4932] SATIP#2 tuner thread started (pid=4921, tid=4932, prio=high)
Mar 29 15:20:55 seneca vdr: [4921] new device number 4 (card index 4)
Mar 29 15:20:55 seneca vdr: [4934] device 3 section handler thread started (pid=4921, tid=4934, prio=low)
Mar 29 15:20:55 seneca vdr: [4921] SATIP: Creating device CardIndex=3 DeviceNumber=3 [device 3]
Mar 29 15:20:55 seneca vdr: [4935] SATIP#3 tuner thread started (pid=4921, tid=4935, prio=high)
Mar 29 15:20:55 seneca vdr: [4936] SATIP#3 section handler thread started (pid=4921, tid=4936, prio=high)
Mar 29 15:20:55 seneca vdr: [4937] device 4 section handler thread started (pid=4921, tid=4937, prio=low)
Mar 29 15:20:55 seneca vdr: [4921] new device number 5 (card index 5)
Mar 29 15:20:55 seneca vdr: [4921] SATIP: Creating device CardIndex=4 DeviceNumber=4 [device 4]
Mar 29 15:20:55 seneca vdr: [4938] SATIP#4 tuner thread started (pid=4921, tid=4938, prio=high)
Mar 29 15:20:55 seneca vdr: [4939] SATIP#4 section handler thread started (pid=4921, tid=4939, prio=high)
...
Mar 29 15:20:56 seneca vdr: [4921] switching to channel 1 S19.2E-1-1107-17503 (WELT)
Mar 29 15:20:58 seneca vdr: [4957] device 1 receiver thread started (pid=4921, tid=4957, prio=high)
...
Mar 29 15:21:01 seneca vdr: [4928] creating new channel 'SAT.1,;ProSiebenSat.1' on S19.2E transponder 112544 with id 1-1107-17500-0
Mar 29 15:21:01 seneca vdr: [4928] creating new channel 'ProSieben,;ProSiebenSat.1' on S19.2E transponder 112544 with id 1-1107-17501-0
Mar 29 15:21:01 seneca vdr: [4928] creating new channel 'kabel eins,;ProSiebenSat.1' on S19.2E transponder 112544 with id 1-1107-17502-0
Mar 29 15:21:01 seneca vdr: [4928] creating new channel 'SAT.1 Gold,;ProSiebenSat.1' on S19.2E transponder 112544 with id 1-1107-17504-0
... (plus a handful more)
but a minute later,
Mar 29 15:21:59 seneca vdr: [4929] curl_easy_perform() [rtsp.c,369] failed: Timeout was reached (28)
Mar 29 15:21:59 seneca vdr: [4929] SATIP-ERROR: Detected invalid status code 0: rtsp://192.168.20.7/ [device 1]
Mar 29 15:21:59 seneca vdr: [4929] SATIP-ERROR: Pid update failed - retuning [device 1]
Mar 29 15:21:59 seneca vdr: [4932] curl_easy_perform() [rtsp.c,340] failed: Timeout was reached (28)
Mar 29 15:21:59 seneca vdr: [4932] SATIP-ERROR: Detected invalid status code 0: rtsp://192.168.20.7/ [device 2]
Mar 29 15:21:59 seneca vdr: [4935] curl_easy_perform() [rtsp.c,244] failed: Timeout was reached (28)
Mar 29 15:21:59 seneca vdr: [4935] SATIP-ERROR: Detected invalid status code 0: rtsp://192.168.20.7/ [device 3]
Mar 29 15:21:59 seneca vdr: [4935] SATIP-ERROR: Connect failed [device 3]
... and
Mar 29 15:22:03 seneca vdr: [4935] SATIP-ERROR: Detected invalid status code 503: rtsp://192.168.20.7/ [device 3]
Mar 29 15:22:03 seneca vdr: [4935] SATIP-ERROR: Connect failed [device 3]
Mar 29 15:22:04 seneca vdr: [4929] SATIP-ERROR: Detected invalid status code 503: rtsp://192.168.20.7/ [device 1]
Mar 29 15:22:04 seneca vdr: [4929] SATIP-ERROR: Connect failed [device 1]
etc. etc. endlessly, and with netstat I see a lot of attempted rtsp connects:
tcp 0 0 192.168.20.1:42764 192.168.20.7:554 ESTABLISHED 5219/vdr
tcp 0 0 192.168.20.1:53584 192.168.20.7:554 TIME_WAIT -
What might be wrong? Any experience that you can share? Should I return this
device because it is known not to work with the satip plugin? (Not that I
didn't google this before, to no avail.)
I would have preferred an Octopus Net S2, but these devices were withdrawn and
are hard to find.
TIA!
Cheers,
hm
--
We should be careful to get out of an experience only the wisdom that is
in it - and stay there, lest we be like the cat that sits down on a hot
stove-lid. She will never sit down on a hot stove-lid again - and that
is well; but also she will never sit down on a cold one any more.
-- Mark Twain
