Some info here now about a test build with HEVC support here
http://forum.xbmc.org/showthread.php?tid...pid1803928
(2014-09-29, 13:58)Willem55 Wrote: [ -> ]It is a user related issue when complaints about these bugs becomes a finger pointing game between android and xbmc code changes.
There will be a lot of users out there experiencing RK3288 SoC based Android media players and XBMC for the first time and they will be given the runaround by vendors with regards to these issues.
Yes you are absolutely right about that, but as a FOSS software project XBMC/Kodi will probably always suffer from fly-by-night operations and resellers just looking to make a quick buck by selling boxes pre-installed with XBMC/Kodi without offering first-line support themselves, and any users who get fooled into buying such devices will almost always be left to rely best-effort support from the community.
The main thing you have to remember here is that XBMC/Kodi is a FOSS software that runs on multiple operating systems and on multiple platforms, so you can never compare your box XBMC/Kodi installed to boxes like Ruku, TiVo, or Popbox which is manufactured by one commercial company so the end-user will always have the security of a single-point of entry for support which is either the the vendor or the box manufacturer, as they will always fully support everything that is pre-loaded on their boxes and act as single point of contact for all issues no matter where the root cause is, so the user never need to think about where to turn for support.
This is exactly why unless the person that will end up using the player a early adopter enthusiasts (that can accept and live with all the bugs) should not just go out and buy any cheap Android box online and expect XBMC/Kodi to run on it without bugs.
If the person who will be the end-user really want to use XBMC/Kodi (thus knowingly accept that it itself is not always user-friendly) but also just want stuff to work without too many bugs then they should instead go buy a box where either the vendor or box manufacturer offer first-line support of XBMC/Kodi directly to the end-user.
First-line support by vendor or box manufacturer at least means that the end-users does not come straight here to to XBMC/Kodi community forum, but instead the end-user contact the vendor or box manufacturer with any issues they have and the vendor or box manufacturer then have in-house support technicians and developers which in in turn filter that information and either solve the issue themselves or submit a professional support request upstream to XBMC/Kodi,
Pivos is a very good example of a XBMC/Kodi box manufacturer which offers first-line support with its own in-house support staff. And in the future we can only hope that more box manufactures like MiniX and Cloud Media will follow in the foot steps of Pivos and also provide good first-line support with its own in-house support staff which can directly try to help end-users with all issues and faults on their boxes no matter if the root cause is hardware, drivers, codecs, operating system / firmware or a bug in media player application like XBMC/Kodi.
(2014-09-29, 13:58)Willem55 Wrote: [ -> ]I just want to understand on what level they are made and how buggy it's going to be.
It is very complicated, again see
http://forum.xbmc.org/showthread.php?tid=204331 which again points to other threads for further questions.
History tells us that there is no firmware or software without bugs, and it is sure getting easier to blame someone else when like in this case, Rockchip is the hardware manufacturer thus responsible for drivers and codecs, Google makes the Android operating system but the box or board manufacturer are responsible for the box/board specific Linux kernel and firmware package, then XBMC/Kodi makes the media player application.
