Building pvr.vdr.vnsi with clang results in:
VNSISession.h:47:8: error: no type named 'unique_ptr' in namespace 'std'

Full log:
http://clang.debian.net/logs/2016-08-30/kodi-pvr-vdr-vnsi_1.11.15-1_unstable_clang.log

I'm running Kodi 17.1. I currently use the following GIT version of the VNSI Kodi addon:
2a90c2f
The Kodi GUI shows me that there is a recording pending some days in future.
I've added some logging to my wakeup script so I know when it is called and with which parameters.
With the pending recording and the "modified" wakup script, I used the Kodi-builtin shutdown function to shut down the system. Result is, that the wakeup script isn't called at all. I don't have anything about this in the Kodi log files... Is there some way to debug this and to get it working again?

Build is failing with latest v18.

In file included from /mnt/package/mediacenter-next-osmc/src/xbmc-35925be7ff4e9ee911387a873f7c01387f3a38ee/cmake/addons/build/pvr.vdr.vnsi/src/client.cpp:22:0:
/mnt/package/mediacenter-next-osmc/src/xbmc-35925be7ff4e9ee911387a873f7c01387f3a38ee/cmake/addons/build/pvr.vdr.vnsi/src/client.h:24:27: fatal error: libXBMC_codec.h: No such file or directory
#include "libXBMC_codec.h"
^
compilation terminated.
CMakeFiles/pvr.vdr.vnsi.dir/build.make:134: recipe for target 'CMakeFiles/pvr.vdr.vnsi.dir/src/client.cpp.o' failed
make[5]: *** [CMakeFiles/pvr.vdr.vnsi.dir/src/client.cpp.o] Error 1

libXBMC_codec.h has now been removed with this commit:

[pvr] remove libXBMC_codec.h and add to libXBMC_pvr.h
xbmc/xbmc@979c330

I don't know if this is a generic PVR issue (if so, please link the Issue here) but since updating to Kodi 19 the progress of already watched recordings does no longer survive a reboot.

Was there any change in the PVR API which requires a change in the PVR VDR VNSI Addon?

Since this PR #174 Kodi is terminated with the message

Jan 24 19:31:41: terminate called without an active exception
Aborted

after the network is restored.

All my raspberry pi's have been completely disabling the network for many years when it has nothing to do. Up until this PR, it has never caused any problems.

To be on the safe side I reinstalled the previous version 20.2.1 and the problem is gone again

https://github.com/kodi-pvr/pvr.vdr.vnsi/blob/master/src/responsepacket.cpp#L29
should read
#include "platform/sockets/tcp.h"

Hi there,

this is with the Jarvis branch (both plugin and xbmc, of course). Compilation, installation etc. works, the plugin basically runs. However: it is not possible to switch channels. There is an Isengart related posting here:

http://forum.kodi.tv/showthread.php?tid=231303&pid=2269976#pid2269976

which suggests that setting the "priority" (whatever that may be) in the addon settings to 0. After that channel switching works (if trying to do so from the channel list). However, if I open the EPG display (timeline, so to say) it is still not possible to switch channels from there. The suggestion disable EPG-scanning during streaming (which is also suggested in the forum thread) does not change anything. I also tried to compile the master-branch of Kodi to try the master-branch of this plugin, but the compilation failed so far. I'll eventually give that another try when I have more time.

The log show the following lines:

11:37:48 T:139766880249600  NOTICE: Previous line repeats 1 times.
11:37:48 T:139766880249600   ERROR: AddOnLog: VDR VNSI Client: ReadSuccess - failed with error code '997'
11:37:48 T:139766880249600   ERROR: AddOnLog: VDR VNSI Client: SwitchChannel - failed to set channel
11:37:48 T:139766880249600   ERROR: PVR - SwitchChannel - cannot switch to channel 'ProSieben' on client '741'
11:37:48 T:139766880249600   ERROR: PVRManager - PerformChannelSwitch - failed to switch to channel 'ProSieben'
11:37:48 T:139766880249600 WARNING: HandleMessages - failed to switch channel. playback stopped

The following remark is unrelated to the error and just explains why I'm trying to start to use vnsi, quais off-topic:
Until yesterday I was still using XBMC Frodo with the xvdr plugin and everything worked flawlessly. Just that Gentoo then decided to remove the old xbmc package. Of course, I could downgrade my HTPC to the state before yesterday by restoring my daily backup, but that is just no fun. xvdr plugin as of now doesn't seem to be available for Kodi.

I've moved away from OpenELEC to LibreELEC today which included updating the vnsi plugin. I don't see any versioning here, but OpenELEC used what they called version 1.10.10 of pvr.vdr.vnsi.

After this, switching between TV channels became a lot slower (the "caching" popup appears several times) and occasionally it just keeps caching forever, which is very annoying. The TV is streamed from a powerful local server via Ethernet.

I've tried using OSMC instead, but the same is happening there as well. It used to work just great with an older version of the plugin. (I obviously cannot rule out that there is a problem in Kodi itself.)

I get following errors in kodi log:
2021-04-04 21:15:00.718 T:1113 ERROR <general>: GetChannelGroupMembers: Add-on 'VDR-Network-Streaming-Interface (VNSI) Server:127.0.0.1:34890' returned an error: server error 2021-04-04 21:15:00.719 T:1113 ERROR <general>: GetChannelGroupMembers: PVR client 'VDR-Network-Streaming-Interface (VNSI) Server:127.0.0.1:34890' returned an error: server error

full debug log
https://pastebin.ubuntu.com/p/QFyMwb8gks/

Hi there,
is there any possibility to suspend the PVR device while Kodi is in idle state?
With Kodi not running but only VDR, the PVR device is not active (not "locked"), only for EPG updates. However as long as Kodi is running, even if no TV channel is selected, the PVR device stays active and consumes a lot of power (it gets quite hot).
I couldn't find an appropriate option in the settings. Is there something I missed or is this not implemented yet?
Thanks!

Hi everybody,

noticed this with the vnsiserver (v2.6.19.1) under Kodi 17:
In former versions there was a setting "Allow VDR messages" which suppressed any message that came from VDR.
In the mentioned version the setting is gone. When I look into .kodi/userdata/addon_data/pvr.vdr.vnsi/settings.xml there is a '<setting id="handlemessages"...>' tag furthermore. But setting its "value" to "false" seems to have no effect, VDR messages are displayed though.

Background:
When the filesystem of the VDR recordings is almost full, VDR sends "Disk almost full" every few minutes which is then displayd in Kodi every few minutes too. This bothers "a bit" while watching TV or any other video.
I could suppress these messages with the mentioned setting in the past so it would be great if it could come back (or another method of suppressing these messages).

Thx in advance!
T0mcat

I can't know how to install this software and what is it requirements. Please add README.md file.

It seems like Kodi is trying check support for undelete and channel scan before it is connected to backend. And because of that deleted recordings isn't available on Kodi.

2022-03-05 10:29:33.572 T:1537    ERROR <general>: AddOnLog: pvr.vdr.vnsi: SupportChannelScan - Can't get response packed
2022-03-05 10:29:33.572 T:1537     INFO <general>: AddOnLog: pvr.vdr.vnsi: SupportRecordingsUndelete - Undelete not supported on backend (min. Ver. 1.3.0; Protocol 7)

...
2022-03-05 10:29:39.617 T:1572 INFO <general>: AddOnLog: pvr.vdr.vnsi: Logged in at '1646468979+7200' to 'VDR-Network-Streaming-Interface (VNSI) Server' Version: '1.8.0' with protocol version '13'

Debug log: https://paste.kodi.tv/tuyomacujo.kodi

I found this issue #162 where this is also mentioned but unfortunately even using latest VNSI client and server I'm still getting this error.

Last weekend channels.conf gone empty. it took me more than one our to realize this. No error from VDR. No Error from VNSI itself. TV doesn't came up. After looking line for line in debug log i saw loading 0 groups/channel.

If TV cannot be showed because of empty tv list maybe vnsi should at least give an error on screen that there are no channels to show.

Hi,

I've been working on getting backend resume positions and other info (artwork, actors etc) to VNSI. I'm now asking are new features even accepted?

You can see my work here https://github.com/Dis90/pvr.vdr.vnsi/tree/tvscraper_backendresume_nexus and here https://github.com/Dis90/vdr-plugin-vnsiserver/tree/tvscraper_backendresume and some discussion about situation here vdr-projects/vdr-projects.github.io#11

For my knowledge there's no active maintainer either vnsiserver or vnsi client so I don't know who can review changes made.

According to https://github.com/kodi-pvr/pvr.vdr.vnsi/blob/Krypton/pvr.vdr.vnsi/addon.xml.in, the current version is 2.6.14. Can you please tag this release?

Releases make things a lot easier for distributions (in my case, Gentoo) to package the add-on.

Thanks!

I am using Kodi on a raspberry pi and my VDR does not run all the time. And in this case Kodi or VNSI client will tell me every x seconds that the connection failed.
Users do not need the information that yet another connection attempt failed. It is redundant and distracting, because it won't stop telling you about the failing connection even when you are watching something from a different source.

VNSI client should tell me once (on startup) that the connection failed and then shut up until the state changes. So unless VNSI client just started or had a connection and lost it, I don't want to see connection lost notifications.

when vnsi is being configured, according it's cmake file it looks first for OpenGL.

imx libs do contain libGL.so, but this is used for X and whole configuration / compilation goes wrong direction.

I'm trying to build the latest GIT version on Arch Linux. Currently this fails for me.

I use the following build script:
https://github.com/VDR4Arch/vdr4arch/blob/vdr-stable/kodi-addon-pvr-vdr-vnsi/PKGBUILD

The following versions are installed:
p8-platform 2.0.1-2
kodi-platform 20160516.c8188d8-1
kodi 16.1-4

While compiling I get the following:
-- VDR OSD support enabled via OpenGL
-- VDR_VERSION=2.6.3
-- Configuring done
-- Generating done
-- Build files have been written to: /home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/build
[ 8%] Building CXX object CMakeFiles/pvr.vdr.vnsi.dir/src/VNSIData.cpp.o
[ 16%] Building CXX object CMakeFiles/pvr.vdr.vnsi.dir/src/VNSIDemux.cpp.o
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIDemux.cpp: In member function 'DemuxPacket* cVNSIDemux::Read()':
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIDemux.cpp:152:33: error: 'struct PVR_STREAM_PROPERTIES::PVR_STREAM' has no member named 'iPID'
if (m_streams.stream[i].iPID == pid)
^~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIDemux.cpp: In member function 'void cVNSIDemux::StreamChange(cResponsePacket_)':
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIDemux.cpp:307:31: error: 'struct PVR_STREAM_PROPERTIES::PVR_STREAM' has no member named 'iPID'
m_streams.stream[count].iPID = pid;
^~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIDemux.cpp:351:31: error: 'struct PVR_STREAM_PROPERTIES::PVR_STREAM' has no member named 'iSubtitleInfo'
m_streams.stream[count].iSubtitleInfo = (composition_id & 0xffff) | ((ancillary_id & 0xffff) << 16);
^~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIDemux.cpp: In member function 'bool cVNSIDemux::StreamContentInfo(cResponsePacket_)':
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIDemux.cpp:404:31: error: 'struct PVR_STREAM_PROPERTIES::PVR_STREAM' has no member named 'iPID'
if (m_streams.stream[i].iPID == pid)
^~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIDemux.cpp:440:16: error: 'struct PVR_STREAM_PROPERTIES::PVR_STREAM' has no member named 'iSubtitleInfo'
props->iSubtitleInfo = (composition_id & 0xffff) | ((ancillary_id & 0xffff) << 16);
^~~~~~~~~~~~~
make[2]: *** [CMakeFiles/pvr.vdr.vnsi.dir/build.make:255: CMakeFiles/pvr.vdr.vnsi.dir/src/VNSIDemux.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp: In member function 'bool cVNSIData::Start(const string&, int, const char_, const string&)':
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:89:8: error: 'class CHelper_libXBMC_pvr' has no member named 'ConnectionStateChange'
PVR->ConnectionStateChange("VNSI started", PVR_CONNECTION_STATE_CONNECTING, "VNSI started");
^~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:89:46: error: 'PVR_CONNECTION_STATE_CONNECTING' was not declared in this scope
PVR->ConnectionStateChange("VNSI started", PVR_CONNECTION_STATE_CONNECTING, "VNSI started");
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp: In member function 'virtual void cVNSIData::OnDisconnect()':
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:100:8: error: 'class CHelper_libXBMC_pvr' has no member named 'ConnectionStateChange'
PVR->ConnectionStateChange("vnsi connection lost", PVR_CONNECTION_STATE_DISCONNECTED, XBMC->GetLocalizedString(30044));
^~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:100:54: error: 'PVR_CONNECTION_STATE_DISCONNECTED' was not declared in this scope
PVR->ConnectionStateChange("vnsi connection lost", PVR_CONNECTION_STATE_DISCONNECTED, XBMC->GetLocalizedString(30044));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp: In member function 'virtual void cVNSIData::OnReconnect()':
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:107:8: error: 'class CHelper_libXBMC_pvr' has no member named 'ConnectionStateChange'
PVR->ConnectionStateChange("vnsi connection established", PVR_CONNECTION_STATE_CONNECTED, XBMC->GetLocalizedString(30045));
^~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:107:61: error: 'PVR_CONNECTION_STATE_CONNECTED' was not declared in this scope
PVR->ConnectionStateChange("vnsi connection established", PVR_CONNECTION_STATE_CONNECTED, XBMC->GetLocalizedString(30045));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp: In member function 'PVR_ERROR cVNSIData::GetRecordingsList(ADDON_HANDLE)':
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:790:11: error: 'PVR_RECORDING {aka struct PVR_RECORDING}' has no member named 'iChannelUid'; did you mean 'strChannelName'?
tag.iChannelUid = -1;
^~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:793:13: error: 'PVR_RECORDING {aka struct PVR_RECORDING}' has no member named 'iChannelUid'; did you mean 'strChannelName'?
tag.iChannelUid = uuid;
^~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:796:6: error: 'PVR_RECORDING {aka struct PVR_RECORDING}' has no member named 'iChannelUid'; did you mean 'strChannelName'?
tag.iChannelUid = PVR_RECORDING_CHANNEL_TYPE_TV;
^~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:796:20: error: 'PVR_RECORDING_CHANNEL_TYPE_TV' was not declared in this scope
tag.iChannelUid = PVR_RECORDING_CHANNEL_TYPE_TV;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:798:6: error: 'PVR_RECORDING {aka struct PVR_RECORDING}' has no member named 'iChannelUid'; did you mean 'strChannelName'?
tag.iChannelUid = PVR_RECORDING_CHANNEL_TYPE_RADIO;
^~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:798:20: error: 'PVR_RECORDING_CHANNEL_TYPE_RADIO' was not declared in this scope
tag.iChannelUid = PVR_RECORDING_CHANNEL_TYPE_RADIO;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:800:6: error: 'PVR_RECORDING {aka struct PVR_RECORDING}' has no member named 'channelType'; did you mean 'iGenreType'?
tag.channelType = PVR_RECORDING_CHANNEL_TYPE_UNKNOWN;
^~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:800:20: error: 'PVR_RECORDING_CHANNEL_TYPE_UNKNOWN' was not declared in this scope
tag.channelType = PVR_RECORDING_CHANNEL_TYPE_UNKNOWN;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:804:11: error: 'PVR_RECORDING {aka struct PVR_RECORDING}' has no member named 'iChannelUid'; did you mean 'strChannelName'?
tag.iChannelUid = PVR_CHANNEL_INVALID_UID;
^~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:804:25: error: 'PVR_CHANNEL_INVALID_UID' was not declared in this scope
tag.iChannelUid = PVR_CHANNEL_INVALID_UID;
^~~~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:805:11: error: 'PVR_RECORDING {aka struct PVR_RECORDING}' has no member named 'channelType'; did you mean 'iGenreType'?
tag.channelType = PVR_RECORDING_CHANNEL_TYPE_UNKNOWN;
^~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:805:25: error: 'PVR_RECORDING_CHANNEL_TYPE_UNKNOWN' was not declared in this scope
tag.channelType = PVR_RECORDING_CHANNEL_TYPE_UNKNOWN;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp: In member function 'PVR_ERROR cVNSIData::GetDeletedRecordingsList(ADDON_HANDLE)':
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:955:11: error: 'PVR_RECORDING {aka struct PVR_RECORDING}' has no member named 'iChannelUid'; did you mean 'strChannelName'?
tag.iChannelUid = vresp->extract_S32();
^~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:958:11: error: 'PVR_RECORDING {aka struct PVR_RECORDING}' has no member named 'iChannelUid'; did you mean 'strChannelName'?
tag.iChannelUid = PVR_CHANNEL_INVALID_UID;
^~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:958:25: error: 'PVR_CHANNEL_INVALID_UID' was not declared in this scope
tag.iChannelUid = PVR_CHANNEL_INVALID_UID;
^~~~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp: In member function 'virtual void_ cVNSIData::Process()':
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:1061:9: error: 'class CHelper_libXBMC_pvr' has no member named 'ConnectionStateChange'
PVR->ConnectionStateChange("vnsi server not reacheable",
^~~~~~~~~~~~~~~~~~~~~
/home/build/BUILDDIR/kodi-addon-pvr-vdr-vnsi/src/pvr.vdr.vnsi/src/VNSIData.cpp:1062:10: error: 'PVR_CONNECTION_STATE_SERVER_UNREACHABLE' was not declared in this scope
PVR_CONNECTION_STATE_SERVER_UNREACHABLE, nullptr);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[2]: *** [CMakeFiles/pvr.vdr.vnsi.dir/build.make:231: CMakeFiles/pvr.vdr.vnsi.dir/src/VNSIData.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:100: CMakeFiles/pvr.vdr.vnsi.dir/all] Error 2
make: *** [Makefile:150: all] Error 2

Hello
great work on the plugin.

I have created a simple script to generate picons symlinks (map them with proper channel png files).
I traced kodi accessing the picon files (with strace) so I knew it wasn't channel name based but picon based.

However, now I can see Kodi accesses the picon files but they are not displayed (they are transparent). Any ideas what could be wrong?

There is nothing in the kodi logs although I haven't checked with the debug mode yet.

Thank you very much

In analogy to #29 I'd like to be able to see episode name in PVR recordings list or recordings infor.

Let the recordings' info text file look like this:

C C-61441-10002-53110 RTL NITRO
E 6750 1494107100 2700 4E 10
T Chicago Fire
S Der freie Fall
D Dawson und Shay verbringen endlich das lange geplante Mädelswochenende. Kurz nach der Ankunft in der Waldhütte bricht Dawson jedoch in Tränen aus, weil sie an ihrer Beziehung zu Casey zweifelt. Als sich endlich Entspannung in der Ferienhütte einstellt, passiert plötzlich ein Unfall, der den beiden keine Gelegenheit bietet, ihren Beruf einmal hinter sich zu lassen. Als ein arbeitsunfähiger und suchtkranker Kollege aus Denver, Dave Bloom, wegen Trunkenheit am Steuer angezeigt wird, bürgt Sev
X 2 03 deu
X 3 03 deu
F 25
P 50
L 99
@ 12 - RTL NITROChicago Fire14941065001494110700636750

I'd like to see 'Der freie Fall' when browsing the recordings in Kodi UI.

I posted some info about this issue here.
It seem to work only on X11/GL but not on GBM/GLES.

When creating a new epg search timer rule with "Any channel" selected it will not be saved.

I use OpenELEC 5.0.3 with vdr-vnsiserver latest Git code (but also tried several older releases).

All TV channels have 1:1 aspect ratio when I select "Normal" view mode, although the XVDR plugin works OK.

I can of course force a certain ratio for some/all channels, but many channels switch aspect ratio on the fly, so this is unusable. Switching on the fly also works with XVDR, but the OpenELEC folks claim that XVDR is "obsolete" and that I should use VNSI.

Hello,

I have activated VNSI and VU+/Enigma PVR addon under Openelec 6.0.0.

In this case the channel groups of the VU+/Enigma PVR addon are deleted.

Most time also the channels of the VU+/Enigma PVR addon are missing after reboot or the progress bar of the PVR manager hangs and TV is not available.

Does the PVR VNSI supports further PVR addons in parallel?

Falcon66

Hey there,

dunno if it's the right repo or if it's a vdr-plugin-vnsiserver issue, but since the update to openelec 6.0 I got random freezes of Live-TV. While the pictures freezes it's still possible to use the menu and to stop the stream. When I started it again it will freeze again after a few seconds. After a reboot of openelec it will work for several hours +/-

I think there are users with a similar problem: http://openelec.tv/forum/87-vdr-addon/79303-need-help-live-tv-freeze-after-a-short-play?limitstart=0

I have the feeling that it will work longer when I disable timeshift function but I'm not sure.

Log-Entries of kodi when the problem appears:
00:00:02 201398.875000 T:1585157184 ERROR: AddOnLog: VDR VNSI Client: ReadResult - request timed out after 3 seconds
00:00:02 201398.875000 T:1585157184 ERROR: AddOnLog: VDR VNSI Client: GetDriveSpace - Can't get response packed
00:00:05 201401.875000 T:1585157184 ERROR: AddOnLog: VDR VNSI Client: ReadResult - request timed out after 3 seconds
00:00:05 201401.875000 T:1585157184 ERROR: AddOnLog: VDR VNSI Client: GetChannelsCount - Can't get response packed
00:00:08 201404.875000 T:1585157184 ERROR: AddOnLog: VDR VNSI Client: ReadResult - request timed out after 3 seconds
00:00:08 201404.875000 T:1585157184 ERROR: AddOnLog: VDR VNSI Client: GetTimersCount - Can't get response packed
00:00:11 201407.875000 T:1585157184 ERROR: AddOnLog: VDR VNSI Client: ReadResult - request timed out after 3 seconds
00:00:11 201407.875000 T:1585157184 ERROR: AddOnLog: VDR VNSI Client: GetRecordingsCount - Can't get response packed

Log-Entries of VDR server in the regarding timeframe:
Dec 29 00:05:20 hp-g8 vdr: [28230] VNSI: cxSocket::read: eof, connection closed
Dec 29 00:05:25 hp-g8 vdr: [28230] ERROR: cLiveStreamer stream processor thread 28233 won't end (waited 5 seconds) - canceling it...
Dec 29 00:05:25 hp-g8 vdr: [28230] VNSI: LiveStreamer::Close - close
Dec 29 00:05:25 hp-g8 vdr: [28230] VNSI: close video input ...
Dec 29 00:05:25 hp-g8 vdr: [28230] VNSI: call retune ...
Dec 29 00:05:25 hp-g8 vdr: [28230] CAM 1: unassigned
Dec 29 00:05:25 hp-g8 vdr: [28230] VNSI: call retune ...
Dec 29 00:05:25 hp-g8 vdr: [28234] device 1 TS buffer thread ended (pid=61758, tid=28234)
Dec 29 00:05:25 hp-g8 vdr: [28231] buffer stats: 1266180 (24%) used
Dec 29 00:05:25 hp-g8 vdr: [28231] device 1 receiver thread ended (pid=61758, tid=28231)
Dec 29 00:05:40 hp-g8 vdr: [28230] VNSI: close video input ...
Dec 29 00:05:40 hp-g8 vdr: [61770] VNSI: Client with ID 44 seems to be disconnected, removing from client list

Anybody got any idea why this is happening? Do I need to update the vnsi plugin to 1.11.11? I can't compile it on openelec, so how to get it done?

My setup:
Server: VDR 2.2.0 with vnsiserver 1.3.1 @ Debian 7.9
Client: 2x Openelec 6.0 @ Raspberry Pi1/Pi2 with vnsi plugin 1.10.10

When u need further information, feel free to give me advise.

Thanks in advance!

I'm missing the option to select a folder for episode recordings. This is available for single and repeating timers only.

Versions:
kodi 16.1
vdr 2.2.0
vnsiserver 1.3.1
pvr.vdr.vnsi 1.11.15

After a kodi upgrade from 15.2 to 16.1, I've been trying to figure out why vnsi has been unable to tune into channels. I'll preface this by stating that vnsiserver was able to work with kodi 15.2 + pvr.vdr.vnsi 1.10.10. And since my vnsiserver hasn't changed, I am certain there is some regression in the addon.

On the vnsiserver side, I did notice this error:
Jul 09 10:20:31 fillmore vdr[6188]: [6245] VNSI-Error: cxSocket::read: read() error at 0/4

I debugged it further and found that the ::read() call in cxSocket::read() was returning with ECONNRESET errno. Not sure why, I am thinking probably a premature connection close on the addon side?

On the kodi side, I did notice this:
10:20:31 T:140256753989376 ERROR: AddOnLog: VDR VNSI Client: DemuxRead - std::exception

Tracing that out hasn't been fun. Still trying to see if I can get a stack trace on that exception.

I've attached debug logs alongside this. Any tips for further tracking down the issue?
vdr.log.txt
kodi.log.txt

Lastly, I wanted to say thanks for maintaining this addon. It is greatly appreciated.

Hi,

first: thanks for your great work!

My Setup:
I have a headless vdr with kodi installed on the same box (livingroom). I use the kodi Idle script addon to create a file when kodi is idle (no tv, music or video playback) and another script takes the date and existence of this file and other services running or not into account to trigger a hibernate if its ok to do so.

The Problem is, that even if vdr would also go into idle (and touch a file for the hibernate script) the still connected vsni client keeps the vdr from doing so. See
https://github.com/FernetMenta/vdr-plugin-vnsiserver/blob/master/status.c#L145

The Solution to this would be to (optionally?) disconnect the vnsiclient when kodi is going into Idle state and reconnect when User activity is detected. Then the vdr could run its shutdown scripts(setting wakeuptimer if needed) and my hibernate script could send the box to hibernate. As Wakeup on unicast works nice, there is no problem in waking up the box from any client.

What are your thoughts on this?

HI,

I'm trying to migrate away from setting the PVRManager on/off to enabling/disabling the actual PVR Plugin via json rpc.
I do this in order to force he client to disconnect from the pvr server.

While the old approach worked, setting the Addon to Enabled=false does not cause a disconnect.

How can this be fixed?

#!/usr/bin/python
import os
import sys
import json, requests
from json import JSONEncoder


url = "http://192.168.1.100:8080/jsonrpc"

def activate(enable) :
    payload = {'jsonrpc': '2.0','method': 'Addons.SetAddonEnabled', 'params' : {'addonid': "pvr.vdr.vnsi", 'enabled': enable},'id':1}
    resp = requests.post(url=url, json=payload)
    #out = resp.text
    #print (out)

def touch(fname, times=None):
    fhandle = open(fname, 'a')
    try:
        os.utime(fname, times)
    finally:
        fhandle.close()

if str(sys.argv[1]) == "true" :
    touch("/tmp/kodiidle")
    activate(False)
    #xbmc.executebuiltin('xbmc.' + 'StopPVRManager')
else:
    try:
        os.remove("/tmp/kodiidle")
    except: 
        pass
    activate(True)
    #xbmc.executebuiltin('xbmc.' + 'StartPVRManager')

Steps to reproduce:

• Create a timer in VDR with VPS enabled
• Start Kodi

Now Kodi 19 has a timer of type "Reminder" that will pop up before the start.
There is no chance to disable the reminder.

Up to Kodi 18 the timer was of type "VPS" without annoying reminder.

I just switched from MythTV to VDR, and so far I'm loving it. I do have one issue with the EPG though: it doesn't show the SubTitle (usually the episode name).

Here's an example from my epg.data:

E 34930 1442447400 3300 0 FF
T CSI Miami
S Dude, Where's My Groom?
D Ett bröllop får en dålig start när bruden inte har någon brudgum. Ännu värre blir det när en polis hittar brudgummens två vänner fastlåsta vid varandra med handklovar i en fontän, och båda lider av allvarlig minnesförlust.|season: 8|episode: 6

The EPG title in Kodi only shows "CSI Miami" but I'd like it to be "CSI:Miami: Dude, Where's My Groom?"

Would this be possible to implement or have I missed something?

I tried latest VNSI server plugin (1.5.1) with the latest GIT version for the Kodi Addon in the Jarvis branch. What I get are the error messages at the end of this bug report. It seems like Kodi tries several times without success but for some reason finally successfully connects.
I've downgraded to 1.5.0 now and at least for now it seems like I get a connection immediately again with every try.
Does the Jarvis branch need some (minor?) update to work flawlessly with the 1.5.1 version of the VDR plugin?
Thanks in advance.
EDIT: Got the same problem again with 1.5.0... :( I really don't know why this happens. There are two clients. One directly on the VDR machine (connecting to localhost) and a second Kodi instance on my desktop. The "local version" connects immediately, my remote version sometimes shows the described problem...

12:23:19 T:139720814208768 ERROR: AddOnLog: VDR VNSI Client: Open - failed to connect to the backend (Connection refused)
12:23:19 T:139720814208768 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
12:23:19 T:139720814208768 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 1
12:23:24 T:139720814208768 ERROR: AddOnLog: VDR VNSI Client: Open - failed to connect to the backend (Connection refused)
12:23:24 T:139720814208768 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
12:23:24 T:139720814208768 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 1
12:23:30 T:139720814208768 ERROR: AddOnLog: VDR VNSI Client: Open - failed to connect to the backend (Connection refused)
12:23:30 T:139720814208768 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
12:23:30 T:139720814208768 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 1
12:23:36 T:139720814208768 ERROR: AddOnLog: VDR VNSI Client: Open - failed to connect to the backend (Connection refused)
12:23:36 T:139720814208768 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
12:23:36 T:139720814208768 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 1
12:23:42 T:139720814208768 ERROR: AddOnLog: VDR VNSI Client: Open - failed to connect to the backend (Connection refused)
12:23:42 T:139720814208768 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
12:23:42 T:139720814208768 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 1
12:23:48 T:139720814208768 ERROR: AddOnLog: VDR VNSI Client: Open - failed to connect to the backend (Connection refused)
12:23:48 T:139720814208768 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
12:23:48 T:139720814208768 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 1
12:23:54 T:139720814208768 ERROR: AddOnLog: VDR VNSI Client: Open - failed to connect to the backend (Connection refused)
12:23:54 T:139720814208768 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
12:23:54 T:139720814208768 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 1
12:24:00 T:139720814208768 ERROR: AddOnLog: VDR VNSI Client: Open - failed to connect to the backend (Connection refused)
12:24:00 T:139720814208768 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
12:24:00 T:139720814208768 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 1
12:24:06 T:139720814208768 ERROR: AddOnLog: VDR VNSI Client: Open - failed to connect to the backend (Connection refused)
12:24:06 T:139720814208768 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
12:24:06 T:139720814208768 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 1
12:24:12 T:139720814208768 ERROR: AddOnLog: VDR VNSI Client: Open - failed to connect to the backend (Connection refused)
12:24:12 T:139720814208768 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
12:24:12 T:139720814208768 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 1
12:24:14 T:139720814208768 NOTICE: AddOnLog: VDR VNSI Client: Logged in at '1485001454+3600' to 'VDR-Network-Streaming-Interface (VNSI) Server' Version: '1.5.1' with protocol version '9'
12:24:14 T:139720814208768 WARNING: GetAddonProperties - Addon VDR-Network-Streaming-Interface (VNSI) Server:manuelsvdr:34890 does not support timer types. It will work, but not benefit from the timer features introduced with PVR Addon API 2.0.0
12:24:15 T:139720856172288 NOTICE: Start - EPG thread started

I am using OE builds from fritsch. pvr.VNSI is from now latest from git 902a3cd
Playback of video doesn't work at all via vnsi recording. video is not started. kodi is working in background and after some minute i am back on video selection. live tv and playback a video via filesystem is working.
http://forum.kodi.tv/showthread.php?tid=231955&pid=2281848#pid2281848
debug log
http://sprunge.us/TCDV

and picture of memory usage.
http://oi64.tinypic.com/i5vdck.jpg

if you need more info, please let me know.

I thought it was a requirement for addons to have a changelog. Apparently it's not, but I guess it would still be useful for users if they'd be able to see what has been fixed.

Hi!
I cannot build this addon on my Debian Jessie machine with Kodi 17.0b1.

pvr.vdr.vnsi did not match any of the supported addons. A list of supported addons can be viewed by building the 'supported_addons' target. Addon definitions are loaded from ADDONS_DEFINITION_DIR (/usr/local/src/xbmc-17.0b1-Krypton/project/cmake/addons/addons).