2013-07-08, 16:31
Well technically I'd call this both a bug and a feature request!
(2013-07-19, 22:49)MilhouseVH Wrote: Remove the <animation> tag, as it's this that rotates the current image through 360 degrees, and then replace the current "busy.png" with something more suitable as a static image.MilhouseVH,
Although to be honest I don't see the point of an entirely static image as you may as well have no image at all. Ideally you just want something that still indicates progress, but hammers the GUI far less than the current version.
<algorithmdirtyregions>2</algorithmdirtyregions>
(2013-07-20, 18:27)wyrm Wrote: While doing as you suggest might fix the problem, the underlying problem is not the busy spinner as such but the fact that the Dirty region code is updating the entire screen for each frame of the animation. If you change the dirty region algorithm type in the adavancedsetting.xml file to use the only update the part of the screen that has changed algorithm (from memory type 2, sorry tried to check the wiki for this but it's down at the moment). So add this line to the as.xml fileThis is not supported on the Pi (or ATV2 or any GLES platform as far as I know).
PHP Code:<algorithmdirtyregions>2</algorithmdirtyregions>
The default setting for this is to update the entire screen anytime there is any change, so in the case of the spinner, update a small part of the screen or update the whole screen. I'm sure you can guess which would be quicker (and less load on the Pi).
(2013-07-20, 18:27)wyrm Wrote: There is maybe another way to reduce the load on your system (that is if you are running a very recent build of Gotham), that is to reduce the maximum frame rate in the as.xml file. The XBMC GUI is rendered in a big game loop, so if you reduce the number of times the Gui loop is executed, your CPU load must go down.There is a PR, but it's not accepted (and I doubt it will be). (https://github.com/xbmc/xbmc/pull/2265 )
(2013-07-20, 18:27)wyrm Wrote: As to replacing the animated image with a static image, how do you tell if your Pi has hung instead of just busy off doing something?XBMC on my Pi doesn't really hang, so this doesn't concern me.
(2013-07-20, 18:27)wyrm Wrote: The default setting for this is to update the entire screen anytime there is any change, so in the case of the spinner, update a small part of the screen or update the whole screen. I'm sure you can guess which would be quicker (and less load on the Pi).I believe the default was changed to the be most efficient value some time ago. As you say the Wiki is down right now so I can't confirm but I'm pretty sure that once the Dirty Regions code was well proven it became the default.
(2013-07-20, 18:27)wyrm Wrote: There is maybe another way to reduce the load on your system (that is if you are running a very recent build of Gotham), that is to reduce the maximum frame rate in the as.xml file. The XBMC GUI is rendered in a big game loop, so if you reduce the number of times the Gui loop is executed, your CPU load must go down.
(2013-07-20, 18:27)wyrm Wrote: As to replacing the animated image with a static image, how do you tell if your Pi has hung instead of just busy off doing something?