Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
Jep - there are differences already. Also between GL and GLES and even on windows between DXVA Rendering and other cpu bound data copying and display. Same for deinterlacing algorithms btw. If something is DXVA only - it's also fine - as it would stick in "that component".
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
I will think about that - perhaps I am back next year perhaps not. For the time being - have fun and get your projects going. I need a break and that I will take exactly now.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 19
Joined: Oct 2015
Reputation:
0
I have been a few days away and have come back to see what has happened. I'm a little confused to be honest because as quite a new user of kodi + DSplayer, I did not understand there was a situation brewing.
If you take the apparent communication issues on the personal level away that seem to have caused this situation then I feel the problems can be solved. I have to say this is not the first time I have seen situations like this in projects that have different branches and it certainly will not be the last.
Because kodi is a multi platform software I can fully see why there would be hesitation to adding DSplayer into the main tree. What we have to remember however is that multiplatform software normally has different goals than a platform pacific application. They normally want the same experience over all platforms. The result is multiplatform software is not as good as software designed for a single platform. This is just the way it is. Sometimes what happens is branches do get merged back into the main tree and then across other platforms but not always. In this case we know the video quality offered by kodi with DSplayer is far greater than kodi with DVDplayer because of its use with madVR for example.
This is where I'm confused, was it always the intention of aracnoz to try and get his DSplayer into the main tree? I personally don't see an issue that its not but at the same time I can understand it being very frustrating if there are communication problems between the devs of the main tree and the branches. Normally these are because of a different mind-set on the goal of the project. If your writing multiplatform software your just going to have to accept that someone can come along and do something better for a single system. One the other side devs for a single system need to understand their are other things to take into consideration which can limit how good the software can be over all systems.
For me personally, I would have never discovered kodi with dsplayer if it did not have madvr support. But I have to thank both aracnoz and the main kodi devs for making it possible. I hope you guys can work something out at some point in the future.
Raz
Posts: 5,246
Joined: Jul 2012
Reputation:
339
Been following this and it seems kind of a typical problem in open source software development. You have people who are unhappy with features or development pace and so fork the project. Of course there is going to be some defensiveness about the the main project. The viability of the fork depends on the developer base supporting it. In this case it was a one man show. That simply isn't sustainable, especially as the dev was working hard to keep the fork aligned with mainline.
The dsplayer fork is on github. ISTM the reasonable approach is to go back to Kodi 11.2 as the starting point and maintain the fork from there. But that requires devs who are interested in this.
scott s.
.
Posts: 3,823
Joined: Feb 2014
Reputation:
224
2015-11-26, 22:55
(This post was last modified: 2015-11-26, 23:01 by Warner306.)
@ fritsch & Martijn
Thank you for your posts in this forum. My labelling of your response as "cold" had more to do with a lack of communication and apathy towards aracnoz more than anything. Users in this forum had been wanting a response from Team Kodi from the very beginning. I believe this is the first time its happened in the Official DSPlayer forum. I think aracnoz's motivation to merge this project had as much to do with pride in what he created as a desire for help.
Its seems likely aracnoz badly wanted some help, so he wasn't always required to be available for each release date. If you don't have the horses to do it, I can accept that. I've already made plans to move on because these things happen with open source software. The hope remains yet another developer(s) will pick up the project in the future.
I'd say to other DSPlayer users to respect aracnoz's decision and hope someone else finds this project exciting. The revival of DSPlayer has happened many times. Having at least one Linux developer see the error of their ways and make their way to Windows would be nice. Kodi development sounds very unbalanced.
Trent.
Posts: 590
Joined: Jun 2014
Reputation:
6
For me, English is not my native language, it is very difficult to pass judgment on what has happened in recent days on this thread, actually are quite disappointed by Kodi team to this project that does not know to do as integration in Kodi, I close with an aphorism ... hoping that it is interpreted in the right way.
... Sometimes good things fall apart so better things can happen (Kodi DSPlayer)
Greetings.