How to compile vdr + vnsiserver from source

(2015-03-07 00:20)FernetMenta Wrote: you use strange expression for the various components, hence it is hard to follow what you mean. we have the VNSI addon which is a addon loaded into Kodi. And we have the vdr-plugin-vnsiserver plugin which is loaded by vdr. can you rephrase your question using these terms.

Sorry for the strange expressions. I'm a little bit confused as well, since I'm on Openelec single seat now and it uses add-on (including the server and VNSI-plugin). I will try to show what I'm using at the moment:

Openelec-> vdr-server add-on as service -> vdr-vnsi plugin as PVR add-on for OE (this connects to the vdr-server service add-on). This is how it works on OE.
I intend to move the server part to a dedicated small itx machine running 7/24. So I will not need the vdr-server add-on at the client OE side, as this will be located on the itx server machine.

Home server: running lets say Ubuntu Server -> here I need to install vdr + vdr-plugin-vnsiserver plugin following your guide (if I'm correct). This will enable all the clients running Kodi (including OE) to connect with the PVR plugin vnsi-client from official add-on repository, point it to the home server ip address where vdr + vdr-plugin-vnsiserver plugin is installed (Kodi wiki). I believe I have used now the correct expressions and explained my intentions.

The home server is a headless server, vdr is used only as a backend, will not be used to watch tv, but only accessed by clients running Kodi (no matter which version, OE, Linux, Windows -- all have the PVR vnsi-client as add-on available.

All the plugins, configuration files, etc will be located on the home server.

I really hope that I was able to summarize this now correctly using regular expressions.

Step 9 is one of the major reasons why I don't like any distributions of VDR. Most of them come with an ancient system V script which ignores startup sequence of tv cards. They just provide a run script launched by a init.d script. I prefer upstart and systemd for future systems.

I installed all these, and I had to compile Tntnet and Cxxtools which went fine.

Then I compiled and installed the plugins, that also went fine. Copied Live directory from the source to vdr/Plugins/ again, as per the readme of live.

I added -P live to runvdr template. Here comes the tricky part. Once I reboot the server, VDR will not run, it gets into an infinity loop when Live plugin starts to load. Here is the part of log from syslog:

I really don't know that could be the problem and how can I fix this. Google for long, but didn't help. Any ideas for this?

EDIT: Problem solved by creating folders 'usr/local/share/vdr/plugins' and adding live folder from source of the plugin. Also added the user who runs vdr (server in my case) as owner. Now Live works, well, almost fine. Remote part is not working. However, I see something very strange now in the logs:
as vdr starts, it immediately switches to channel 1 in channels.conf file, that is AlJazeera English (FTA) at the moment, and later there is also an error saying Channel Locked, Recording -- however no recordings are running at all and no clients are turned on.
What can this be and how can I prevent this?