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) - maxodolo - 2015-08-05 (2015-08-05, 19:35)popcornmix Wrote:(2015-08-05, 19:33)maxodolo Wrote: Because for me the symptoms you describe are happening, when OMX is deactivated and MMAL is activated. Tried #804 today and had the same problems. Definitely not fixed for me. Max Re: RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-08-05 (2015-08-05, 19:45)Patrics83 Wrote: No crash log have been generated. Kodi just restarts. Maybe it's an out of memory situation due to all the recursion - after Kodi has restarted, run "journalctl --no-pager | paste" and paste the link. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-08-06 New OpenELEC Jarvis build #0805: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (15ce9459, changelog) and tip of XBMC master (9628f606, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - J_E_F_F - 2015-08-06 with all the cool stuff you guys do to the test builds, why is there no option to change the SSH password yet? Re: RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-08-06 (2015-08-06, 01:38)J_E_F_F Wrote: with all the cool stuff you guys do to the test builds, why is there no option to change the SSH password yet? Because you haven't written it yet? If a pull request existed with that feature I'd include it. Until then, you can disable password access and rely on public/private keys for authentication, this is much more secure than any password you may set. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - MarkT - 2015-08-06 When playing a broadcast MPEG2 stream on #0805 I can see in htop that the Kodi main process (w/ threads included) is guzzling up 35-45% of a core. Looking at kodi.bin's threads I can see the main culprit is ActiveAE i.e. the audio engine. Other threads are 1-3%. Now this is an MPEG Layer 2 audio stream at 192 kbps. The RPi2 has a MPEG2 hardware license. Any quick methods to push this CPU guzzler down to say 10%? Or figure out what it is doing? The vdr.bin process requires about 12-20% of a core, which is consistent with a non-accelerated software CSA decrypter using libdvbcsa. There are patches by glenvt18 for libdvbcsa though that utilize the NEON instructions. The claimed speedup of 2.63x would push this process below 10% and allow even fat satellite HD streams with 25 Mbps data rate be decoded at 1/3 utilization of one core. If that ain't awesome then I don't know what is. ;-) My own oscam build with a smartcard on USB card reader basically draws no CPU. Haven't tried an HD stream yet, will need to borrow a smartcard from a friend. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Patrics83 - 2015-08-06 (2015-08-05, 22:58)Milhouse Wrote:I will do that when I get home from the vacation.(2015-08-05, 19:45)Patrics83 Wrote: No crash log have been generated. Kodi just restarts. Maybe the gpu_mem split is problem? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - ivota - 2015-08-06 Problem with reproduce movie .mp4 (log line 954) http://pastebin.com/fLeX4a5e RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-08-06 (2015-08-06, 10:28)Patrics83 Wrote: Maybe the gpu_mem split is problem? 384MB is fine, Kodi really shouldn't be running out of memory on a Pi2 unless something has gone horribly wrong... RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-08-06 (2015-08-06, 11:09)ivota Wrote: Problem with reproduce movie .mp4 (log line 954) Can you upload a debug log (or provide the mediainfo for the file, or better yet a sample?) RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - ivota - 2015-08-06 http://pastebin.com/0gSAQmJC RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - MrNice - 2015-08-06 (2015-07-28, 19:35)MrNice Wrote:A bit different with build #0805;(2015-07-27, 19:58)MrNice Wrote:(2015-07-27, 13:58)popcornmix Wrote: Install the Leopold OE updater addon and find the first build with the problem. You can probably do this in fifteen minutes. With this information you are much more likely to get a fix. Good files have CPU usage (kodi.bin) around 10% Bad files have around 60% I recall that there is no activity, no play. I run a RPi1 512. (2015-08-03, 18:20)MrNice Wrote: I use a RPi1 with a USB Flirc (it simulates a keyboard) and the AVR remote.Still the same Log done from ssh as screen freezes: http://sprunge.us/VjcO RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-08-06 (2015-08-06, 07:55)MarkT Wrote: The vdr.bin process requires about 12-20% of a core, which is consistent with a non-accelerated software CSA decrypter using libdvbcsa. There are patches by glenvt18 for libdvbcsa though that utilize the NEON instructions. The claimed speedup of 2.63x would push this process below 10% and allow even fat satellite HD streams with 25 Mbps data rate be decoded at 1/3 utilization of one core. If that ain't awesome then I don't know what is. ;-) Presumably you're referring to these commits. Unfortunately these commits don't apply cleanly on the version of libdvbcsa being used by OpenELEC as it appears glenvt18 has applied additional changes to master, so these also need to be added to OpenELEC. Without any sign of these commits being pushed upstream (and the NEON performance stuff still in a development branch) it's pretty much a non-starter for upstream OpenELEC. Just for the hell of it, I've uploaded a vdr-addon that includes the above glenvt18 commits (plus a build patch to enable NEON/SSE2) - give it a try, let us know what difference it makes. If the changes are positive, try to get glenvt18 to push his commits upstream. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - MarkT - 2015-08-07 (2015-08-06, 15:55)Milhouse Wrote: Presumably you're referring to these commits. Unfortunately these commits don't apply cleanly on the version of libdvbcsa being used by OpenELEC as it appears glenvt18 has applied additional changes to master, so these also need to be added to OpenELEC. Looks like we did work in parallel while forum was down. I also ported those patches and recompiled vdr. My imho better libdvbcsa package.mk which will also enable MMX/SSE2/SSSE3 on x86 if available in the project: Code: PKG_NAME="libdvbcsa" The patch itself libdvbcsa-1.1.0-rff.patch is too big (1.4 MB text) so can't be included here. Page me if interested. ZIP 300 KB. Of course I did benchmark cpu time as shown by htop with 120 seconds of ~2 Mbps video each. Focus was on the "device 1 receiv" receiver thread of vdr.bin, which handles decryption. Code: libdvbcsa 1.1.0: TLDR; CSA decryption speed using NEON instructions has doubled. Do legst di nieda is a saying where I live for such cases. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Mfleigle - 2015-08-07 Is there anyway to remove the pvr manager? I have all the pvr addons disabled, and still see "PVR Manager Is Starting Up" on boot. |