You are not logged in.

CI-Unterstützung für CineS2, Mystique SaTiX-S2 Dual usw.

Dear visitor, welcome to VDR Portal. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

D0nR0s4

Beginner

Posts: 4

  • Send private message

141

Saturday, January 7th 2012, 5:38pm

Blöde Frage, ich weiß, aber hast du irgendwas neues in Erfahrung bringen können?
Kann ich noch irgendwie helfen? Irgendwelche log Dateien die dir helfen würden? Ich hab kein Problem damit, vdr oder dein plugin selbst zu kompilieren um irgendeine Debug Option anzuschalten, nur hab ich leider selber keinerlei Ahnung, was dir helfen würde.

chris281080

Trainee

Posts: 105

Location: Wien / Österreich

Occupation: iT-Techniker

  • Send private message

142

Sunday, January 8th 2012, 5:34pm

Da ich den VDR bisher immer selbst kompiliert habe, hab ich mir mal folgendes runtergeladen:
vdr-1.7.22
vdr-plugin-ddci

Der Patch angewendet und das kompellieren hat soweit geklappt.

Das ganze vdr-pluggin-ddvi Verzeichniss hab ich ins PLUGINS/src verzeichniss kopiert und als ddci verlinkt.


Jedoch beim "make plugin" erhalte ich folgende Rückmeldung:
Plugin ddci:
make[1]: Betrete Verzeichnis '/usr/local/src/vdr-1.7.22/PLUGINS/src/vdr-plugin-ddci'
make[1]: Verlasse Verzeichnis '/usr/local/src/vdr-1.7.22/PLUGINS/src/vdr-plugin-ddci'
make[1]: Betrete Verzeichnis '/usr/local/src/vdr-1.7.22/PLUGINS/src/vdr-plugin-ddci'
g++ -g -O3 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"ddci"' -I../../../include ddci.c
g++ -g -O3 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"ddci"' -I../../../include dddvbci.c
dddvbci.c:3:21: schwerwiegender Fehler: libudev.h: Datei oder Verzeichnis nicht gefunden
Kompilierung beendet.
make[1]: *** [dddvbci.o] Fehler 1
make[1]: Verlasse Verzeichnis '/usr/local/src/vdr-1.7.22/PLUGINS/src/vdr-plugin-ddci'

Ich versuch gerade herauszufinden, wie ich an diese libudev.h gelange, hast du vielleicht Tipps?

Lg,
Christoph
Server: GoFlex Net - PCTV 460e (S2), PCTV 290e (T2) - OCZ Vertex 2 & RAID5 mit 3TB netto
Client: Zotac NVIDIA ION - yaVDR (HDMI an Onkyo TX-SR705, Mitsubishi HC-6800)

calime

Beginner

Posts: 5

  • Send private message

143

Sunday, January 8th 2012, 6:00pm

Thirst : sory to answer in english , but my german is too bad . I only manage to follow your post with google translation

I have compile a new vdr 1.7.22 with plugin ddci and have had the same problème .
try to install package libudev-dev and you 'll have no problème with "make plugin"

anyway , menu CAM is present in VDR menu, and my CI is well recognize "Aston Module 2.2500" channel are not decrypt . I can only sea free channel.
My knowledge is not big enouth in linux and encrypt channel , to find the solution , so I will continue to read this topic with hope , and help when I can .

good luck

calime

chris281080

Trainee

Posts: 105

Location: Wien / Österreich

Occupation: iT-Techniker

  • Send private message

144

Sunday, January 8th 2012, 6:50pm

Thx for the tipp with "libudev-dev", everythings compiles correctly.

Anything special to log?
Or any hints how to activate the necessary debug level?
Server: GoFlex Net - PCTV 460e (S2), PCTV 290e (T2) - OCZ Vertex 2 & RAID5 mit 3TB netto
Client: Zotac NVIDIA ION - yaVDR (HDMI an Onkyo TX-SR705, Mitsubishi HC-6800)

mini73

Moderator

Posts: 2,988

Location: Flensburg

  • Send private message

145

Sunday, January 8th 2012, 8:25pm

Hi,

If you look at ci.c in the vdr-source you'll find some "debug-enable" options:

Source code

 
1
2
3
4

static bool DumpTPDUDataTransfer = false;
static bool DebugProtocol = false;
static bool DumpPolls = false;
static bool DumpDateTime = false;

vdr will output some informationen on stdout (DumpPolls will be very verbose).

Didn't have any time last week to dig deeper into the "non decrypting" problem.

Lars.

meine Signatur

vdr2: yaVDR 0.5/softhddevice @ G540, Intel DH67BLB3, Asus GT610/2GB, DDBridge + 2x DuoFlex C/T
vdr: yaVDR 0.2/pvr350 @ Sempron 64 LE-1200, MSI K9MM-V, 1x PVR350, 2x Satelco EasyWatch DVB-C
hdvdr: yaVDR unstable/softhddevice @ E8400, Asus P5Q SE Plus, 1x L4M-TwinCI + Flex C/T, 1x Sundtek MediaTV Pro, GT520
Plugins: | avahi4vdr | dbus2vdr | dynamite | noepg | pvrinput | sundtek |
pre-alpha Plugins: | ddci CI-Support für DD/L4M (siehe Post 1048374) |

calime

Beginner

Posts: 5

  • Send private message

146

Sunday, January 8th 2012, 8:53pm

here an extract of syslog. ok on a free to air channel (49) and nothing on an encrypt channel

Source code

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208

 Jan  8 20:31:36 vdrbox vdr: [2185] VDR version 1.7.22 started
Jan  8 20:31:36 vdrbox vdr: [2185] codeset is 'UTF-8' - known
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR (tools.c,1380): ./locale: Aucun fichier ou dossier de ce type
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'deu,ger'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'slv,slo'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'ita'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'dut,nla,nld'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'prt'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'fra,fre'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'nor'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'fin,suo'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'pol'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'esl,spa'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'ell,gre'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'sve,swe'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'rom,rum'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'hun'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'cat,cln'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'rus'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'srb,srp,scr,scc'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'hrv'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'est'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'dan'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'cze,ces'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'tur'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'ukr'
Jan  8 20:31:36 vdrbox vdr: [2185] no locale for language code 'ara'
Jan  8 20:31:36 vdrbox vdr: [2185] loading plugin: /usr/local/lib/vdr/libvdr-pluginsetup.so.1.7.22
Jan  8 20:31:36 vdrbox vdr: [2185] loading plugin: /usr/local/lib/vdr/libvdr-xineliboutput.so.1.7.22
Jan  8 20:31:36 vdrbox vdr: [2185] loading plugin: /usr/local/lib/vdr/libvdr-ddci.so.1.7.22
Jan  8 20:31:36 vdrbox vdr: [2185] loading /video/vdrconf/setup.conf
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: ChannelBindingByRid = 1
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: DisableVPS = 0
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: DoubleEpgAction = 1
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: DoubleEpgTimeDelta = 15
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: HardLinkCutter = 0
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: JumpPlay = 0
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: JumpSeconds = 60
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: JumpSecondsRepeat = 300
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: JumpSecondsSlow = 10
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: LocalChannelProvide = 1
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: LRChannelGroups = 1
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: LRForwardRewind = 1
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: LRVolumeControl = 0
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: MaxRecordingSize = 100
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: MenuCmdPosition = 0
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: MixEpgAction = 0
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: PauseLastMark = 0
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: PlayJump = 0
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: ReloadMarks = 0
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: ShowProgressBar = 0
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: ShowRecDate = 1
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: ShowRecLength = 1
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: ShowRecTime = 1
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: ShowValidInput = 0
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: SupportTeletext = 0
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown config parameter: WarEagleIcons = 1
Jan  8 20:31:36 vdrbox vdr: [2185] [xine..put] Skipping configuration entry Frontend=none (overridden in command line)
Jan  8 20:31:36 vdrbox vdr: [2185] [xine..put] Skipping configuration entry Remote.ListenPort=37890 (overridden in command line)
Jan  8 20:31:36 vdrbox vdr: [2185] [xine..put] Skipping configuration entry RemoteMode=1 (overridden in command line)
Jan  8 20:31:36 vdrbox vdr: [2185] loading /video/vdrconf/sources.conf
Jan  8 20:31:36 vdrbox vdr: [2185] loading /video/vdrconf/diseqc.conf
Jan  8 20:31:36 vdrbox vdr: [2185] loading /video/vdrconf/channels.conf
Jan  8 20:31:36 vdrbox vdr: [2185] loading /video/vdrconf/timers.conf
Jan  8 20:31:36 vdrbox vdr: [2185] loading /video/vdrconf/commands.conf
Jan  8 20:31:36 vdrbox vdr: [2185] loading /video/vdrconf/reccmds.conf
Jan  8 20:31:36 vdrbox vdr: [2185] loading /video/vdrconf/svdrphosts.conf
Jan  8 20:31:36 vdrbox vdr: [2185] loading /video/vdrconf/remote.conf
Jan  8 20:31:36 vdrbox vdr: [2185] loading /video/vdrconf/keymacros.conf
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown plugin 'weatherng'
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: empty key macro
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: unknown plugin 'mplayer'
Jan  8 20:31:36 vdrbox vdr: [2185] ERROR: empty key macro
Jan  8 20:31:36 vdrbox vdr: [2186] video directory scanner thread started (pid=2185, tid=2186)
Jan  8 20:31:36 vdrbox vdr: [2187] video directory scanner thread started (pid=2185, tid=2187)
Jan  8 20:31:36 vdrbox vdr: [2185] reading EPG data from /video/records/epg.data
Jan  8 20:31:36 vdrbox vdr: [2187] video directory scanner thread ended (pid=2185, tid=2187)
Jan  8 20:31:36 vdrbox vdr: [2186] video directory scanner thread ended (pid=2185, tid=2186)
Jan  8 20:31:36 vdrbox vdr: [2185] registered source parameters for 'A - ATSC'
Jan  8 20:31:36 vdrbox vdr: [2185] registered source parameters for 'C - DVB-C'
Jan  8 20:31:36 vdrbox vdr: [2185] registered source parameters for 'S - DVB-S'
Jan  8 20:31:36 vdrbox vdr: [2185] registered source parameters for 'T - DVB-T'
Jan  8 20:31:36 vdrbox vdr: [2185] probing /dev/dvb/adapter0/frontend0
Jan  8 20:31:36 vdrbox vdr: [2185] creating cDvbDevice
Jan  8 20:31:36 vdrbox vdr: [2185] new device number 1
Jan  8 20:31:36 vdrbox vdr: [2185] ddci: found /dev/dvb/adapter2/ca0
Jan  8 20:31:36 vdrbox vdr: [2185] ddci: with 1 cam slot
Jan  8 20:31:36 vdrbox vdr: [2185] cTimeMs: using monotonic clock (resolution is 1 ns)
Jan  8 20:31:36 vdrbox kernel: [   82.994410] slot_shutdown
Jan  8 20:31:36 vdrbox vdr: [2189] CI adapter on device 0 thread started (pid=2185, tid=2189)
Jan  8 20:31:36 vdrbox vdr: [2189] CAM 1: module present
Jan  8 20:31:36 vdrbox vdr: [2185] frontend 0/0 provides DVB-S2 with QPSK ("STV090x Multistandard")
Jan  8 20:31:36 vdrbox vdr: [2190] tuner on frontend 0/0 thread started (pid=2185, tid=2190)
Jan  8 20:31:36 vdrbox vdr: [2191] section handler thread started (pid=2185, tid=2191)
Jan  8 20:31:36 vdrbox vdr: [2185] probing /dev/dvb/adapter1/frontend0
Jan  8 20:31:36 vdrbox vdr: [2185] creating cDvbDevice
Jan  8 20:31:36 vdrbox vdr: [2185] new device number 2
Jan  8 20:31:37 vdrbox vdr: [2185] frontend 1/0 provides DVB-S2 with QPSK ("STV090x Multistandard")
Jan  8 20:31:37 vdrbox vdr: [2193] tuner on frontend 1/0 thread started (pid=2185, tid=2193)
Jan  8 20:31:37 vdrbox vdr: [2194] section handler thread started (pid=2185, tid=2194)
Jan  8 20:31:37 vdrbox vdr: [2185] found 2 DVB devices
Jan  8 20:31:37 vdrbox vdr: [2185] initializing plugin: pluginsetup (0.0.6): Plugin Setup
Jan  8 20:31:37 vdrbox vdr: [2185] initializing plugin: xineliboutput (1.0.90-cvs): X11/xine-lib output plugin
Jan  8 20:31:37 vdrbox vdr: [2185] new device number 9
Jan  8 20:31:37 vdrbox vdr: [2185] [xine..put] cTimePts: clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us
Jan  8 20:31:37 vdrbox vdr: [2185] [xine..put] cTimePts: using monotonic clock
Jan  8 20:31:37 vdrbox vdr: [2185] [xine..put] RTP SSRC: 0x68ff2663
Jan  8 20:31:37 vdrbox vdr: [2195] [xine..put] Have CAP_SYS_NICE capability
Jan  8 20:31:37 vdrbox vdr: [2185] initializing plugin: ddci (0.0.1a): external ci-adapter
Jan  8 20:31:37 vdrbox vdr: [2185] setting primary device to 3
Jan  8 20:31:37 vdrbox vdr: [2185] assuming manual start of VDR
Jan  8 20:31:37 vdrbox vdr: [2185] SVDRP listening on port 6419
Jan  8 20:31:37 vdrbox vdr: [2185] setting current skin to "classic"
Jan  8 20:31:37 vdrbox vdr: [2185] loading /video/vdrconf/themes/classic-default.theme
Jan  8 20:31:37 vdrbox vdr: [2185] starting plugin: pluginsetup
Jan  8 20:31:37 vdrbox vdr: [2185] starting plugin: xineliboutput
Jan  8 20:31:37 vdrbox vdr: [2196] Remote decoder/display server (cXinelibServer) thread started (pid=2185, tid=2196)
Jan  8 20:31:37 vdrbox vdr: [2196] [xine..put] Have CAP_SYS_NICE capability
Jan  8 20:31:37 vdrbox vdr: [2196] [xine..put] cXinelibServer priority set successful SCHED_RR 2 [1,99]
Jan  8 20:31:37 vdrbox vdr: [2196] [xine..put] Listening on port 37890
Jan  8 20:31:37 vdrbox vdr: [2196] [xine..put] Listening for UDP broadcasts on port 37890
Jan  8 20:31:37 vdrbox vdr: [2196] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0#015#012Server port: 37890#015#012Server version: xineliboutput-1.0.90-cvs#015#012#015
Jan  8 20:31:37 vdrbox vdr: [2185] [xine..put] cXinelibDevice::StartDevice(): Device started
Jan  8 20:31:37 vdrbox vdr: [2185] starting plugin: ddci
Jan  8 20:31:37 vdrbox vdr: [2185] remote control KBD - keys known
Jan  8 20:31:37 vdrbox vdr: [2197] KBD remote control thread started (pid=2185, tid=2197)
Jan  8 20:31:39 vdrbox kernel: [   85.269498] dvb_ca adapter 2: DVB CAM detected and initialised successfully
Jan  8 20:31:39 vdrbox vdr: [2189] CAM 1: module ready
Jan  8 20:31:41 vdrbox vdr: [2196] [discovery] Received valid discovery message VDR xineliboutput DISCOVERY 1.0#015#012Client: 255.255.255.255:37890#015#012#015
Jan  8 20:31:41 vdrbox vdr: [2196] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0#015#012Server port: 37890#015#012Server version: xineliboutput-1.0.90-cvs#015#012#015
Jan  8 20:31:43 vdrbox vdr: [2196] [xine..put] Client 0 connected: 192.168.0.20:51242
Jan  8 20:31:43 vdrbox vdr: [2196] loading /video/vdrconf/plugins/xineliboutput/allowed_hosts.conf
Jan  8 20:31:43 vdrbox vdr: [2196] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes
Jan  8 20:31:43 vdrbox vdr: [2196] [xine..put] Trying PIPE connection ...
Jan  8 20:31:43 vdrbox vdr: [2196] creating directory /video/vdrconf/plugins/xineliboutput/pipes.2185
Jan  8 20:31:43 vdrbox vdr: [2196] removing /video/vdrconf/plugins/xineliboutput/pipes.2185
Jan  8 20:31:43 vdrbox vdr: [2196] [xine..put] cBackgroundWriterI initialized (buffer 512 kb)
Jan  8 20:31:43 vdrbox vdr: [2196] [xine..put] cTcpWriter initialized (buffer 512 kb)
Jan  8 20:31:43 vdrbox vdr: [2196] [xine..put] Pipe open
Jan  8 20:31:47 vdrbox vdr: [2189] CAM 1: Aston Module 2.2500, 01, 0100, 0100
Jan  8 20:31:51 vdrbox vdr: [2189] CAM 1: doesn't reply to QUERY - only a single channel can be decrypted
Jan  8 20:31:51 vdrbox vdr: [2185] switching to channel 49
Jan  8 20:31:51 vdrbox vdr: [2219] receiver on device 2 thread started (pid=2185, tid=2219)
Jan  8 20:31:51 vdrbox vdr: [2220] TS buffer on device 2 thread started (pid=2185, tid=2220)
Jan  8 20:31:52 vdrbox vdr: [2185] OSD size changed to 720x576 @ 1.42222
Jan  8 20:31:52 vdrbox vdr: [2185] timer 1 (49 1856-2156 '@VU DU CIEL-S04-EP004-SENEGAL') set to event Sun 08.01.2012 20:30-20:56 'JOURNAL DE FRANCE 2-08/01/12'
Jan  8 20:31:52 vdrbox vdr: [2185] switching device 2 to channel 49
Jan  8 20:31:52 vdrbox vdr: [2185] timer 1 (49 1856-2156 '@VU DU CIEL-S04-EP004-SENEGAL') start
Jan  8 20:31:52 vdrbox vdr: [2185] Title: 'JOURNAL DE FRANCE 2-08/01/12' Subtitle: '(null)'
Jan  8 20:31:52 vdrbox vdr: [2185] record /video/records/@VU_DU_CIEL-S04-EP004-SENEGAL/2012-01-08.18.56.49-0.rec
Jan  8 20:31:52 vdrbox vdr: [2185] recording to '/video/records/@VU_DU_CIEL-S04-EP004-SENEGAL/2012-01-08.18.56.49-0.rec/00005.ts'
Jan  8 20:31:52 vdrbox vdr: [2221] recording thread started (pid=2185, tid=2221)
Jan  8 20:31:52 vdrbox vdr: [2219] [xine..put] Detected video size 720x576
Jan  8 20:31:53 vdrbox vdr: [2194] changing pids of channel 173 from 0+0=0:0:0:0 to 0+0=0:0:0:0
Jan  8 20:31:53 vdrbox vdr: [2194] channel 49 (TV5MONDE EUROPE) event Sun 08.01.2012 20:30-20:56 'JOURNAL DE FRANCE 2-08/01/12' status 4
Jan  8 20:31:57 vdrbox vdr: [2185] timer 1 (49 1856-2156 '@VU DU CIEL-S04-EP004-SENEGAL') set to event Sun 08.01.2012 18:59-19:45 'VU DU CIEL-S04-EP004-SENEGAL'
Jan  8 20:32:27 vdrbox vdr: [2185] switching to channel 3
Jan  8 20:32:27 vdrbox vdr: [2185] CAM 1: assigned to device 1
Jan  8 20:32:27 vdrbox vdr: [2223] receiver on device 1 thread started (pid=2185, tid=2223)
Jan  8 20:32:28 vdrbox vdr: [2224] TS transfer buffer on device 1 thread started (pid=2185, tid=2224)
Jan  8 20:32:28 vdrbox vdr: [2225] TS buffer on device 1 thread started (pid=2185, tid=2225)
Jan  8 20:32:28 vdrbox vdr: [2226] TS transfer on device 1 thread started (pid=2185, tid=2226)
Jan  8 20:32:37 vdrbox vdr: [2190] frontend 0/0 timed out while tuning to channel 3, tp 211817
Jan  8 20:32:39 vdrbox kernel: [  145.692517] slot_shutdown
Jan  8 20:32:39 vdrbox vdr: [2189] CAM 1: module present
Jan  8 20:32:39 vdrbox vdr: [2224] buffer usage: 90% (tid=2223)
Jan  8 20:32:39 vdrbox vdr: [2223] ERROR: skipped 4 bytes to sync on TS packet on device 1
Jan  8 20:32:39 vdrbox vdr: [2224] buffer usage: 60% (tid=2223)
Jan  8 20:32:39 vdrbox vdr: [2223] ERROR: skipped 176 bytes to sync on TS packet on device 1
Jan  8 20:32:39 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:40 vdrbox vdr: [2224] buffer usage: 60% (tid=2223)
Jan  8 20:32:40 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:40 vdrbox vdr: [2224] buffer usage: 60% (tid=2223)
Jan  8 20:32:40 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:40 vdrbox vdr: [2224] buffer usage: 60% (tid=2223)
Jan  8 20:32:40 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:40 vdrbox vdr: [2224] buffer usage: 50% (tid=2223)
Jan  8 20:32:40 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:41 vdrbox vdr: [2224] buffer usage: 50% (tid=2223)
Jan  8 20:32:41 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:41 vdrbox vdr: [2224] buffer usage: 50% (tid=2223)
Jan  8 20:32:41 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:41 vdrbox vdr: [2224] buffer usage: 50% (tid=2223)
Jan  8 20:32:41 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:41 vdrbox kernel: [  147.993725] dvb_ca adapter 2: DVB CAM detected and initialised successfully
Jan  8 20:32:41 vdrbox vdr: [2224] buffer usage: 50% (tid=2223)
Jan  8 20:32:41 vdrbox vdr: [2223] ERROR: skipped 4 bytes to sync on TS packet on device 1
Jan  8 20:32:42 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:42 vdrbox vdr: [2224] buffer usage: 50% (tid=2223)
Jan  8 20:32:42 vdrbox vdr: [2189] CAM 1: module ready
Jan  8 20:32:42 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:42 vdrbox vdr: [2224] buffer usage: 50% (tid=2223)
Jan  8 20:32:42 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:42 vdrbox vdr: [2224] buffer usage: 40% (tid=2223)
Jan  8 20:32:42 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:42 vdrbox vdr: [2224] buffer usage: 40% (tid=2223)
Jan  8 20:32:43 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:43 vdrbox vdr: [2224] buffer usage: 30% (tid=2223)
Jan  8 20:32:43 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:43 vdrbox vdr: [2224] buffer usage: 30% (tid=2223)
Jan  8 20:32:43 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:43 vdrbox vdr: [2224] buffer usage: 30% (tid=2223)
Jan  8 20:32:43 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:44 vdrbox vdr: [2224] buffer usage: 30% (tid=2223)
Jan  8 20:32:44 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:44 vdrbox vdr: [2224] buffer usage: 30% (tid=2223)
Jan  8 20:32:44 vdrbox vdr: [2224] buffer usage: 100% (tid=2223)
Jan  8 20:32:44 vdrbox vdr: [2224] buffer usage: 30% (tid=2223)

Quoted

chris281080

Trainee

Posts: 105

Location: Wien / Österreich

Occupation: iT-Techniker

  • Send private message

147

Monday, January 9th 2012, 6:27pm

Hi,

Also some input from my side.

Test System:
Hardware & Softwarebase as in my Signature.
VDR specific Software:
plain vdr-1.7.22 patched with Patch from ddci Plugin
Plugins: ddci, xineliboutput

Command to run the VDR:
sudo ./vdr -w 60 --no-kbd --lirc -L /usr/local/src/vdr-1.7.22/PLUGINS/lib/ -c /etc/vdr_tst/ -E /etc/vdr_tst/epg.data -P xineliboutput -P ddci >~/vdr.log_smartcard_in_DD 2>&1

Captured Logs:
vdr.log_smartcard_in_TT
SmartCard and AlphaCrypt Modul was in my Technotrend Card, decryption already works under vanila VDR.
Decoding worked without problems under the test system.

vdr.log_smartcard_in_DD
SmartCard and AlphaCrypt Modul was in my DD Card
Decoding didnt work under the test system.
After about a minute i entered "Setup" / "CAM" and reseted it. (CAM was showen correctly)
After about another minute without picture, i went back to "Setup" / "CAM" and entered the CAM Menu, which worked well.

Hope the logs help.
Please inform me if I can log/test something else.

Just have seen that only some CI specific output was captured. If the other output is also necessary just leave a short note.
chris281080 has attached the following files:
Server: GoFlex Net - PCTV 460e (S2), PCTV 290e (T2) - OCZ Vertex 2 & RAID5 mit 3TB netto
Client: Zotac NVIDIA ION - yaVDR (HDMI an Onkyo TX-SR705, Mitsubishi HC-6800)

This post has been edited 1 times, last edit by "chris281080" (Jan 9th 2012, 6:42pm)

calime

Beginner

Posts: 5

  • Send private message

148

Friday, January 13th 2012, 9:42pm

hello chris281080
how do you generate your file vdr.log....
I want to do some test myself but don't know how to do ?

chris281080

Trainee

Posts: 105

Location: Wien / Österreich

Occupation: iT-Techniker

  • Send private message

149

Saturday, January 14th 2012, 10:34am

Hi,

I just activated the debuging for ci.c as told:
Replace all here listed "false" with "true" and then compile the VDR with "make".
If it was already compiled before, use "make clean" before you "make" again.

Quoted from "mini73"

Hi,

If you look at ci.c in the vdr-source you'll find some "debug-enable" options:

Source code

 
1
2
3
4

static bool DumpTPDUDataTransfer = false;
static bool DebugProtocol = false;
static bool DumpPolls = false;
static bool DumpDateTime = false;

vdr will output some informationen on stdout (DumpPolls will be very verbose).

Didn't have any time last week to dig deeper into the "non decrypting" problem.

Lars.
Command to start the VDR:
sudo ./vdr -w 60 --no-kbd --lirc -L /usr/local/src/vdr-1.7.22/PLUGINS/lib/ -c /etc/vdr_tst/ -E /etc/vdr_tst/epg.data -P xineliboutput -P ddci >~/vdr.log_smartcard_in_DD 2>&1

You have to adapt the Pugins and directorys for your system.

I think something in the redirection into a file works wrong, as there is no Standard VDR Input in the file.
Server: GoFlex Net - PCTV 460e (S2), PCTV 290e (T2) - OCZ Vertex 2 & RAID5 mit 3TB netto
Client: Zotac NVIDIA ION - yaVDR (HDMI an Onkyo TX-SR705, Mitsubishi HC-6800)

mini73

Moderator

Posts: 2,988

Location: Flensburg

  • Send private message

150

Wednesday, January 18th 2012, 7:36pm

Moin!

Made some tests today: the plugin writes scrambled packets to sec0 but doesn't read anything. Seems like they get "stuck" in the sec-device.
The communication with the cam seems to work... as I can say from my and your logs.

Anyone an idea how to debug/log this?
Has the ci-driver any debugging options?

Lars.

meine Signatur

vdr2: yaVDR 0.5/softhddevice @ G540, Intel DH67BLB3, Asus GT610/2GB, DDBridge + 2x DuoFlex C/T
vdr: yaVDR 0.2/pvr350 @ Sempron 64 LE-1200, MSI K9MM-V, 1x PVR350, 2x Satelco EasyWatch DVB-C
hdvdr: yaVDR unstable/softhddevice @ E8400, Asus P5Q SE Plus, 1x L4M-TwinCI + Flex C/T, 1x Sundtek MediaTV Pro, GT520
Plugins: | avahi4vdr | dbus2vdr | dynamite | noepg | pvrinput | sundtek |
pre-alpha Plugins: | ddci CI-Support für DD/L4M (siehe Post 1048374) |

mini73

Moderator

Posts: 2,988

Location: Flensburg

  • Send private message

151

Wednesday, January 18th 2012, 10:02pm

Moin!

I get sometimes

Source code

 
1
2
3
4
5

[15716.116014] dvb_ca adapter 3: DVB CAM detected and initialised successfully
[15726.556514] IA 4 0 00000007
[15794.172298] IA 5 0 00000007
[15797.724331] IA 5 0 00000007
[15816.096372] IA 5 0 00000007

those "IA" messages. Don't know if they're crucial...

Hm, cxd2099 doesn't have to have any options for debugging.

Lars.

meine Signatur

vdr2: yaVDR 0.5/softhddevice @ G540, Intel DH67BLB3, Asus GT610/2GB, DDBridge + 2x DuoFlex C/T
vdr: yaVDR 0.2/pvr350 @ Sempron 64 LE-1200, MSI K9MM-V, 1x PVR350, 2x Satelco EasyWatch DVB-C
hdvdr: yaVDR unstable/softhddevice @ E8400, Asus P5Q SE Plus, 1x L4M-TwinCI + Flex C/T, 1x Sundtek MediaTV Pro, GT520
Plugins: | avahi4vdr | dbus2vdr | dynamite | noepg | pvrinput | sundtek |
pre-alpha Plugins: | ddci CI-Support für DD/L4M (siehe Post 1048374) |

calime

Beginner

Posts: 5

  • Send private message

152

Friday, January 20th 2012, 9:46pm

new version of plugin ddci since yesterday !

I compile a new version of VDR 1.7.23 with this new version of ddci (you have to apply last line of patch vdr-1.7.22-external-ci.patch by hand but it works)
I actived debug option in ci.c and run VDR with this commande : sudo ./vdr -w 60 -P xineliboutput -P ddci >/var/log/smartcard.txt 2>&1

I start on a clear channel and after 1 minute zap on a crypted channel . and ... it doesnt decrypte ;(

I join the file smartcard.txt if it can help ....
calime has attached the following file:
  • smartcard.txt (61.25 kB - 55 times downloaded - latest: May 14th 2013, 9:41am)

mini73

Moderator

Posts: 2,988

Location: Flensburg

  • Send private message

153

Saturday, January 21st 2012, 3:53pm

Hi,

Communication with the CAM seems to work, I suspect there's the same problem I have: I can't read anything from sec0 respectively read doesn't return any data or error.

Lars.

meine Signatur

vdr2: yaVDR 0.5/softhddevice @ G540, Intel DH67BLB3, Asus GT610/2GB, DDBridge + 2x DuoFlex C/T
vdr: yaVDR 0.2/pvr350 @ Sempron 64 LE-1200, MSI K9MM-V, 1x PVR350, 2x Satelco EasyWatch DVB-C
hdvdr: yaVDR unstable/softhddevice @ E8400, Asus P5Q SE Plus, 1x L4M-TwinCI + Flex C/T, 1x Sundtek MediaTV Pro, GT520
Plugins: | avahi4vdr | dbus2vdr | dynamite | noepg | pvrinput | sundtek |
pre-alpha Plugins: | ddci CI-Support für DD/L4M (siehe Post 1048374) |

UFO

Sage

  • "UFO" started this thread

Posts: 4,850

Location: Großherzogthum Baden

  • Send private message

154

Saturday, January 21st 2012, 5:59pm

Quoted from "mini73"


Communication with the CAM seems to work, I suspect there's the same problem I have: I can't read anything from sec0 respectively read doesn't return any data or error.

Habe mir das Plugin nicht genauer angesehen, aber noch ein paar Hinweise:

Das sec-Device sollte *zweimal* geöffnet werden:
- Write-Only zum Schreiben zum CAM
- Read-only zum Lesen vom CAM

Es müssen immer Vielfache von 188 Bytes (TS-Paket) geschrieben/gelesen werden.

Testen kann man den Datentransfer auch mit unverschlüsselten Daten, sogar ohne CAM.
Das Teil ist dann im Loopback-Modus.

CU
Oliver
VDR Remote Control Plugin (Version 0.5.0): http://www.escape-edv.de/endriss/vdr
FAQ zum Remote Control Plugin: http://www.escape-edv.de/endriss/vdr/FAQ
SDRAM-Erweiterung auf 4 MByte: http://www.escape-edv.de/endriss/dvb-mem-mod
Full-TS-Mod für (SD) full-featured Karten: http://www.escape-edv.de/endriss/dvb-full-ts-mod bzw. hier
Aktuelle Treiber: http://www.vdr-portal.de/board16-video-d…-s2-6400-teil-2

mini73

Moderator

Posts: 2,988

Location: Flensburg

  • Send private message

155

Saturday, January 21st 2012, 6:29pm

Moin!

Ok, werde es noch mal mit zweimaligem Öffnen versuchen. Hatte ich zwar schon mal, aber es kann sein, dass ich nicht "write only" gesetzt habe.
Ich benutze einen cTSBuffer und schreibe immer 188 Byte Pakete. Wenn die Systemlast dadurch zu groß wird, werde ich noch ein Vielfaches eines TS-Pakets probieren.
Aber erst mal soll es überhaupt funktionieren.

Danke!

Lars.

meine Signatur

vdr2: yaVDR 0.5/softhddevice @ G540, Intel DH67BLB3, Asus GT610/2GB, DDBridge + 2x DuoFlex C/T
vdr: yaVDR 0.2/pvr350 @ Sempron 64 LE-1200, MSI K9MM-V, 1x PVR350, 2x Satelco EasyWatch DVB-C
hdvdr: yaVDR unstable/softhddevice @ E8400, Asus P5Q SE Plus, 1x L4M-TwinCI + Flex C/T, 1x Sundtek MediaTV Pro, GT520
Plugins: | avahi4vdr | dbus2vdr | dynamite | noepg | pvrinput | sundtek |
pre-alpha Plugins: | ddci CI-Support für DD/L4M (siehe Post 1048374) |

mini73

Moderator

Posts: 2,988

Location: Flensburg

  • Send private message

156

Sunday, January 22nd 2012, 3:31pm

Hi,

For those, who want to verify if the CI/CAM is working, you can use the "redirect" attribute of ddbridge.
My setup:

Source code

 
1
2
3
4
5
6

$> dmesg
DDBridge 0000:04:00.0: irq 47 for MSI/MSI-X
Port 0 (TAB 1): NO MODULE
Port 1 (TAB 2): DUAL DVB-C/T
Port 2 (TAB 3): CI internal
Port 3 (TAB 4): CI internal

CAM is in second CI on port 3.

EDIT: With recent drivers removing of the unneeded frontend is not necessary anymore. They are combined in one frontend /EDIT
I load the driver with adapter_alloc=3, which will create all devices in one adapter-directory. I just want to use DVB-C, so I remove the DVB-T-Frontends (old driver with frontend per delivery system):

Source code

 
1
2
3

$> sudo modprobe ddbridge adapter_alloc=3
$> sudo rm /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend3
$> sudo mv /dev/dvb/adapter0/frontend2 /dev/dvb/adapter0/frontend1


Redirect input of first tuner through first CI and second tuner through second CI, so ca0 belongs to dvr0 and ca1 to dvr1 (vdr will combine all devices with the same device number in one cDvbDevice):

Source code

 
1
2

sudo echo "02 02" > /sys/class/ddbridge/ddbridge0/redirect
sudo echo "03 03" > /sys/class/ddbridge/ddbridge0/redirect

Look at http://www.spinics.net/lists/linux-media/msg39494.html for your right redirect-value.
IMPORTANT: The redirect value has to be written before the first use of the device!

Now vdr can be used without ddci and the second tuner can decrypt channels.
With this I can confirm my CAM is working...

No luck so far with separated opens for read and write to sec.

Lars.

meine Signatur

vdr2: yaVDR 0.5/softhddevice @ G540, Intel DH67BLB3, Asus GT610/2GB, DDBridge + 2x DuoFlex C/T
vdr: yaVDR 0.2/pvr350 @ Sempron 64 LE-1200, MSI K9MM-V, 1x PVR350, 2x Satelco EasyWatch DVB-C
hdvdr: yaVDR unstable/softhddevice @ E8400, Asus P5Q SE Plus, 1x L4M-TwinCI + Flex C/T, 1x Sundtek MediaTV Pro, GT520
Plugins: | avahi4vdr | dbus2vdr | dynamite | noepg | pvrinput | sundtek |
pre-alpha Plugins: | ddci CI-Support für DD/L4M (siehe Post 1048374) |

This post has been edited 3 times, last edit by "mini73" (Yesterday, 9:11am)

mini73

Moderator

Posts: 2,988

Location: Flensburg

  • Send private message

157

Sunday, January 22nd 2012, 5:00pm

Moin!

Quoted from "UFO"

Das sec-Device sollte *zweimal* geöffnet werden:
- Write-Only zum Schreiben zum CAM
- Read-only zum Lesen vom CAM
Es müssen immer Vielfache von 188 Bytes (TS-Paket) geschrieben/gelesen werden.

Ich mache nun folgendes:
  • ich starte einen cRingBufferLinear auf dem Filehandle von dvr
    Der liest in einem eigenen Thread die Daten von dvr in einen Buffer
  • ich starte einen cRingBufferLinear auf dem Lese-Filehandle von sec
    Dieser wird an den vdr statt des sonst üblichen dvr-Buffers gegeben
  • immer, wenn der vdr Daten aus dem sec-Buffer holt, schaue ich nach, ob Daten im dvr-Buffer sind und schreibe sie ggf. nach sec

Auch mit einem unverschlüsseltem Sender klappt es nicht. Lesen aus dvr und Schreiben nach sec funktioniert, aber irgendwie bekommt der sec-Buffer nichts gelesen.
Nur manchmal beim ersten mal kommen ein paar verschlüsselte Pakete heraus.
Aber ich gebe nicht auf. ;-)

Gab es nicht irgendwie ein modifiziertes czap oder so, dass mit den Cine-CI funktioniert? Leider finde ich es nirgendwo...

Lars.

meine Signatur

vdr2: yaVDR 0.5/softhddevice @ G540, Intel DH67BLB3, Asus GT610/2GB, DDBridge + 2x DuoFlex C/T
vdr: yaVDR 0.2/pvr350 @ Sempron 64 LE-1200, MSI K9MM-V, 1x PVR350, 2x Satelco EasyWatch DVB-C
hdvdr: yaVDR unstable/softhddevice @ E8400, Asus P5Q SE Plus, 1x L4M-TwinCI + Flex C/T, 1x Sundtek MediaTV Pro, GT520
Plugins: | avahi4vdr | dbus2vdr | dynamite | noepg | pvrinput | sundtek |
pre-alpha Plugins: | ddci CI-Support für DD/L4M (siehe Post 1048374) |

Flachzange

Intermediate

Posts: 199

  • Send private message

158

Monday, January 23rd 2012, 8:38pm

Quoted from "mini73"

Hi,

For those, who want to verify if the CI/CAM is working, you can use the "redirect" attribute of ddbridge.

....

Hi Lars,

thanks for the redirection hint. I tried to repeat the experiment on my Cine CT v6 with a single CI-Module.:


Source code

 
1
2
3

Port 0 (TAB 1): DUAL DVB-C/T
Port 1 (TAB 2): NO MODULE
Port 2 (TAB 3): CI



Source code

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14

ls -la /dev/dvb/adapter0/

drwxr-xr-x 2 root root 	240 2012-01-23 20:31 .
drwxr-xr-x 3 root root  	60 2012-01-23 20:31 ..
crw-rw---- 1 root video 212, 8 2012-01-23 20:31 ca0
crw-rw---- 1 root video 212, 0 2012-01-23 20:31 demux0
crw-rw---- 1 root video 212, 4 2012-01-23 20:31 demux1
crw-rw---- 1 root video 212, 1 2012-01-23 20:31 dvr0
crw-rw---- 1 root video 212, 5 2012-01-23 20:31 dvr1
crw-rw---- 1 root video 212, 3 2012-01-23 20:31 frontend0
crw-rw---- 1 root video 212, 7 2012-01-23 20:31 frontend1
crw-rw---- 1 root video 212, 2 2012-01-23 20:31 net0
crw-rw---- 1 root video 212, 6 2012-01-23 20:31 net1
crw-rw---- 1 root video 212, 9 2012-01-23 20:31 sec0


Redirects:

Source code

 
1
2

echo "00 02" > /sys/class/ddbridge/ddbridge0/redirect
 echo "01 02" > /sys/class/ddbridge/ddbridge0/redirect



When I switch to an encrypted channel, vdr assigns the cam to the device, but the screen stays black. BUT, I don't get the message "channel not available".

Within vdr I see the CAM and I can read my smartcard.

I am actually not 100% sure about my redirects.

Any ideas?

Thx
Christoph
Testsystem:
Hardware: Lian Li C39, Core-i7-3632QM, Jetway NF9G-QM77, 4GB RAM, PicoPSU 160XT inkl 80W Morex, 3x 2,5" 1TB RAID5, 1xSamsung PM830 mSATA 128GB, 1x LG BDROM, 1x DD Cine CT (v6) + CI + Alphacrypt CAM
Software: Ubuntu 13.04 mit 3.8 x64, VDR 2.0.1 + xbmc 12.2

mini73

Moderator

Posts: 2,988

Location: Flensburg

  • Send private message

159

Tuesday, January 24th 2012, 9:05am

Hi,

I would only set one redirection "00 02", since there is only one ca-Device with the device number 0.
Whatever you receive with the second tuner, vdr will not send the PMT to the ca, since there isn't a ca1.
So it will not be decrypted.

Lars.

meine Signatur

vdr2: yaVDR 0.5/softhddevice @ G540, Intel DH67BLB3, Asus GT610/2GB, DDBridge + 2x DuoFlex C/T
vdr: yaVDR 0.2/pvr350 @ Sempron 64 LE-1200, MSI K9MM-V, 1x PVR350, 2x Satelco EasyWatch DVB-C
hdvdr: yaVDR unstable/softhddevice @ E8400, Asus P5Q SE Plus, 1x L4M-TwinCI + Flex C/T, 1x Sundtek MediaTV Pro, GT520
Plugins: | avahi4vdr | dbus2vdr | dynamite | noepg | pvrinput | sundtek |
pre-alpha Plugins: | ddci CI-Support für DD/L4M (siehe Post 1048374) |

Flachzange

Intermediate

Posts: 199

  • Send private message

160

Tuesday, January 24th 2012, 12:15pm

Brilliant! That does the job. I see, I still do not know enough about vdr internal stuff :)
Testsystem:
Hardware: Lian Li C39, Core-i7-3632QM, Jetway NF9G-QM77, 4GB RAM, PicoPSU 160XT inkl 80W Morex, 3x 2,5" 1TB RAID5, 1xSamsung PM830 mSATA 128GB, 1x LG BDROM, 1x DD Cine CT (v6) + CI + Alphacrypt CAM
Software: Ubuntu 13.04 mit 3.8 x64, VDR 2.0.1 + xbmc 12.2