Posts: 6,810
Joined: Jul 2010
Reputation:
198
you said you played with and without the entire advancedsettings file. what else is in this file?
Posts: 6,252
Joined: Jun 2009
Reputation:
115
da-anda
Team-Kodi Member
Posts: 6,252
2017-06-20, 14:13
(This post was last modified: 2017-06-20, 14:15 by da-anda.)
too bad you can't see the CPU clock speed on the linux task manager so that we could be sure it's not related to speed stepping. I'm not a linux guy, but I recall one was able to configure certain modes for the CPU govenor. If that's the case on your setup, could you set it to "max performance" or alike, so that speed stepping is basically disabled and redo the above test?
Please also make sure to wait at least a minute after startup of Kodi before you do the test, because some add-ons could run background tasks that eat up CPU. Best probably might be to temporarily use a clean Kodi profile by renaming your userdata folder, reconfigure HW acceleration as needed and then run the test with and without an advancedsettings file with only the dirtyregion setting. Thanks.
Posts: 82
Joined: Oct 2013
Reputation:
5
I have no idea how to do such a thing nor if it can be done, browsed around a bit but found nothing useful. But there's really no point, if it is "nonsense" then it is what it is.
If that's not the problem/solution then theoretically you still have a solution, if things worked great in Kodi 16.1 and now work badly in 17.x and newer, at least theoretically all you gotta do is undo the changes made and it all should work great again.