Beiträge von manxie

manxie · 6. April 2021

Diese Fernbedienung mit USB Empfänger hat ja das Problem, dass “nicht alle Tasten funktionieren”.

Sie funktionieren schon, werden aber nur als hid-events empfangen. Sie tauchen z.B. nicht bei evtest oder X auf.

Es gibt ein verwaistes Projekt auf GitHub (hid_mapper), das ich mit Patches auf Stand gebracht habe.

Es ist jetzt in Form eines arch-linux PKGBUILD bei GitHub verfügbar: https://github.com/fcringle/hid-mapper-pkg .

Durch diese neue Version funktionieren alle Tasten und können für VDR benutzt werden.

Auch power und sleep können von VDR ausgewertet werden.

Code

$ git clone https://github.com/fcringle/hid-mapper-pkg
$ cd hid-mapper-pkg/
$ makepkg -i

Hoffentlich ist es für nützlich. Ich habe die FB mit Empfänger bei Pollin für 2,50€ (+5,99 Versand - hmmm) gekauft.

Frank

manxie · 10. September 2015

I agree with hepi. I have been a happy eepg user for more than a year, watching (among others) the BBC HD channels.

Code

:BBC
BBC One HD;BSkyB:10847:vC23M5O35S1:S28.2E:23000:5400=27:5402=NAR@3;5401=eng@106:5403;5404=eng:0:6941:2:2050:0
BBC Two HD;BSkyB:10847:vC23M5O35S1:S28.2E:23000:5500=27:5502=NAR@3;5501=eng@106:5503;5504=eng:0:6940:2:2050:0
BBC One N West;BSkyB:10802:hC56M2O35S0:S28.2E:22000:5700=2:5701=eng@3:5703;5704=eng:0:6441:2:2047:0
BBC R4 FM;BSkyB:10788:vC56M2O35S0:S28.2E:22000:0:6002=eng@3:0:0:10381:2:2046:0
BBC Three HD;BSkyB:10847:VC23M5O25P0S1:S28.2E:23000:5600=27:5602=NAR@3;5601=eng@106:5603;5604=eng:0:6951:2:2050:0
BBC Four HD;BSkyB:11023:HC23M5O25P0S1:S28.2E:23000:5300=27:5302=NAR@3;5301=eng@106:5303;5304=eng:0:8931:2:2061:0
BBC NEWS HD;BSkyB:11023:hC23M5O35S1:S28.2E:23000:5000=27:0;5001=eng@106:5003;5004=eng:0:8921:2:2061:0
BBC Parliament;BSkyB:10788:vC56M2O35S0:S28.2E:22000:5100=2:5101=eng@3:5103;5104=eng:0:10307:2:2046:0
BBC World;BBC:11597:vC56M2O35S0:S19.2E:22000:163=2:92=eng@3:0:0:10050:1:1026:0

manxie · 1. September 2015

Yes. It is a while since I set it up. Presumably "epgscan set to 0" is EPGScanTimeout...

Code

vdr ~ # grep ^EPG /etc/vdr/setup.conf
EPGBugfixLevel = 3
EPGLanguages = eng
EPGLinger = 0
EPGScanTimeout = 0

I also have channels.conf sorted by sat position, except for a few channels at the beginning that I watch. And in fact those positions will usually be scanned by my satip tuner. So, 6am vdr wakes up, tunes to BBC R4, and the remaining tuners start scanning for epg data.

manxie · 1. September 2015

I use cron to trigger an EPG scan once a day...

Code

57   5  * * *  /usr/bin/svdrpsend "SCAN" >/dev/null

manxie · 9. Februar 2015

Hier eine kleine Korrektur eines Log-Messages...

Diff

diff --git a/softhddevice.cpp b/softhddevice.cpp
index b3467a5..92ebf8d 100644
--- a/softhddevice.cpp
+++ b/softhddevice.cpp
@@ -2288,7 +2288,7 @@ int64_t cSoftHdDevice::GetSTC(void)
 #if APIVERSNUM >= 20103
 void cSoftHdDevice::TrickSpeed(int speed, bool forward)
 {
-	dsyslog("[softhddev]%s: %d $d\n", __FUNCTION__, speed, forward);
+	dsyslog("[softhddev]%s: %d %d\n", __FUNCTION__, speed, forward);


 	::TrickSpeed(speed);
 }

Alles anzeigen

manxie · 29. Januar 2015

OK, here is a "works for me" patch. The idea is to create devices on demand, after discovery, and assign them a fixed type (sat/ter/cab). I have disabled the logic by which servers are removed and rediscovered. A server can check in but it can't check out.

I am an old C hacker with limited C++ competence (practically none), so if want to use this, feel free, but check it out carefully.

manxie · 24. Januar 2015

This thread appears to be dormant, but the problem still exists. At least for systems with directly connected dvbdevices and mixed satip dvb-s/dvb-t tuners. vdr overcommits the tuners, leading to "invalid status code 404". The system knows the number of tuners, but it doesn't keep track of their capabilities at the right time. The satip plugin returns 'true' from ProvidesSource indiscriminately. If devices were preassigned as dvb-s/dvb-t/dvb-c (on the basis of the number of each type in the server(s)), ProvidesSource could provide accurate information. As I understand it, the devices are initialized after discovery, so rather than creating 'deviceCount' general purpose devices, it should be possible to create a suitable number of each, marked with a 'tunerType' property (S|T|C), which would later be evaluated in ProvidesSource.

With this strategy the plugin parameters -d and -S would become redundant. The default would be to use every discovered device. The -s parameter can be used, as at present, to restrict certain server devices. The plugin should avoid creating "phantom" devices. If a server announces "DVBT2-2", that means 2 DVB-T2 devices, which may well be able to receive DVB-T also, but it is still only 2 devices, not 4. For cases such as OctopusNet terrestrial/cable cards, which announce "DVBT2-2,DVBC-2" for 2 tuners, the user must specify, in the -s parameter, what is connected to the 2 inputs.

manxie · 17. Januar 2015

Ok. Of course I would like to use mixed front-ends...

manxie · 17. Januar 2015

Excellent! Thank you very much.

Initial tests indicate that satip (1.0.2-GIT-d2064f0) works well with '--plugin=satip -d 2 -s 192.168.38.73|DVBS2-2|OctopusNet -S 1'. I assume that I have set the -S 1 parameter correctly?

manxie · 16. Januar 2015

Zitat

Thanks for your latest info. I'm now able to reproduce the problem on my system.

Great!

I hesitate to wish for another extension while you are still working on this topic, but it is somewhat related. Given a VDR system with SAT>IP server(s) receiving fixed sources, along with a directly connected dvb device with a H-to-H positioner, the current number of disabled sources is insufficient and inconvenient. It is not feasible to store 30 positions in satip.DisabledSources, even if the array size were extended (I assume that there is a limit on setup line length). So, for those with positioners, how about recognizing src=0 in sources.conf as disabling that position from satip, while leaving it available for other devices?

manxie · 15. Januar 2015

Zitat

Could you verify that you'll end up using 2 servers?

Code

Jan 15 11:11:45 vdr vdr[5203]: [5203] VDR version 2.1.6 started
Jan 15 11:11:45 vdr vdr[5203]: [5203] SATIP: Adding server '192.168.38.73|DVBS2-2|OctopusNet #0'
Jan 15 11:11:45 vdr vdr[5203]: [5203] SATIP: Adding server '192.168.38.73|DVBT2-2|OctopusNet #1'

For simplicity I have now removed the USB device, so only the Octopus sever is involved. Here is a test with channel 1 tuned, timers set for channel 7 and channel 100 (all satellite).

Code

fdc@vdr ~/src/satip-1.0.2 $ sh ~/set-timers
220 vdr SVDRP VideoDiskRecorder 2.1.6; Thu Jan 15 11:12:33 2015; UTF-8
900 SATIP tracing mode: 0x0100
221 vdr closing connection
220 vdr SVDRP VideoDiskRecorder 2.1.6; Thu Jan 15 11:12:34 2015; UTF-8
250 1 BBC One HD
221 vdr closing connection
220 vdr SVDRP VideoDiskRecorder 2.1.6; Thu Jan 15 11:12:35 2015; UTF-8
250 44 1:7:2015-01-15:1114:1122:50:99:Test1:
221 vdr closing connection
220 vdr SVDRP VideoDiskRecorder 2.1.6; Thu Jan 15 11:12:36 2015; UTF-8
250 45 1:100:2015-01-15:1114:1122:50:99:Test3:
221 vdr closing connection

Alles anzeigen

The attached trace extracted by

Code

fdc@vdr ~ $ journalctl --since=11:10 | grep -v 'CloseFilter\|SetPid\|vdpau\|video\|audio\|codec\|softhddev'

The exact same test with satip started with '--plugin=satip -d 2 -s 192.168.38.73|DVBS2-2|OctopusNet' succeeds. Channels 7 and 100 are recorded and live TV gets preempted to channel 100.

Code

fdc@vdr ~ $ journalctl --since=11:30 | grep 'VDR version 2.1.6 started\|Adding server\|switching'
Jan 15 11:42:38 vdr vdr[5592]: [5592] VDR version 2.1.6 started
Jan 15 11:42:38 vdr vdr[5592]: [5592] SATIP: Adding server '192.168.38.73|DVBS2-2|OctopusNet #0'
Jan 15 11:42:40 vdr vdr[5592]: [5592] switching to channel 4
Jan 15 11:44:12 vdr vdr[5592]: [5592] switching to channel 1
Jan 15 11:45:06 vdr vdr[5592]: [5592] switching device 4 to channel 7
Jan 15 11:45:17 vdr vdr[5592]: [5592] switching device 4 to channel 100
Jan 15 11:45:28 vdr vdr[5592]: [5592] switching device 4 to channel 7
Jan 15 11:45:39 vdr vdr[5592]: [5592] switching device 4 to channel 100
Jan 15 11:45:50 vdr vdr[5592]: [5592] switching device 4 to channel 7
Jan 15 11:46:00 vdr vdr[5592]: [5592] switching device 4 to channel 7
Jan 15 11:46:01 vdr vdr[5592]: [5592] switching device 3 to channel 100
Jan 15 11:46:02 vdr vdr[5592]: [5592] switching to channel 100

Alles anzeigen

manxie · 14. Januar 2015

Ah. I hadn't noticed the updated README.

My server claims

Code

<satip:X_SATIPCAP xmlns:satip="urn:ses-com:satip">DVBS2-2,DVBT2-2,DVBC-2</satip:X_SATIPCAP>

However, when I start vdr with "--plugin=satip -d 4 -s 192.168.38.73|DVBS2-2,DVBT2-2|OctopusNet", I still see the same bad behavior.

manxie · 14. Januar 2015

Thanks rofafor.

It still fails, I am afraid. The attached trace has this device configuration:

new device number 1
frontend 0/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV090x Multistandard")
new device number 4
SATIP: Creating device CardIndex=3 DeviceNumber=3 [device 0]
new device number 5
SATIP: Creating device CardIndex=4 DeviceNumber=4 [device 1]
new device number 6
SATIP: Creating device CardIndex=5 DeviceNumber=5 [device 2]
new device number 7
SATIP: Creating device CardIndex=6 DeviceNumber=6 [device 3]

The default channel is Sat-Radio 4. The Test sets live Sat-TV on channel 1 and
schedules recording of Sat channel 7, Terrestrial channel 501 and Sat channel 100 (which are all on different transponders). I imagine vdr/satip in this situation should leave live TV on the tuned satip device, schedule recordings on the other sat tuner and a terrestrial tuner, and let vdr use the low-priority directly connected frontend for the remaining recording.

I noticed a couple of minor bugs. When parsing satip.DisabledSources from the setup file, if more then one is disabled, only the first survives. It is subtle, because if you set 2 sources via osd it looks right initially and also after a restart. After the 2nd restart only one is still there. It is due to scribbling over the setup line, that vdr will write back on shutdown. There are a bunch of similar occurrences which may also cause problems (beware casts!). "fgrep -s '(char *)' *"

In cSatipServer::cSatipServer, when parsing modelM, you need to use "else if (strstr(r, "DVBT"))" etc., otherwise DVBT2 is counted twice (similarly DVBC2).

A cosmetic fix: s/GetHeaderLenght/GetHeaderLength/g

I still think it would be preferable, and indeed actually necessary, to let the user specify how many of which type of tuner to use. Something like '--plugin=satip --SatTuners=2 --TerrTuners=2". At the moment, even if the current method can be made to work, I don't see how to reserve a specific number of a specific type (i.e use fewer than are actually available).

manxie · 5. Januar 2015

Comparing the two traces in messages 11 and 13, it seems that the wrong decision is made in trace 1 starting at 'Jan 05 11:10:00'. That is when vdr starts to prepare for the recordings that will start a minute later. ProvidesTransponder and ProvidesSource claim to be able to provide 'transponder=210847 source=S' (which is BBC 1 HD via Satellite 28.2) on any of the 4 devices. Unfortunately, that is only going to work for the first two.

Given that the capabilities of the tuners are known to the plugin, maybe it's just a "small matter of programming" to extend it (hint).

manxie · 5. Januar 2015

Well, I am not familiar with the protocol.

Some info I forgot to provide with the previous trace, namely the timer settings:

Code

fdc@vdr ~ $ sh ~/set-timers
220 vdr SVDRP VideoDiskRecorder 2.1.6; Mon Jan  5 11:09:17 2015; UTF-8
250 48 1:1:2015-01-05:1111:1119:50:99:Test1:
221 vdr closing connection
220 vdr SVDRP VideoDiskRecorder 2.1.6; Mon Jan  5 11:09:18 2015; UTF-8
250 49 1:100:2015-01-05:1111:1119:50:99:Test2:
221 vdr closing connection
220 vdr SVDRP VideoDiskRecorder 2.1.6; Mon Jan  5 11:09:19 2015; UTF-8
250 50 1:200:2015-01-05:1111:1119:50:99:Test3:
221 vdr closing connection
220 vdr SVDRP VideoDiskRecorder 2.1.6; Mon Jan  5 11:09:20 2015; UTF-8
900 SATIP tracing mode: 0x0112
221 vdr closing connection
fdc@vdr ~ $ svdrpsend plug satip trac 0
220 vdr SVDRP VideoDiskRecorder 2.1.6; Mon Jan  5 11:12:41 2015; UTF-8
900 SATIP tracing mode: 0x0000
221 vdr closing connection

Alles anzeigen

Now I have done the same test, but with disabled DVB-T tuners, where everything works as planned.

Code

fdc@vdr ~ $ sh ~/set-timers
220 vdr SVDRP VideoDiskRecorder 2.1.6; Mon Jan  5 13:07:48 2015; UTF-8
250 48 1:1:2015-01-05:1309:1317:50:99:Test1:
221 vdr closing connection
220 vdr SVDRP VideoDiskRecorder 2.1.6; Mon Jan  5 13:07:49 2015; UTF-8
250 49 1:100:2015-01-05:1309:1317:50:99:Test2:
221 vdr closing connection
220 vdr SVDRP VideoDiskRecorder 2.1.6; Mon Jan  5 13:07:50 2015; UTF-8
250 50 1:200:2015-01-05:1309:1317:50:99:Test3:
221 vdr closing connection
220 vdr SVDRP VideoDiskRecorder 2.1.6; Mon Jan  5 13:07:51 2015; UTF-8
900 SATIP tracing mode: 0x0112
221 vdr closing connection
fdc@vdr ~ $ svdrpsend plug satip trac 0
220 vdr SVDRP VideoDiskRecorder 2.1.6; Mon Jan  5 13:11:01 2015; UTF-8
900 SATIP tracing mode: 0x0000
221 vdr closing connection

Alles anzeigen

And the good trace is attached.

manxie · 5. Januar 2015

I rebooted the OctopusNet (power down) got these results.

manxie · 4. Januar 2015

fnu

The requirements are ok.

Code

fdc@vdr ~ $ ldd /usr/lib64/vdr/plugins/libvdr-satip.so.2.1.6
	linux-vdso.so.1 (0x00007fff9c6de000)
	libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f3f2fda5000)
	libpugixml.so.1 => /usr/lib64/libpugixml.so.1 (0x00007f3f2fb72000)
	libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/libstdc++.so.6 (0x00007f3f2f86d000)
	libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/libgcc_s.so.1 (0x00007f3f2f657000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f3f2f2c2000)
	libssl.so.1.0.0 => /usr/lib64/libssl.so.1.0.0 (0x00007f3f2f056000)
	libcrypto.so.1.0.0 => /usr/lib64/libcrypto.so.1.0.0 (0x00007f3f2ec85000)
	libz.so.1 => /lib64/libz.so.1 (0x00007f3f2ea6f000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f3f2e853000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f3f2e552000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f3f3025c000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f3f2e34e000)

Alles anzeigen

Code

fdc@vdr ~ $ cave owner /usr/lib64/libcurl.so.4
net-misc/curl-7.39.0::installed
fdc@vdr ~ $ cave owner /usr/lib64/libpugixml.so.1
dev-libs/pugixml-1.5::installed

rofafor

I will reset the OctopusNet tomorrow and continue testing.

manxie · 4. Januar 2015

Zitat

Any info about the timers?

I generate 3 timers, for the 3 available sat tuners (2 on Octopus, 1 direct), with this script.

Bash

#!/bin/sh


DAY=`date --date='2 minutes' +%Y-%m-%d`
SOON=`date --date='2 minutes' +%H%M`
LATER=`date --date='10 minutes' +%H%M`


svdrpsend NEWT 1:1:$DAY:$SOON:$LATER:50:99:Test1
svdrpsend NEWT 1:100:$DAY:$SOON:$LATER:50:99:Test2
svdrpsend NEWT 1:200:$DAY:$SOON:$LATER:50:99:Test3

Alles anzeigen

Channel 1 is BBC 1 HD, 2 is ITV HD and 3 is Das Erste.

It works as expected with the terrestrials disabled, but chaos ensues with them enabled.

As in:

Code

Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::ProvidesSource(int) const (S) [device 3]
Jan 04 18:35:17 vdr vdr[15020]: [15020] switching device 7 to channel 1
Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::SetChannelDevice(const cChannel*, bool) (1, 0) [device 3]
Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::ProvidesTransponder(const cChannel*) const (100) transponder=211097 source=S [device 0]
Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::ProvidesSource(int) const (S) [device 0]
Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::ProvidesTransponder(const cChannel*) const (100) transponder=211097 source=S [device 1]
Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::ProvidesSource(int) const (S) [device 1]
Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::ProvidesTransponder(const cChannel*) const (100) transponder=211097 source=S [device 2]
Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::ProvidesSource(int) const (S) [device 2]
Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::ProvidesTransponder(const cChannel*) const (100) transponder=211097 source=S [device 3]
Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::ProvidesSource(int) const (S) [device 3]
Jan 04 18:35:17 vdr vdr[15020]: [15020] switching device 6 to channel 100
Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::SetChannelDevice(const cChannel*, bool) (100, 0) [device 2]
Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::ProvidesTransponder(const cChannel*) const (200) transponder=111493 source=S [device 0]
Jan 04 18:35:17 vdr vdr[15020]: [15020] SATIP9: virtual bool cSatipDevice::ProvidesSource(int) const (S) [device 0]
Jan 04 18:35:17 vdr vdr[15020]: [15066] SATIP-ERROR: Detected invalid status code 404: rtsp://192.168.38.73/ [device 3]
Jan 04 18:35:17 vdr vdr[15020]: [15066] SATIP-ERROR: Connect failed [device 3]
Jan 04 18:35:17 vdr vdr[15020]: [15063] SATIP-ERROR: Detected invalid status code 404: rtsp://192.168.38.73/ [device 2]
Jan 04 18:35:17 vdr vdr[15020]: [15063] SATIP-ERROR: Connect failed [device 2]
Jan 04 18:35:17 vdr vdr[15020]: [15059] SATIP9: virtual void cSatipDevice::CloseFilter(int) (275) [device 0]
Jan 04 18:35:17 vdr vdr[15020]: [15059] SATIP9: bool cSatipTuner::SetPid(int, int, bool) (275, 5, 0) pids=0,16,17,18,20,57,3842,6002 [device 0]
Jan 04 18:35:17 vdr vdr[15020]: [15059] SATIP9: virtual int cSatipDevice::OpenFilter(u_short, u_char, u_char) (276, 02, FF) [device 0]
Jan 04 18:35:17 vdr vdr[15020]: [15059] SATIP9: bool cSatipTuner::SetPid(int, int, bool) (276, 5, 1) pids=0,16,17,18,20,57,276,3842,6002 [device 0]
Jan 04 18:35:18 vdr vdr[15020]: [15062] SATIP9: virtual void cSatipDevice::CloseFilter(int) (5120) [device 1]
Jan 04 18:35:18 vdr vdr[15020]: [15062] SATIP9: bool cSatipTuner::SetPid(int, int, bool) (5120, 5, 0) pids=0,16,17,18,20 [device 1]
Jan 04 18:35:18 vdr vdr[15020]: [15062] SATIP9: virtual int cSatipDevice::OpenFilter(u_short, u_char, u_char) (5130, 02, FF) [device 1]
Jan 04 18:35:18 vdr vdr[15020]: [15062] SATIP9: bool cSatipTuner::SetPid(int, int, bool) (5130, 5, 1) pids=0,16,17,18,20,5130 [device 1]
Jan 04 18:35:18 vdr vdr[15020]: [15066] SATIP-ERROR: Detected invalid status code 404: rtsp://192.168.38.73/ [device 3]
Jan 04 18:35:18 vdr vdr[15020]: [15066] SATIP-ERROR: Connect failed [device 3]
Jan 04 18:35:18 vdr vdr[15020]: [15063] SATIP-ERROR: Detected invalid status code 404: rtsp://192.168.38.73/ [device 2]
Jan 04 18:35:18 vdr vdr[15020]: [15063] SATIP-ERROR: Connect failed [device 2]

Alles anzeigen

manxie · 4. Januar 2015

I'm not using radio id.

Situation before a recording:

Code

fdc@vdr ~/src/satip-1.0.0 $ svdrpsend plug satip stat
220 vdr SVDRP VideoDiskRecorder 2.1.6; Sun Jan  4 15:24:57 2015; UTF-8
900-Device: SAT>IP 0 192.168.38.73|DVBS2-2,DVBT2-2,DVBC-2|OctopusNet
900-CardIndex: 3  HasLock: yes  Strength: 74  Quality: 60  Live: yes
900-Transponder: 210788  Channel: BBC R4 FM
900-
900-Device: SAT>IP 1 192.168.38.73|DVBS2-2,DVBT2-2,DVBC-2|OctopusNet
900-CardIndex: 4  HasLock: no
900-Transponder: 210847  Channel: BBC One HD
900-
900-Device: SAT>IP 2 192.168.38.73|DVBS2-2,DVBT2-2,DVBC-2|OctopusNet
900-CardIndex: 5  HasLock: no
900-Transponder: 211097  Channel: ITV HD
900-
900-Device: SAT>IP 3 192.168.38.73|DVBS2-2,DVBT2-2,DVBC-2|OctopusNet
900-CardIndex: 6  HasLock: yes  Strength: 72  Quality: 66
900-Transponder: 211097  Channel: ITV HD
900
221 vdr closing connection

Alles anzeigen

and during the recording:

Code

fdc@vdr ~/src/satip-1.0.0 $ svdrpsend plug satip stat
220 vdr SVDRP VideoDiskRecorder 2.1.6; Sun Jan  4 15:18:54 2015; UTF-8
900-Device: SAT>IP 0 192.168.38.73|DVBS2-2,DVBT2-2,DVBC-2|OctopusNet
900-CardIndex: 3  HasLock: yes  Strength: 74  Quality: 60  Live: yes
900-Transponder: 210788  Channel: BBC R4 FM
900-
900-Device: SAT>IP 1 192.168.38.73|DVBS2-2,DVBT2-2,DVBC-2|OctopusNet
900-CardIndex: 4  HasLock: no
900-Transponder: 210847  Channel: BBC One HD
900-Recording: 1 timer
900-
900-Device: SAT>IP 2 192.168.38.73|DVBS2-2,DVBT2-2,DVBC-2|OctopusNet
900-CardIndex: 5  HasLock: no
900-Transponder: 211097  Channel: ITV HD
900-Recording: 1 timer
900-
900-Device: SAT>IP 3 192.168.38.73|DVBS2-2,DVBT2-2,DVBC-2|OctopusNet
900-CardIndex: 6  HasLock: yes  Strength: 72  Quality: 66
900-Transponder: 211097  Channel: ITV HD
900
221 vdr closing connection

Alles anzeigen

Just to clarify the device numbers:

Code

new device number 1
frontend 0/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV090x Multistandard")

Code

initializing plugin: softhddevice (0.6.1rc1-GIT9f134c1): A software and GPU emulated HD device
new device number 2

Code

initializing plugin: play (0.0.14-GIT8035264): A play plugin
new device number 3

Code

initializing plugin: satip (1.0.0): SAT>IP Devices
ERROR (thread.c,227): Permission denied
new device number 4
SATIP: Creating device CardIndex=3 DeviceNumber=3 [device 0]
SATIP#0 tuner thread started (pid=369, tid=406, prio=high)

Code

new device number 5
SATIP: Creating device CardIndex=4 DeviceNumber=4 [device 1]
SATIP#1 tuner thread started (pid=369, tid=409, prio=high)

Code

new device number 6
SATIP: Creating device CardIndex=5 DeviceNumber=5 [device 2]
SATIP#2 tuner thread started (pid=369, tid=412, prio=high)

Code

new device number 7
SATIP: Creating device CardIndex=6 DeviceNumber=6 [device 3]
SATIP#3 tuner thread started (pid=369, tid=415, prio=high)

And other random data:

Code

Linux version 3.18.1-gentoo (root@vdr) (gcc version 4.8.3 (Gentoo 4.8.3 p1.1, pie-0.5.9) ) #1 SMP Wed Dec 17 16:19:22 CET 2014

Code

VDR version 2.1.6 started

Code

OctopusNet 1.0.40 BETA

manxie · 4. Januar 2015

Many thanks to rofafor for the plugin!

I have an OctopusNet with two DVB-S/S2 tuners and two DVB-C/T/T2 tuners. The satellite signals come from twin LNBs and the terrestrial signals from a normal DVB-T antenna. And for added complexity there is a single LNB on a rotor feeding a USB tuner.

I give the OctopusNet high priority, so the rotor is only used when no other sat-tuner is available.

Unfortunately this configuration fails, in particular when programmed timers kick in. Clearly no more than 3 DVB-S and/or 2 DVB-T simultaneous recordings are possible, but I am seeing effects where even the second DVB-S recording get assigned to a DVB-T tuner, apparently.

So I have changed "--plugin=satip -d 4" to -d 2 and set satip.DisabledSources=T, thus disabling DVB-T reception. But it would be great to be able to use all of the tuners. I would be pleased to help with debugging and apologise if there is some configuration option that has escaped me.

Beiträge von manxie

Philips MCE USB Receiver: HID Treiber aufgefrischt

UK Freeview HD channel EPG data corrupted

VDR + USALS and EPG update

VDR + USALS and EPG update

softhddevice git 4f4d304 fehler

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T

[vdr-plugin-satip] Issues with mixed setup DVB-S & DVB-T