OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166) +---- Thread: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) (/showthread.php?tid=231092) Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - rob77 - 2015-07-13 Hi Just a little bug with the latest build. Pop up notifications now have no text. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - charlieroot - 2015-07-13 (2015-07-13, 01:26)rob77 Wrote: Hi Same here, started with #0711. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-13 (2015-07-13, 01:26)rob77 Wrote: Hi (2015-07-13, 02:01)charlieroot Wrote: Same here, started with #0711. Thanks both - are you referring to the Kai Toast notifications (notifications that appear in the bottom right corner of the screen, in Confluence)? Would it be possible to upload a screen shot, or describe a really easy way to reproduce? I rarely see notifications... Edit1: OK I can see the problem, running "texturecache.py notify ThisIsTheTitle ThisIsTheMessage 5000 warning" should display a Kai Toast (notification) with a title and message, but there is no text. Edit2: Seems to be due to PR:7323 - there's a mention of it there already so hopefully fixed soon. Edit3: Should be fixed by PR:7491 - I'll include this in the next build if it's not already merged. Thanks for reporting. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-13 @popcornmix: this is the commit that causes the high CPU load in Music > Files in build #0304: test: fix for dirty rendering with skipped updates If the above commit is reverted from #0304, the high CPU load in Music disappears. Leave it in, and there is high CPU load. This "test" commit remained in newclock4 until build #0407, at which point the "test" commit appears to be merged into a separate commit: renderer: Allow gui updates to be skipped when playing video which had been in newclock4 since #0125. This second "renderer" commit subsequently merged into Kodi on 9 April (#0409) as part of PR:6898, which helps explain why we still have high CPU load in Music in current master builds even though the "test" commit is no longer around. I then tried to revert only the "test" commit from a current tip of master Kodi 16 build, but this didn't have any noticeable effect (I verified the code has been reverted from Application.cpp correctly) so maybe another change (possibly in PR:6898) is compounding this issue... The extra CPU load is definitely GUI related as mass or continuous GUI updates (eg. scrolling text) are about the only thing that sends my CPU temp through the roof, and leaving Kodi on Music > Files in a current build (or #0304 with "test" commit included) will eventually result in the RPi1 SoC temperature reaching 85C... I'll see if I can build #0409 with and without PR6898 to see if that has any effect, although it may be a little later on today. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-07-13 (2015-07-13, 08:29)Milhouse Wrote: @popcornmix: this is the commit that causes the high CPU load in Music > Files in build #0304: Thanks Milhouse - good detective work as usual. I suspect reverting the offending commit, could help audio playback cpu, but is likely to harm video playback cpu. I've pinged @FernetMenta who may be able to help find a fix for both. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Bartmaniac - 2015-07-13 Just a quick question. Everyday I download the newest build and install it. Maybe that is not necessary? Is it OK to do it every day in and out? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-07-13 (2015-07-13, 17:34)Bartmaniac Wrote: Just a quick question. Everyday I download the newest build and install it. Maybe that is not necessary? Is it OK to do it every day in and out? I update pretty much every day. I use Leopold's add-on to update easily. So there is no problem with doing this. Is it necessary? Depends why you are using these builds. If you want to help with testing, and see new features as early as possible, then sure, update every day. If you don't then sticking with a stable build may be better. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Forage - 2015-07-13 (2015-07-13, 17:34)Bartmaniac Wrote: Just a quick question. Everyday I download the newest build and install it. Maybe that is not necessary? Is it OK to do it every day in and out?No problem at all. I do the same. Sometimes I update every day, sometimes not for a week or two. To update or not depends on if it has any interesting commits (fixes, features) you like or need to have/test. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Bartmaniac - 2015-07-13 (2015-07-13, 17:41)popcornmix Wrote:I'm using these Mulhouse builds on my rpi2 attached to my Sony LCD en wired ethernet to my router. No dvb devices and no pvr stuf whatsoever(2015-07-13, 17:34)Bartmaniac Wrote: Just a quick question. Everyday I download the newest build and install it. Maybe that is not necessary? Is it OK to do it every day in and out? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - invisable - 2015-07-13 Hi Millhouse, can I ask if your still including your latest librtmp in Openelec 16 the only reason I ask is because I noticed the test build release you made on May 16 (#0516) the librtmp is slightly larger then the ones on the recent builds ? Many Thanks. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Mfleigle - 2015-07-13 (2015-07-13, 02:41)Milhouse Wrote:I was just getting to posting about the bug. Good to see it'll be fixed soon.(2015-07-13, 01:26)rob77 Wrote: Hi RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-13 (2015-07-13, 18:29)invisable Wrote: Hi Millhouse, can I ask if your still including your latest librtmp in Openelec 16 the only reason I ask is because I noticed the test build release you made on May 16 (#0516) the librtmp is slightly larger then the ones on the recent builds ? The librtmp patch in #0516 is unchanged in the latest builds, so if the librtmp.so library has changed in size that's probably due to gcc updating from 4.9.2 to 4.9.3 on 28 Jun, and possibly other dependencies that have bumped since #0516. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-13 (2015-07-13, 14:13)popcornmix Wrote: Thanks Milhouse - good detective work as usual. I've re-built #0409, and reverted PR6898, but it hasn't had any effect on the high CPU load (which is still there) so I'm going to have to go back to #0304 and review what the hell is going on and which commit is responsible - building with and without the "test" commit confirmed it to be the cause in #0304, but removing this same commit from later builds is having no effect, which is frustrating. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-14 New OpenELEC Isengard build #0713: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (a1fff18a, changelog) and tip of XBMC master (8ed51929, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - misa - 2015-07-14 Love this build but got a simple question: "5.Add image scaling algorithm which should allow better quality cached artwork (see post with details how to change current default algorithm)" When I want to use this, do I have just put <imagescalingalgorithm>bicubic</imagescalingalgorithm> in the advangesettings.xml or do I have to do more? |