KODI is an award winning media center application for Linux, Mac OS X, Windows and XBox. The ultimate hub for all your media, KODI is easy to use, looks slick, and has a large helpful community. Media Management KODI supports viewing and playing a vast library of audio, video and image formats. KODI has a sophisticated library management system that allows you to organize all your media to give you quick and immediate access. Fluid Interface KODI provides a user friendly interface that's intuitive, very flexible, and easy to use. The interface is completely customizable through user-created or downloadable skins. Plug-ins and Extensibility KODI has a built-in Python interpreter that allows users and developers to write their own scripts and plugins that run inside KODI using it's own widgets and controls. It also has a built-in web server that allows it to be controlled remotely. Visualisations KODI's audio player supports many visualisations including ProjectM and Goom. In addition, it allows easy development of visualisations using a simple API. ![]() ![]() Hi, maybe someone has a clue what is going wrong here on my device. I am on a Gigabyte Fusion Board and XBMC was running nicely until I tried out the DIRTYREGION SETTINGS I created an advancedsettings.xml and entered all the parameters. Result was the picture was flickering no matter which combination I tried. As there was no big benefit in either performance or smoothness of the menue's I decided to delete the respective lines again from the XML file but the flickering stayed. So actually no matter what I try -> the flickering stays. I have a raspberry pi and have loaded the latest standalone from raspbmc.com. When using XBMC, I see that the CPU usage is always above 90%. After looking at the XBMC. GUIColorManager.cpp Use system implementation of tinyxml instead of internal implementation. GUIColorManager.h Use system implementation of tinyxml instead of internal implementation. GUIControl.cpp dirty regions: dont add invalidated, invisible controls to the tracker, 5 years. Good night, I was wondering why OpenELEC for Raspberry Pi isn't using the dirty regions setting from XBMC by default? ![]() ![]() ![]() - If I add the dirtyregions section with 0 (off) -> it flickers - If I remove the section completely -> it flickers - Regardless if there are any dirtyregion settings in the XML or the respective lines are completely deleted from the XML - the visualization shows dirty regions and the flickering is still there. Strange thing is, I can turn on and off the visualization - no matter if any dirtyregion settings are in the file and it shows a result. Just if I alter the dirtyregions parameter themselves - it does not have any effect. What am I doing wrong? Thx, Philipp.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2018
Categories |