+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Discussions (https://forum.kodi.tv/forumdisplay.php?fid=222)
+--- Forum: Hardware (https://forum.kodi.tv/forumdisplay.php?fid=112)
+--- Thread: Rockchip RK3288 SoC based Android media players and XBMC experience? (/showthread.php?tid=202924)
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - User 182116 - 2014-10-02
(2014-10-02, 13:57)Willem55 Wrote: This is getting religious..
I tend to agree with your viewpoint.
If a product can enhance it's usage in the short term by utilising external and especially free options, it makes for a better experience when it works.
Players already use codecs that are essentially sources created by others, so using the term hack is not relevant.
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - User 231261 - 2014-10-02
the Idea is to buy time for kodi developers to come up with a permanent solution as opposed to flooding new xbmc users with a non compliant forked Gotham 13 release that is already 2 updates behind.
Try and read up and understand before you assume anything and go of a rant.
Re: RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - bornagainpenguin - 2014-10-02
(2014-10-02, 14:51)Bluesmanuk Wrote:The problem is that it doesn't work.(2014-10-02, 13:57)Willem55 Wrote: This is getting religious..
I tend to agree with your viewpoint.
If a product can enhance it's usage in the short term by utilising external and especially free options, it makes for a better experience when it works.
Players already use codecs that are essentially sources created by others, so using the term hack is not relevant.
By sacrificing the long term for the sake of short term expediency, you kill even the possibility of a long term solution because those who would be required to build a long term solution point to the hack you're using and tell you to fix your end of it rather than working with you to build it innate to the player. And when the OEM's player changes, you're reminded that you were using a hacked solution and so were you should expect some breakage. Since your hacky work-around requires more and more working-around it gets harder and harder not only to keep things working that sort-have kinda almost worked before, but now you're less and less able to debug because there are so many variables including this black box you have no idea what's happening inside of....
Is it painful to have to wait for things to come the right way? Maybe. Sure, I understand that but I'd rather Kodi keep thinking long term because I want Kodi to be here for the long haul. These Android OEMs pressing for short term solutions only care about us for as long as it takes to get a new device model out the door, Kodi needs to consider the entire life time of the device in its usage. Plus right now Kodi is the hot girl in this market.
Everyone wants to be the one to take Kodi to the dance. People are buying these devices on the strength of the killer app Kodi represents and by how well Kodi can perform on them. That's the whole reason why we're even seeing them building versions of XBMC to put on the device, because it's a selling point. This means that this is not the time to be making concessions, but rather time to be demanding them. Personally I consider asking people to conform to the agreement they made when obtaining the code to be a fairly light requirement to be making on Kodi's part. They could be demanding logo usage, branding requirements, profit sharing agreements, etc. Instead all they're saying is "Hey work with us here, obey the terms of the license. It's a good thing that will in the end benefit both of us and make less work for you."
If that sounds religious, then there are worse religions.
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - User 231261 - 2014-10-02
you missed the option where the chip manufacturer is working with kodi developers to get support inside the kodi playback engine.
Some fly by night manufactures are shipping with a forked Gotham 13 dead end solution and some others are investigating calling the external playback engine that has proven to playback what kodi now can't.
Stop thinking black or white, this or that. but think timeline: now bad fork...then workaround... then team kodi solution..
Good luck in demanding the market to sit on it's arse... have a good look at what they done to the "hot girl"...... it's not pretty and has nothing to do with having a dance..
But if the manufacturers that want to be compliant can't do "the right thing" with using playercorefactory.xml my guess is we'll see more forked solution until kodi catches up.
And users left in total confusion... on the many faces of xbmc...
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - Ned Scott - 2014-10-03
(2014-10-02, 15:24)Willem55 Wrote: the Idea is to buy time for kodi developers to come up with a permanent solution as opposed to flooding new xbmc users with a non compliant forked Gotham 13 release that is already 2 updates behind.
Try and read up and understand before you assume anything and go of a rant.
There's nothing to buy time for. We spent a hell of a lot of time and effort to trademark a new name to prevent companies from using the name "Kodi" for custom forks. Trademark law exists to prevent such confusion with users. Anyone who makes a custom version of the software and uses the name "Kodi" must have the approval of the XBMC Foundation or they will face legal action.
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - nickr - 2014-10-03
So why aren't the innumerable GPL infringers facing legal action for breach of copyright?
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - User 182116 - 2014-10-03
So does the name change and trademark close the open source nature of the software?
Re: RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - nickr - 2014-10-03
(2014-10-03, 05:41)Bluesmanuk Wrote: So does the name change and trademark close the open source nature of the software?No of course not.
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - nickr - 2014-10-03
To enlarge, a trademark is quite different to copyright. Kodi is still open source, which means anyone can take the source, modify it and release PROVIDED they provide the source code.
However the trademark means that no one can market something as "kodi" without a licence form the foundation.
An example: Redhat is a commercial linux solutions provider. As it is built on the linux kernel and other open source code, people are free to change it, distribute it, etc. However they are not able to use the Redhat name. Hence CentOS - 100% compatible, uses the same source, given away free, but can't call itself Redhat.
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - User 231261 - 2014-10-03
(2014-10-03, 03:12)Ned Scott Wrote:(2014-10-02, 15:24)Willem55 Wrote: the Idea is to buy time for kodi developers to come up with a permanent solution as opposed to flooding new xbmc users with a non compliant forked Gotham 13 release that is already 2 updates behind.
Try and read up and understand before you assume anything and go of a rant.
There's nothing to buy time for. We spent a hell of a lot of time and effort to trademark a new name to prevent companies from using the name "Kodi" for custom forks. Trademark law exists to prevent such confusion with users. Anyone who makes a custom version of the software and uses the name "Kodi" must have the approval of the XBMC Foundation or they will face legal action.
Nobody is using the name kodi here... as to Trademark law the Term "Free" in FOSS automatically excludes a lot of what the Trademark law is about as they can bundle "Free stuff" with their products.
But if you're right that there is nothing to buy time for and you got it all covered then slap an injunction on all player sales that are bundled with with the forked xbmc so that the manufactures who want to be compliant don't lose customers to those fly by night companies and new xbmc users don't get shafted with half baked solutions when they think they are getting the real deal.
Word of advice... Don't burn money on lawyers as that will cost a hundred times the money that using payed developers would cost to solve this issue.
BTW it's not Team kodi that needs to buy time here it's the kodi developers engaged by Rockchip as Rockchip needs to take ownership of this mess.
Now... if they supply their honest manufactures with a working playercorefactory.xml solution calling their Rockchip mediaplayer for HEVC and 4K to work within kodi I think that's a good workaround up and until such time as HEVC and 4K become part of the kodi player.
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - nickr - 2014-10-03
Quote:as to Trademark law the Term "Free" in FOSS automatically excludes a lot of what the Trademark law is about as they can bundle "Free stuff" with their products
Willem55 you talk absolute shite. GPL does not allow illicit use of trademarks.
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - User 231261 - 2014-10-03
you know what talking shite is:
Saying the law does not allow illicit use....... duh.. sort of obvious
Stop selective out of context quoting please
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - nickr - 2014-10-03
When and where did you get your law degree?
Kodi trademark is owned by XBMC Foundation. The fact that XBMC Foundation provides GPL2 software does not create a trademark license for the name Kodi. Just because Kodi source is release under GPL2 does not just allow the Kodi name to be used by anyone.
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - User 231261 - 2014-10-03
1979 University of Amsterdam and you?
these fork go under the name xbmc..... not kodi... minor detail.
RE: Rockchip RK3288 SoC based Android media players and XBMC experience? - nickr - 2014-10-03
1986 University of Canterbury - and been in practice ever since.
And what you say about FOSS excluding trademark law is just bollocks. Ask Redhat.