VNSI versions and compatibility
FernetMenta
Retired Team-Kodi Member
Posts: 6,810
#46
2015-02-05, 19:43
why branch jim? Smile use master
Find
Reply
Tuxwork
Junior Member
Posts: 43
#47
2015-02-05, 19:51
jim Updated 5 days ago by FernetMenta
master Updated 11 days ago by FernetMenta Tongue

Ok, i try master Smile

Thanks for reply.
Find
Reply
FernetMenta
Retired Team-Kodi Member
Posts: 6,810
#48
2015-02-05, 21:50
latest != greatest Smile
Find
Reply
Tuxwork
Junior Member
Posts: 43
#49
2015-02-05, 22:16
same problem Confused
Code:
19:55:00 T:3020420992  NOTICE: special://profile/ is mapped to: special://masterprofile/
19:55:00 T:3020420992  NOTICE: -----------------------------------------------------------------------
19:55:00 T:3020420992  NOTICE: Starting Kodi (14.1 Git:Unknown). Platform: Linux x86 32-bit
19:55:00 T:3020420992  NOTICE: Using Debug Kodi x32 build
19:55:00 T:3020420992  NOTICE: Kodi compiled Feb  5 2015 by GCC 4.9.1 for Linux x86 32-bit version 3.16.7 (200711)
19:55:00 T:3020420992  NOTICE: Running on Debian GNU/Linux 8 (jessie), kernel: Linux x86 32-bit version 3.16.0-4-686-pae
19:55:00 T:3020420992  NOTICE: FFmpeg statically linked, version: 2.4.6-xbmc-2.4.6-Helix
19:55:00 T:3020420992  NOTICE: Host CPU: Intel(R) Atom(TM) CPU N270 @ 1.60GHz, 2 cores available
19:55:00 T:3020420992  NOTICE: special://xbmc/ is mapped to: /usr/share/kodi
19:55:00 T:3020420992  NOTICE: special://xbmcbin/ is mapped to: /usr/lib/kodi
19:55:00 T:3020420992  NOTICE: special://masterprofile/ is mapped to: /home/media/.kodi/userdata
19:55:00 T:3020420992  NOTICE: special://home/ is mapped to: /home/media/.kodi
19:55:00 T:3020420992  NOTICE: special://temp/ is mapped to: /home/media/.kodi/temp
19:55:00 T:3020420992  NOTICE: The executable running is: /usr/lib/kodi/kodi.bin
...
...
21:04:59 T:2819902272  NOTICE: PVRManager - starting up
21:04:59 T:2760129344  NOTICE: Thread PVRManager start, auto delete: false
21:04:59 T:2865425216  NOTICE: Thread PVRClient start, auto delete: false
21:04:59 T:2865425216   DEBUG: RegisterClient - registering add-on 'VDR VNSI Client'
21:04:59 T:2865425216   DEBUG: Previous line repeats 1 times.
21:04:59 T:2865425216   DEBUG: PVR - Create - creating PVR add-on instance 'VDR VNSI Client'
21:04:59 T:2865425216   DEBUG: ADDON: Dll Initializing - VDR VNSI Client
21:04:59 T:2865425216   ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (6) from Create and is not usable
21:04:59 T:2865425216    INFO: Called Add-on status handler for '6' of clientName:VDR VNSI Client, clientID:pvr.vdr.vnsi (same Thread=no)
21:04:59 T:2865425216 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 6
21:04:59 T:2865425216 WARNING: UpdateAndInitialiseClients - failed to load the dll for add-on VDR VNSI Client, disabling it
21:04:59 T:3020420992   DEBUG: CGUIMediaWindow::GetDirectory (addons://disabled/)
21:04:59 T:3020420992   DEBUG:   ParentPath = [addons://disabled/]
21:04:59 T:2954242880  NOTICE: Thread AddonStatus pvr.vdr.vnsi start, auto delete: true
21:04:59 T:2954242880   DEBUG: Thread AddonStatus pvr.vdr.vnsi 2954242880 terminating (autodelete)
21:04:59 T:2789751616  NOTICE: Thread BackgroundLoader start, auto delete: false

any idea ?

Thanks.
Find
Reply
wsnipex
Team-Kodi
Posts: 7,648
#50
2015-02-05, 23:20
vnsi master doesn't work on kodi 14.1, only on kodi master.

for 14.1 use opdenkamps helix branch
Team XBMC stable PPA -- Team XBMC unstable PPA -- Team XBMC nightly PPA
DEBUG log
Find
Reply
FernetMenta
Retired Team-Kodi Member
Posts: 6,810
#51
2015-02-06, 08:16
Also note that you can't downgrade addons by installing are earlier version. You have to delete the addon from the file system.
Find
Reply
Tuxwork
Junior Member
Posts: 43
#52
2015-02-06, 15:36
same problem Confused
Code:
13:14:47 T:2820066112   DEBUG: RegisterClient - registering add-on 'VDR VNSI Client'
13:14:47 T:2820066112   DEBUG: Previous line repeats 1 times.
13:14:47 T:2820066112   DEBUG: PVR - Create - creating PVR add-on instance 'VDR VNSI Client'
13:14:47 T:2820066112   DEBUG: ADDON: Dll Initializing - VDR VNSI Client
13:14:47 T:2820066112   ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (6) from Create and is not usable
13:14:47 T:2820066112    INFO: Called Add-on status handler for '6' of clientName:VDR VNSI Client, clientID:pvr.vdr.vnsi (same Thread=no)
13:14:47 T:2820066112 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 6
13:14:47 T:2820066112 WARNING: UpdateAndInitialiseClients - failed to load the dll for add-on VDR VNSI Client, disabling it
13:14:47 T:3020736384   DEBUG: CGUIMediaWindow::GetDirectory (addons://disabled/)
13:14:47 T:3001789248  NOTICE: Thread AddonStatus pvr.vdr.vnsi start, auto delete: true
13:14:47 T:3020736384   DEBUG:   ParentPath = [addons://disabled/]
13:14:47 T:3001789248   DEBUG: Thread AddonStatus pvr.vdr.vnsi 3001789248 terminating (autodelete)
13:14:47 T:3010460480  NOTICE: Thread BackgroundLoader start, auto delete: false
13:14:47 T:3010460480   DEBUG: Thread BackgroundLoader 3010460480 terminating

usin vdr-2.1.7
vnsi 1.2.1

vdr cmd line:
Code:
/usr/bin/vdr -w 60 -Pepgtableid0 -Piptv -Pfemon -Pskincurses -Pwirbelscan -Pstreamdev-server -Pdvbapi -Pvnsiserver -Pxineliboutput --local=none --primary --remote=:37890

Code:
#netstat -naptu |grep vdr
tcp        0      0 0.0.0.0:3000            0.0.0.0:*               LISTEN      1117/vdr        
tcp        0      0 0.0.0.0:37890           0.0.0.0:*               LISTEN      1117/vdr        
tcp        0      0 0.0.0.0:34890           0.0.0.0:*               LISTEN      1117/vdr        
tcp        0      0 0.0.0.0:6419            0.0.0.0:*               LISTEN      1117/vdr        
tcp        0      0 0.0.0.0:2004            0.0.0.0:*               LISTEN      1117/vdr        
udp        0      0 255.255.255.255:37890   0.0.0.0:*                           1117/vdr

vdr startup:
Code:
Feb  6 12:59:14 mediadvb root: init VDR: QBOXS2 Frontend is ready
Feb  6 12:59:14 mediadvb vdr: [1117] VDR version 2.1.7 started
Feb  6 12:59:14 mediadvb vdr: [1117] switched to user 'media'
Feb  6 12:59:14 mediadvb vdr: [1117] loading plugin: /usr/lib/vdr/libvdr-epgtableid0.so.2.1.7
Feb  6 12:59:14 mediadvb vdr: [1117] loading plugin: /usr/lib/vdr/libvdr-iptv.so.2.1.7
Feb  6 12:59:14 mediadvb vdr: [1117] loading plugin: /usr/lib/vdr/libvdr-femon.so.2.1.7
Feb  6 12:59:14 mediadvb vdr: [1117] loading plugin: /usr/lib/vdr/libvdr-skincurses.so.2.1.7
Feb  6 12:59:14 mediadvb vdr: [1117] loading plugin: /usr/lib/vdr/libvdr-wirbelscan.so.2.1.7
Feb  6 12:59:14 mediadvb vdr: [1117] loading plugin: /usr/lib/vdr/libvdr-streamdev-server.so.2.1.7
Feb  6 12:59:14 mediadvb vdr: [1117] loading plugin: /usr/lib/vdr/libvdr-dvbapi.so.2.1.7
Feb  6 12:59:14 mediadvb vdr: [1117] loading plugin: /usr/lib/vdr/libvdr-vnsiserver.so.2.1.7
Feb  6 12:59:14 mediadvb vdr: [1117] loading plugin: /usr/lib/vdr/libvdr-xineliboutput.so.2.1.7
Feb  6 12:59:14 mediadvb vdr: [1117] [xine..put] Listening on address '' port 37890
Feb  6 12:59:14 mediadvb vdr: [1117] loading /etc/vdr/setup.conf
Feb  6 12:59:14 mediadvb vdr: [1117] loading /etc/vdr/sources.conf
Feb  6 12:59:14 mediadvb vdr: [1117] loading /etc/vdr/diseqc.conf
Feb  6 12:59:14 mediadvb vdr: [1117] loading /etc/vdr/channels.conf
Feb  6 12:59:15 mediadvb vdr: [1117] loading /etc/vdr/timers.conf
Feb  6 12:59:15 mediadvb vdr: [1117] loading /etc/vdr/svdrphosts.conf
Feb  6 12:59:15 mediadvb vdr: [1117] loading /etc/vdr/remote.conf
Feb  6 12:59:15 mediadvb vdr: [1117] loading /etc/vdr/keymacros.conf
Feb  6 12:59:15 mediadvb vdr: [1117] DVB API version is 0x050A (VDR was built with 0x050A)
Feb  6 12:59:15 mediadvb vdr: [1117] frontend 0/0 provides DVB-T with QPSK,QAM16,QAM64 ("DiBcom 7000PC")
Feb  6 12:59:15 mediadvb vdr: [1117] frontend 1/0 provides DVB-T with QPSK,QAM16,QAM64 ("DiBcom 7000PC")
Feb  6 12:59:15 mediadvb vdr: [1117] frontend 2/0 provides DVB-S,DVB-S2 with QPSK ("Conexant CX24116/CX24118")
Feb  6 12:59:15 mediadvb vdr: [1117] found 3 DVB devices
Feb  6 12:59:15 mediadvb vdr: [1117] initializing plugin: epgtableid0 (2.1.1): EPG handler for events with table id 0x00
Feb  6 12:59:15 mediadvb vdr: [1117] initializing plugin: iptv (2.1.3): Experience the IPTV
Feb  6 12:59:15 mediadvb vdr: [1117] creating IPTV device 0 (CardIndex=3)
Feb  6 12:59:15 mediadvb vdr: [1117] initializing plugin: femon (2.1.1): DVB Signal Information Monitor (OSD)
Feb  6 12:59:15 mediadvb vdr: [1117] initializing plugin: skincurses (2.1.1): A text only skin
Feb  6 12:59:15 mediadvb vdr: [1117] initializing plugin: wirbelscan (0.0.9): DVB and pvrinput channel scan for VDR
Feb  6 12:59:15 mediadvb vdr: [1117] initializing plugin: streamdev-server (0.6.1-git): VDR Streaming Server
Feb  6 12:59:15 mediadvb vdr: [1117] initializing plugin: dvbapi (2.1.1-GIT-1b9df50): SoftCAM for OSCam
Feb  6 12:59:15 mediadvb vdr: [1117] initializing plugin: vnsiserver (1.2.1): VDR-Network-Streaming-Interface (VNSI) Server
Feb  6 12:59:15 mediadvb vdr: [1117] initializing plugin: xineliboutput (2.0.0-cvs): X11/xine-lib output plugin
Feb  6 12:59:15 mediadvb vdr: [1117] setting primary device to 5
...
and NO "vnsi plugin" log in vdr messages, only this:
Code:
Feb  6 12:59:15 mediadvb vdr: [1117] starting plugin: vnsiserver
Feb  6 12:59:15 mediadvb vdr: [1117] VNSI: Starting vnsi server at port=34890
Feb  6 12:59:15 mediadvb vdr: [1117] VNSI: VNSI Server started
Feb  6 12:59:15 mediadvb vdr: [1117] VNSI: Channel streaming timeout: 10 seconds

any idea ?
Find
Reply
FernetMenta
Retired Team-Kodi Member
Posts: 6,810
#53
2015-02-06, 15:43
you are digging in the wrong place. Kodi fails to load the pvr addon.

failed to load the dll for add-on VDR VNSI Client, disabling it
Find
Reply
Tuxwork
Junior Member
Posts: 43
#54
2015-02-06, 15:56
what the solution ?

Code:
$ ldd  /usr/lib/kodi/addons/pvr.vdr.vnsi/Kodi_VDR_vnsi.pvr
    linux-gate.so.1 (0xb7743000)
    libGLESv2.so.2 => /usr/lib/i386-linux-gnu/libGLESv2.so.2 (0xb76f0000)
    libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb76d5000)
    libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb75e2000)
    libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb759d000)
    libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb742b000)
    libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb740e000)
    libdrm.so.2 => /usr/lib/i386-linux-gnu/libdrm.so.2 (0xb73ff000)
    libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xb73f9000)
    libglapi.so.0 => /usr/lib/i386-linux-gnu/libglapi.so.0 (0xb73e0000)
    /lib/ld-linux.so.2 (0xb7746000)

all library are here Smile
Find
Reply
Tuxwork
Junior Member
Posts: 43
#55
2015-02-09, 13:04
sorry this is not pvr nor vnsi related.
I posted the problem here: http://forum.kodi.tv/showthread.php?tid=...pid1920686
Find
Reply
zeebee
Member
Posts: 53
#56
2015-02-13, 22:48
Ok, I am a little bit confued. Which is the correct vnsi-server for Helix 14.1? I need to compile it on my Cubietruck. Trying to get it (GIT from master) working with Openelec 5.0.3 on RPI2, but after some channel switches the client cannot connect anymore until VDR service is restarted.
Find
Reply
FernetMenta
Retired Team-Kodi Member
Posts: 6,810
#57
2015-02-14, 12:05
Those should work with latest version of the server plugin. If not please set logging level of vdr to 3 and post syslog (afaik the name of the log is different on OE)
Find
Reply
zeebee
Member
Posts: 53
#58
2015-02-14, 16:24
This is a fresh VDR start, a few channel changes. Then I watch a recording for a few seconds and a mkv video. Then I cannot watch any channel (also from other clients than RPI2).
http://pastebin.com/5YnHVZU6 (I hope this is the correct log level)
Find
Reply
FernetMenta
Retired Team-Kodi Member
Posts: 6,810
#59
2015-02-14, 16:47
could you make it hang again and post the log? I want to check if the last messages logged are the same.
Find
Reply
zeebee
Member
Posts: 53
#60
2015-02-14, 19:02
Sure: http://pastebin.com/CykSMBpQ
Find
Reply

Home
Search
Help
Logout Mark Read Team Forum Stats Members Help
VNSI versions and compatibility1