Closed 3PO closed 9 years ago
It's not yet in VDR. In the mean time you have to apply this: http://skyboo.net/pub/vdr-2.1.6-catemmpids-02.diff
THX! Now it seems working:
2014/04/08 20:20:10 85A770 r sky [irdeto] vdr_dvbapi emmtype=shared, len=139, idx=56, cnt=2: written (610 ms)
BTW: Is it planned, to implant this Patch into the VDR in a future Version?
Yes :)
Does this patch work for anyone with Via5.0 cards (0500:050800)? After applying the patch I do get EMMs to my NDS card, but not to the Viaccess card. According to oscam (with -d128) there is only an emmfilter set for caid 0001 (?) when switching to a channel with 0500:050800 ECMs.
It is a general patch for allowing EMMs. So if EMMs generally works, but not for some CAID/card then you should look for help on the oscam forum, or review your configuration. You also can switch to classic socket mode (disable network mode) and then you can make sure if it is working or not (OScam is then handling it itself).
Also make sure that you are waiting some time. IIRC it is set to 30 seconds after channel zap (to EMMs starts flowing).
Thats what I thought, my subscription already expired, so this is never tried for 30 seconds. Not sure if its vdr itself, satip plugin or dvbapi- but it seems there are only 2-3 ECMs tried and then it stops even trying. Unfortunately I cannot switch to socket mode as I only have satip as input (no actual DVB hardware). (Btw I already tried in OSCAM forum, they are saying Viaccess 5.0 updates are working in general and noone else seems to use it combined with DVBAPI)
Ah... this problem was also raised some time ago (I cannot fix it, the VDR has to do something in this case, eg constantly waiting on the channel without hopping on available CAMs). Ask on VDR forum for the solution, while in the mean time you can probably increase the TS_SCRAMBLING_TIMEOUT in the device.c (from VDR).
Good point, I increased it to 60 seconds but still no lock. I assume the added EMM handling of the patch is never triggered in "void cDevice::Action(void)". I'll bring it up in the vdr-ml or vdr-portal then. Thanks for taking your time to analyze this.
I'd suggest to add two items to the FAQ:
Closing this issue, as the new VDR 2.1.7 has this feature/patch (and other EMM handling fixes) finally in :)
In Network Mode the dvbapi-Plugin do not sent any EMM Requests.
"AU" is enabled for "dvbapi" and "user"
oscam.conf: (<-- on oscam Server)
oscam.user (<-- on oscam Server)