2019-08-11, 08:50
(2019-03-25, 21:56)FernetMenta Wrote:(2019-03-25, 19:21)ashlar Wrote:Again for clarity and other readers who might come across this in future. An open source project like Kodi won't make itself dependent on a closed source library like madVR. That means that the one and only option to make madVR available in Kodi is via binary addons.(2019-03-24, 22:51)FernetMenta Wrote:Ok, thank you @FernetMenta. Did I understand uncorrectly what @davilla meant with "One would have to extend the binary addon interface to support it."?
I did not say this and again this it not true. If madVR is desired as a renderer for Kodi, binary addon is the way to go.
My understanding was that there is currently no way for such a binary addon to be created unless Kodi devs worked on their side to create the proper "environment" for it.
Right, currently there is no binary addon interface for external renderers. But such an interface can be created like it has been done for other purposes too. Everybody can be a Kodi dev. That means that everbody who wants to wrap madVR into a binary addon can also extend Kodi's external interfaces. A lot of v18 features like videobuffers support this now. That means it has never been easier to create external renderers. But still a lot of work ahead though.
Quote:devs have sacrificed quality over platform proliferation
What a pity, isn't it?
(2019-03-24, 04:46)davilla Wrote: Sorry to confuse. I mean since by-pass rendering has been removed in v18, the option of doing what you want with a by-pass renderer is also not possible with v18.
Hi all,
I haven’t looked - but this exchange from here:
https://forum.kodi.tv/showthread.php?tid=335218
To me means that it would be not possible to merge Dsplayer into 18. The only way forward seems to be extend the binary add on for Kodi and the hook madVR into that. Certainly doesn’t seem like a small job, and to me the fact that the current method appears to have been shut down is the reason we haven’t seen a updated build.
Glenn