OpenELEC Testbuilds for RaspberryPi Part 2 - 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 Part 2 (/showthread.php?tid=184866) 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
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
RE: OpenELEC Testbuilds for RaspberryPi Part 2 - doveman2 - 2013-12-31 Dammit, half the channels have disappeared from the EPG again. They still all show in Channel List though. I even tried reverting to build 16442 but that hasn't helped. Updated to the latest build and I was getting spammed with Connection Lost messages for TVheadend and Windows Media Service. I couldn't disable the latter so had to uninstall that but I'm still just getting the Connection Lost messages for TVHeadend and after rebooting the Windows Media service had reinstalled itself but at least I could disable it this time but it hasn't helped with TVHeadend. The TVHeadend Web portal is now not showing any DVB adapters installed It doesn't seem like the SMB path provides access to temp\xbmc.log so I have to use WinSCP to grab that, which is a bit of pain but no biggie. http://xbmclogs.com/show.php?id=103786 I thought maybe the cascaded hub bug, which appeared to be fixed, had come back so I move the USB tuner to the first half of the hub. Now I can't even get the Web portal to load http://xbmclogs.com/show.php?id=103788 I also keep finding, probably after updating, that it's changed from 1280x720 to 1920x1080 and 1280x720 isn't available, the closet being 1280x1024. I need 1280x720 as that's all my TV supports, so when switching from my LCD monitor to my TV, nothing will display if it's set to 1920x1080. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-12-31 (2013-12-31, 03:30)doveman2 Wrote: Updated to the latest build and I was getting spammed with Connection Lost messages for TVheadend and Windows Media Service. I couldn't disable the latter so had to uninstall that but I'm still just getting the Connection Lost messages for TVHeadend and after rebooting the Windows Media service had reinstalled itself but at least I could disable it this time but it hasn't helped with TVHeadend. Have you updated the Tvheadend addon (you need v4.1.1 or greater) as the recent curl/TLS change appears to have broken it (along with a few others - vdr and possibly Transmission, the latter doesn't appear to have been updated yet). (2013-12-31, 03:30)doveman2 Wrote: It doesn't seem like the SMB path provides access to temp\xbmc.log so I have to use WinSCP to grab that, which is a bit of pain but no biggie. The easiest way to get your logs uploaded is to ssh in to your OpenELEC client, then run: Code: grep -v CecLogMessage /storage/.xbmc/temp/xbmc.log | pastebinit RE: OpenELEC Testbuilds for RaspberryPi Part 2 - doveman2 - 2013-12-31 (2013-12-31, 03:35)MilhouseVH Wrote: Have you updated the Tvheadend addon (you need v4.1.1 or greater) as the recent curl/TLS change appears to have broken it (along with a few others - vdr and possibly Transmission, the latter doesn't appear to have been updated yet). With the recent build, it shows v4.0.1, so I need to update but I don't know how to. It's not prompting me to or showing any available update and I don't know where to download it from manually. Quote:The easiest way to get your logs uploaded is to ssh in to your OpenELEC client, then run: Cool, thanks I'll try that next time. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-12-31 (2013-12-31, 03:58)doveman2 Wrote: With the recent build, it shows v4.0.1, so I need to update but I don't know how to. It's not prompting me to or showing any available update and I don't know where to download it from manually. These are addons, so they're not part of the OS build. Go to addons and you should see v4.1.1 for tvheadend - if not, try refreshing your "OpenELEC Mediacenter OS Addons" repository (use the context menu). RE: OpenELEC Testbuilds for RaspberryPi Part 2 - doveman2 - 2013-12-31 (2013-12-31, 04:03)MilhouseVH Wrote:(2013-12-31, 03:58)doveman2 Wrote: With the recent build, it shows v4.0.1, so I need to update but I don't know how to. It's not prompting me to or showing any available update and I don't know where to download it from manually. Thanks, refreshing that did the trick and it seems to be working again now RE: OpenELEC Testbuilds for RaspberryPi Part 2 - doveman2 - 2013-12-31 Regarding the resolution, according to this page http://elinux.org/RPiconfig hdmi_group=1 hdmi_mode=4 should give me 720p@60hz but it's giving me a corrupt bootscreen and XBMC is loading at a fixed 640x480@60hz. So I tried group=2 in case they were the wrong way round but that gives me a readable bootscreen at 640x480@60hz and XBMC at the same res, so any ideas how I force it to 1280x720? RE: OpenELEC Testbuilds for RaspberryPi Part 2 - doveman2 - 2013-12-31 I was mistaken about the EPG working now I've upgraded TVHeadend as well. A couple more channels appeared but a lot are still missing. The channels list shows them all though and I can start them from there OK. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Doktor-X - 2013-12-31 Code: OpenELEC:~ # uname -a
this is modify MilhouseVH release that have dvdplayer enable so that you can use software decoding Code: https://www.dropbox.com/s/kw1j8jfdbxkyc14/OpenELEC_Gotham-RPi.arm-devel-20131230182856-r16752-gd55ec77.tar thanks MilhouseVH for building instructions and scripts RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Trickname - 2013-12-31 Quote:New OpenELEC Gotham build: #3012 Live tv works perfect here using Dvbviewer. Only think is canĀ“t get guisound working. I noticed system-audio output is set to analog as default but there is still no guisound when switching to hdmi. Seems that curling in plugins is faster. thx for this build RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2013-12-31 (2013-12-31, 04:56)doveman2 Wrote: Regarding the resolution, according to this page http://elinux.org/RPiconfig Possibly your monitor's edid doesn't report support for that mode, also add: hdmi_ignore_edid=0xa5000080 You could also try: hdmi_group=2 hdmi_mode=85 which is the DMT (monitor style) version of 720p. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-12-31 New OpenELEC Gotham build: #3112 (obsolete) Code: rpi512:~ # uname -a Based on tip of XBMC master (877b4249f2) and tip of OpenELEC master (72606141ac) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi Part 2 - extension23 - 2013-12-31 milhousevh - here is the paste of the debug log: http://sprunge.us/WPbQ I disabled CEC so those messages do not show up in the log. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-12-31 Loading 2686 movies might explain why it takes 18 seconds - when you said it was slow I kind of assumed you were talking about a small-ish number of movies. 2686 is actually quite a lot and given the nature of how XBMC is designed it means an awful lot of processing for the Pi, so the time taken is actually fairly reasonable. Code: 11:51:42 T:3043635200 DEBUG: ------ Window Init (MyVideoNav.xml) ------ It used to take a lot longer than this just to load the fileitem cache before Ben and popcornmix optimised the processing. It's possible that once the cache is loaded there is still a lot of number crunching (parsing) that has to take place, the question is whether all of it is absolutely necessary (possibly not, but identifying and eliminating the unnecessary cruft is a slow and tedious process). As a reference, on my Pi (1GHz ARM) it takes about 4 seconds to cache 650 movies. So 9-10 seconds to cache 2686 movies is about what you might expect, or actually slightly better. I should also point out that the build you are testing does not have all of the library performance optimisations (these are the "newclock3" patches you may see me and others referring to). This may explain the 8 second delay you are experiencing having loaded the fileitem cache, but before images are displayed: Code: 11:51:51 T:3043635200 DEBUG: -- items: 2686, sort method: 0, ascending: true On my Pi with 650 movies, there's a one-off extra delay of about 2 seconds when I first enter the movie library between the fileitem cache being populated and the first image displayed. Re-entering the movie library is usually much quicker at under 4 seconds before the first image is displayed. When you re-enter the Movie library, do you experience the same kind of delay? Try a Gotham build that has all the newclock3 performance patches. Other than the extra 8 second delay which may be resolved by existing patches, overclocking your Pi will help to display the movie library more quickly. If you want really fast library access times with a large-ish library then x86 is likely your only option until XBMC improves the way it handles library access so that it can scale better as the library size increases. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - extension23 - 2013-12-31 I thought that may be the case. I used to have the same issue with my large library even on my faster processor systems under openelec, but sometime around 2.95 or 3.0 the issue went away and everything started loading within about 2 seconds. Not sure if some library optimizations happened to the main code around then or not, but that was a refreshing change when it did happen. Overall I am amazed at how responsive the rpi is with the optimizations everyone has been doing. Other than the library taking a little while to load, the overall responsiveness once in the library isn't that far off from my much faster systems. I even tried Aeon Nox on it today and it handled it surprisingly well. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2014-01-01 (2013-12-31, 11:46)Doktor-X Wrote: this is modify MilhouseVH release that have dvdplayer enable so that you can use software decoding So, have you been able to play any video with dvdplayer that keeps up? |