search

manio / vdr-plugin-dvbapi

VDR dvbapi plugin for use with OSCam
http://www.streamboard.tv/wbb2/thread.php?threadid=40060
GNU General Public License v2.0
58 stars 25 forks source link

vdr-plugin-dvbapi does not work with oscam >= r11195 #102

Closed 3PO closed 8 years ago

3PO commented 8 years ago

the support für the vdr-dvbapi Plugin is broken since oscam r11195.

further Information --> http://www.streamboard.tv/wbb2/thread.php?postid=556366#post556366

3PO commented 8 years ago

Any News?

manio commented 8 years ago

If it was working before, and now after some OSCam changes it is broken then I think the changes which broke it are in the OSCam. The plugin was untouched for a longer time period. If the problem is in the dvbapi plugin, please provide a log and point me where you suspect if differ from a working version. The plugin just sends a PMT data to the OSCam - that's all - what have I to fix which was working before?

Maybe try this: http://pastebin.com/E7qcERWr ?

If theparasol is telling something about closing socket - It is as I was explaining before: the plugin is using single socket for all decoding, and it is not closing the socket, but sending the DVBAPI_DMX_STOP command to stop descrambling. The connection is still open to allow faster zap times when starting a channel again.

manio commented 8 years ago

@3PO - is it working with the mentioned patch? And a question for sure: I assume that with oscam r11194 it is working ok, right?

3PO commented 8 years ago

with patched dvbapi Plugin and oscam r11200, i get the folowing issue:

--> https://bpaste.net/show/5323f0595e73

manio commented 8 years ago

I am now using OSCam r11200 and my latest master plugin. I am trying to reproduce the problem using a recordings. When I enabled the recording, it successfully start decoding, when i disabled it - it stops, and it is correctly sending the "stop descrambling" command; the socket is left open, and when i re-enabled timer again, it is recording back again. So all is working fine for me. Can you reproduce the problem using recording and activating/deactivating timer? Maybe i have to try harder with normal zapping, what do you think?

3PO commented 8 years ago

Recording, i've never tested.

When i update oscam to >= r11195 and switch to a encypted channel, i get a black Screen and in the log i find the issue i posted above.

manio commented 8 years ago

@3PO Sorry - no idea how to reproduce your problem. I also asked on IRC if the guys there also have similar problems - no one has. Maybe it is related with your channels/config/oscam configuration etc...

manio commented 8 years ago

@3PO From IRC discussion: I don't know if it is related with your problem, but you may also try this patch: http://www.vdr-portal.de/board16-video-disk-recorder/board99-distributionen/board96-yavdr/p1258103-vdr-startet-auf-genau-einem-sender-n-tv-hd-einfach-neu/#post1258103

FrodoVDR commented 8 years ago

@manio I have the same issue and the patch from the vdr-portal was included on my VDR.

Dec 23 08:52:44 vdr4 vdr: [2406] switching to channel 35 Dec 23 08:52:44 vdr4 vdr: [2406] CAM 1: assigned to device 1 Dec 23 08:52:44 vdr4 vdr: [2406] DVBAPI: 0.0 CA_PMT decoding len=28 lm=4 prg=131 len=13 Dec 23 08:52:44 vdr4 vdr: [2406] DVBAPI: ci_cmd(G)=01 Dec 23 08:52:44 vdr4 vdr: [2406] DVBAPI: pid=2,04ff len=0 (0x0) Dec 23 08:52:44 vdr4 vdr: [2406] DVBAPI: pid=6,0503 len=0 (0x0) Dec 23 08:52:44 vdr4 vdr: [2406] DVBAPI: pid=6,0504 len=0 (0x0) Dec 23 08:52:44 vdr4 vdr: [2406] DVBAPI: 0.0 got CA pmt ciCmd=1 caLm=4 Dec 23 08:52:44 vdr4 vdr: [2406] DVBAPI: 0.0 answer to query suppressed Dec 23 08:52:44 vdr4 vdr: [2406] DVBAPI: 0.0 set CAM decrypt (SID 131 (0x0083), caLm 4, HasCaDescriptors 1) Dec 23 08:52:44 vdr4 vdr: [2406] DVBAPI: send: channelSid=0x83 (131) Dec 23 08:52:44 vdr4 vdr: [2406] DVBAPI: Write, sock=58 Dec 23 08:52:44 vdr4 vdr: [2406] DVBAPI: socket_fd=58 len=50 wrote=50 Dec 23 08:52:44 vdr4 vdr: [22093] device 1 receiver thread started (pid=2406, tid=22093, prio=high) Dec 23 08:52:44 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: 002b6f3c Dec 23 08:52:44 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: 00000000 Dec 23 08:52:44 vdr4 vdr: message repeated 3 times: [ [2806] DVBAPI-Error: Action: read failed unknown command: 00000000] Dec 23 08:52:44 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: ff000000 Dec 23 08:52:44 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: 00000000 Dec 23 08:52:44 vdr4 vdr: message repeated 5 times: [ [2806] DVBAPI-Error: Action: read failed unknown command: 00000000] Dec 23 08:52:44 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: 00000004 Dec 23 08:52:44 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: 0000002b Dec 23 08:52:44 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: 3c400001 Dec 23 08:52:44 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: 1a800000 Dec 23 08:52:44 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: 00000000 Dec 23 08:52:44 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: 00000000 Dec 23 08:52:44 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: 0000f000 Dec 23 08:52:44 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: 00000000 Dec 23 08:52:45 vdr4 vdr: message repeated 5 times: [ [2806] DVBAPI-Error: Action: read failed unknown command: 00000000] Dec 23 08:52:45 vdr4 vdr: [2806] DVBAPI-Error: Action: read failed unknown command: 00b80b00

MegaV0lt commented 8 years ago

@3PO when you have the "unknown command" try to restart oscam on the server and see if it working then. In the past that was working here. I still only have 11194 running here.

@manio when "unknown" command can be fixed by oscam restart i think the dvbapi has to do a better connectioncheck with oscam in network mode.

PS: can do no testing, because i am not home during the hole holidays...

manio commented 8 years ago

@FrodoVDR @MegaV0lt So my patch http://pastebin.com/E7qcERWr is not working for the "unknown command" problems?

@FrodoVDR Please don't mix problems - @3PO problems was described in the streamboard thread - he can't zap for the second time, the log which he pasted here was because of my other patch - it is not about the core issue.

MegaV0lt commented 8 years ago

In the 11194 it is not needed. I can not test until early january. At least in 3PO's log ist isnt' working.

FrodoVDR commented 8 years ago

@manio The patch works not correct for me. The same "unknown command" I see in logfile.

But in the test, I noticed that the new versions Oscam work. Apparently only the first link between dvbapi plugin and newer versions Oscam r11194 is disturbed. If the VDR is connected over DVBAPI already to Oscam r11194 also works a newer version, unfortunately, only when switching during operation of Oscam version r11194 to Oscam version r11200.

manio commented 8 years ago

Closing as the problem is not occurs in recent OSCams, it's probably two problems in the same issue, and discussion has moved to the streamboard thread.