Posts: 23,545
Joined: Aug 2011
Reputation:
1,108
fritsch
Team-Kodi Developer
Posts: 23,545
It is always sad - seeing capable and qualified users / developers leaving. Though I can fully understand the reasons he named. Working on kodi with a little team in the freetime while overwhelmed with feature requests by users too tired to learn up coding, emails over emails ...
Good luck with the new job / project.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 1,483
Joined: Aug 2010
Does those new development also envision multi-threading (and/or Vulcan) support?
Posts: 466
Joined: Mar 2014
Reputation:
3
Funny you mention "narrow mind" in light of what just occurred...
I'll stop there, I don't want to spoil this dev topic.
Posts: 48
Joined: Aug 2011
Reputation:
16
madshi
Junior Member
Posts: 48
To get back on topic: Would it make sense to split the video renderer (not the decoders or splitters, nor the GUI renderer, just the video renderer) into a separate binary (e.g. DLL in Windows) with a clean interface? I suppose for the other platforms it probably wouldn't bring much benefit? For Windows it might allow to use alternative external renderers (like mine) without having to fork Kodi at all. But if it's not useful for the other Platforms, it probably doesn't make too much sense?
Posts: 1,483
Joined: Aug 2010
2015-11-26, 12:58
(This post was last modified: 2015-11-26, 13:55 by Robotica.)
(2015-11-26, 08:52)FernetMenta Wrote: (2015-11-26, 02:26)Robotica Wrote: Does those new development also envision multi-threading (and/or Vulcan) support?
please elaborate on this
New era (also DX12) with many decode threads, a smart submitting thread. And something similar for rendering and other components. I know dvdplayer became a lot smarter but hé, you have the vision and you are the dev. I just read
Imagination's blog about it..
I hoped you could tell me...