PVR API changes Kodi 18

[debutanker]

Will try this ---> https://github.com/xbmc/xbmc/pull/12791 !
Thanks ksooo!

[debutanker]

Hi @Oberon,

have you already had the time to look into the new API changes ---> https://github.com/xbmc/xbmc/pull/13228 ?

Many thanks and happy new year everyone
debutanker

[Oberon]

No, not yet. The work is planned for the next week.

[debutanker]

Many thanks for the information! Its 2018, so "make haste slowly"....

[Siutsch]

Something new here?

[Oberon]

No news at the moment.
The changes in API very fresh and very substantial. There are several things that Kodi team has to fix before we can proceed.

[ashley]

Hey @oberon, do you think the recent API changes with Kodi will address the various timeshift buffer issues using dvblink and kodi, or should we rather wait for your new rework of the dvblogic stack which you said the beta of which should be available by end jan.?

There still seems a bit of a disconnect between team Kodi and dvblogic and a possible lack of understanding around tv transmissions on team kodi from the snippets I read.

Hats off to everyone though as these issues are far from trivial, but how come set top box makers can resolve all these issues so the end user doesn't need to worry?

[Oberon]

I really do not know.

The PVR interface in Kodi becomes more and more complex and more difficult to support for backend developers.
It is mainly because Kodi PVR developers use TVHeadend as their primary backend, which is most advanced among all others and delivers many low level features, which others do not do.

We will wait first a bit until it new functionality stabilizes to understand what exactly we would need to change.

[debutanker]

[...]
There still seems a bit of a disconnect between team Kodi and dvblogic and a possible lack of understanding around tv transmissions on team kodi from the snippets I read.
[...]

Thats the essential point for me - like in a good marriage, only active communication will do the trick....

[ashley]

hey @Oberon, any news of the new dvblink product you were working on which may address some of these short comings, which was due in beta by end Jan 2018?