Closed CReimer closed 9 years ago
Oscam Version is 9959 BTW and I can easily simulate this problem And here's another set of logs: https://gist.github.com/CReimer/4cf382c9e889ba360f63
Okt 30 20:57:05 vdr4arch vdr[27227]: [27227] DVBAPI: 0.0 set CAM decrypt (SID 4911, caLm 4, HasCaDescriptors 0) Okt 30 20:57:06 vdr4arch vdr[27227]: [27227] DVBAPI: 1.0 set CAM decrypt (SID 5401, caLm 4, HasCaDescriptors 0) Okt 30 20:57:07 vdr4arch vdr[27227]: [27227] DVBAPI: 0.0 set CAM decrypt (SID 4911, caLm 5, HasCaDescriptors 1) Okt 30 20:57:07 vdr4arch vdr[27227]: [27227] DVBAPI: 0.0 set CAM decrypt (SID 4911, caLm 4, HasCaDescriptors 1) Okt 30 20:57:08 vdr4arch vdr[27227]: [27227] DVBAPI: 1.0 set CAM decrypt (SID 5401, caLm 5, HasCaDescriptors 1) Okt 30 20:57:08 vdr4arch vdr[27227]: [27227] DVBAPI: 1.0 set CAM decrypt (SID 5401, caLm 4, HasCaDescriptors 1) Okt 30 20:58:30 vdr4arch vdr[27227]: [27227] DVBAPI: 0.0 set CAM decrypt (SID 4911, caLm 4, HasCaDescriptors 1) Okt 30 20:58:31 vdr4arch vdr[27227]: [27227] DVBAPI: 1.0 set CAM decrypt (SID 5402, caLm 4, HasCaDescriptors 1) Okt 30 20:58:39 vdr4arch vdr[27227]: [27227] DVBAPI: 0.0 set CAM decrypt (SID 61304, caLm 4, HasCaDescriptors 0) Okt 30 20:58:47 vdr4arch vdr[27227]: [27227] DVBAPI: 1.0 set CAM decrypt (SID 5402, caLm 5, HasCaDescriptors 1) Okt 30 20:58:55 vdr4arch vdr[27227]: [27227] DVBAPI: 0.0 set CAM decrypt (SID 61304, caLm 5, HasCaDescriptors 1) Okt 30 20:58:55 vdr4arch vdr[27227]: [27227] DVBAPI: 0.0 set CAM decrypt (SID 61301, caLm 4, HasCaDescriptors 1) Okt 30 20:59:00 vdr4arch vdr[27227]: [27227] DVBAPI: 0.0 set CAM decrypt (SID 61302, caLm 4, HasCaDescriptors 1)
I see exactly same requests in the OSCam log. Sorry I don't know what is wrong. Can you tell me where in the log is the problem?
Maybe I wasn't clear enough. While zapping through a few channels all previous channels seem to remain stuck and oscam keeps decrypting and requesting ECMs.
The problem seems to be this
[DVBAPI] Demuxer #0 continue decoding of SRVID 132F
I found out, that everything works fine with the default VDR skin. That means it has something to do with vdr-skindesigner. I told the maintainer of skindesigner about it and he pointed me to a commit which could cause this problem. http://projects.vdr-developer.org/git/vdr-plugin-skindesigner.git/commit/?id=abd8fd8db042ae860bb5346ce886ee961a847ae6
And he's right. It is exactly this commit, which causes my problem. Do you know what's wrong with his commit?
It also happens with skinflatplus with enabled video bitrate display
It also happens with a default vdr skin and an open femon window. And since both skinflatplus and skindesigner use femon to show the video bitrate...
Maybe the femon is issue here :) Is it working ok when you disable it?
I don't have to remove the plugin. I can start the femon plugin with VDR. The above behaviour only happens if the femon plugin is active (Started via main menu) and I switch channels inside the femon menu.
And both skindesigner and skinflatplus use a part of femon to show additional informations. And therefore they trigger that bug, too.
I see. But I don't consider this as a bug in the dvbapi plugin in this case. Please report it to the femon plugin author. The dvbapi plugin just follows VDR cam requests.
Currently I'm watching Tele 5 HD and Oscam still shows log messages for channels I zapped on a few minutes ago.
https://gist.github.com/CReimer/cdfbd01c895538724440