Kodi Community Forum

Hi folks,

I'll have a "maintanace window" in to weeks. Due to some itching (and failed add-ons) I want to upgrade my multiple xbmc client + mysql + vdr home installation. Besides the failed plugins and lagging behind xbmc /kodi releases I have nothing to complain. Perfect setup for me.

Most of the time the vdr backend is where I fail. Thus I want to be sure to do the right thing with regard to vdr and vnsi compatibility.

Current setup:
5 x xbmc 13.2 clients (Intel nuc & ASrock V3D Nvidia both w/ OpenElec, various Android 5.x)
1 x vdr 2.0.6 headless server with vnsiserver 1.1.0 and sundtek dvb-c stick (yavdr based)
1 x mysql server (on rpi2)

The two intel based systems are most critical. I use vdr for live TV - no recording and or timeshift. Recording - if any - via vdr-manager

My question is:
Will Kodi 16.1 (or OE 7.0) with its supplied vdr-vnsi plugin (I think it's 1.11.17) work with my 2.0.6 vdr backend and vnsiserver 1.1.0 for basic (live tv) usage?

I might be able to upgrade the vdr backend to 2.2.0 and vnsiserver to 1.2.1, too.

//
Inst vdr [2.0.6-6yavdr0~0.5] (2.2.0-1yavdr0~precise testing-vdr:12.04/precise [amd64])
Inst vdr-plugin-vnsiserver [2:1.1.0~git20140518-7d4aa813cc-0yavdr1~precise] (2:1.2.1~git20150208-f2175ba-0yavdr2~precise testing-vdr:12.04/precise [amd64])
//

Though experience on my side shows that this will be a few ours of additional work ... and I most likely will fail. After that I have another few hour of a new yvdr setup ...

In case I have to do the new backend setup (2.2.0 >) upfront will the exiting xbmc 13.2 supplied vdr.vnsi plugin (1.9.8) work with vnsiserver 1.2.1?

Thanks

Hi again,

well, maybe too much text and gossip ... here again my two questions:

Will KODI 16.1 vdr plugin (1.11.17) work with vdr-backend 2.0.6 (vnsiserver 1.1.0)?

Will XBMC 13.2. vdr plugin (1.9.8) work with vdr backend 2.2.0 (vnsiserver 1.2.1)?

Thanks for your help - highly appreciated.

VDR 2.0.x is rather buggy. Don't use this version.

Danke FernetMenta!

So I'll perform a VDR server upgrade first. 2.2.0 is ok? I expect that my 13.2. clients won't connect against the provided 1.2.1 vnsiserver, right?

btw, I did not have any 2.0.6 issues for ~ 2 years. But yes, I hear what you say

edit: I checked stable-vdr at yavdr lauchpad and there is vnsiserver 1.3.1 (vor vdr 2.2.0) in case I go for a complete yavdr reinstall. vdr-testing is more or less the same ATM. I don't expect any (vnsi protocol) backward compatibility with my old 13.2. clients

vnsiserver should be backwards compatible but I have never tested connecting such an old client.

I'll provide feedback - for whatever use - as my vdr backend will be upgraded / reinstalled first.

vdr upgrade done. No major incidents and nothing to reconfigure. vdr is now 2.2.0 and vnsiserver is 1.3.0 (whereever this version came from)

Good job FernetMenta: Even (?) with ancient vnsi client 1.9.8 it's working. That's what I call futureproof ,) Seems that the channellogos are gone ... but I dont't care. kodi incoming.

These three warnings and the single error msg doesn't seem to have an effect at all


now the xbmc to kodi stunt ...

btw, FernteMenta thanks for taking care and your support on PVR, vnsi and all the other stuff.

Well, all clients on kodi 16.1. I did not expect this outcome ... All HD channels won't tune/stream to kodi. SD is fine. This behavior is on all clients (linux and android) with two different vnsi-plugin versions (1.11.16 and .17)

VDR live (HD and SD) works. vdr log did not show anything useful (some: ERROR: AddOnLog: VDR VNSI Client: ReadSuccess - failed with error code '997'). Nothing specific on client side, too. Will have a log gathering session this week.

I hardly remember but this smells like an issue with priority. check priority setting of vnsi pvr client. change to -1 or 0

I did /checked this cause it was mentioned here on a few occasions. Changed it back and forth a few times, just to be sure, to <= -1 never to 0 ... will check with 0 too upfront the Krypton testdrive you recommended here ( http://forum.kodi.tv/showthread.php?tid=...pid2339946 )

Again - on topic - additional kudos for keeping vnsi this compatible (like (13.2) 1.9.8. vnsi-client <=> 1.5.0 vnsi-server)

0 did it. changed prority from -1 to 0 and ... woo hoo, channel switching works. Will check with other clients later and well, that's so easy

FernetMenta, you remembered right. Maybe I missed the 0 in the other threads I checked.Thanks again for your support and help. And besides I might check krypton, too.