Closed piotrekcrash closed 7 years ago
The main problem is here:
Feb 28 16:55:03 LibreELEC00 vdr[2715]: [2940] DVBAPI: CA_PMT doesn't contain CA descriptors
This is known VDR disease. It just doesn't collect CAPMT information at all in own channels.conf file (in contrast to tvheadend, wchich I am currently using btw). The other related problem is that VDR is doing retune after CAPMT description has changed. So it is stopping streaming and restarting it (tvh is also handling such situations in the better way IMHO, so the channel is still playing). So after your fresh VDR start you have to switch to a channel at least once (to VDR collect this information), or wait for the idle epg-scan for do this for you. In other words - more time VDR is running, more fast channels are zapping :) VDR was probably designed to be runned 24h a day - so in this configuration there would be probably not such problems, because the epg scan thread is constantly scanning transponders. If you are re-starting VDR often, than it indeed could be a problem - as you are confirming with this issue. Anyway - it is not a dvbapi plugin issue - so I am closing this one.
If you wish - you have to raise this problem on the VDR side, but be prepared that my time which I am now spending on the dvbapi plugin is very limited.
Many thanks for You answer. I also considered to run my KII Pro as Server (24h) and some other TV Box with LE as Clients to VDR Server. Strange thing is in older LibreELEC 7.0 with:
VDR version 2.2.0 dvbapi PKG_VERSION="c76c24e" It works perfect, directly after system boot all works without any problem. But there was used older protocol of OSCam with "camd.socket". Is there still possible to use it like older one or now only TCP mode is available? If "camd.socket" still available I'll test if this works correct on current LE version.
BTW great work with this plugin. Thanks
Newer plugin version only use network mode (camd.socket was deprecated since some version).
Thanks.
Hi,
I'm using KII Pro with: LibreELEC release: S905.arm-8.0.0c-I VDR 2.2.0 / vdr-plugin-dvbapi 2.2.3 OSCam v1.20-unstable_svn, build r11350
I have problem with connection between VDR and OSCam over dvbapi. It's possible to connect both only if directly after System boot I'm changing fast encrypted channels one by one, then dvbapi Client apper in Oscam Clients section and everything works correct to next system boot. But If I'm not make this process on beginning then dvbapi never connect to OSCam.
When dvbapi is not connected to OSCam in logs apper something like this:
but when after few channel changes this will connect it look like this:
and then in OSCam log i can see:
My conf:
VDR:
All system logs I uploaded here;
VDR_dvbapi_OSCam_logs.zip
In file 09_Journal-cur.log there's a lot of entries from dvbapi
Is there any solution for this problem? Thanks