v17 LibreELEC Testbuilds for x86_64 (Kodi 17.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: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52) +---- Thread: v17 LibreELEC Testbuilds for x86_64 (Kodi 17.0) (/showthread.php?tid=269815) 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
|
RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - fritsch - 2016-08-25 (2016-08-25, 22:21)kelsdogz Wrote:(2016-08-25, 17:14)kelsdogz Wrote: Is there any way to force HW decoding? Quote:16:10:05 10.383188 T:139818767374400 NOTICE: GL_RENDERER = Mesa DRI Intel® 965GM You are kidding me? This device has no hw decoding support at all. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - kelsdogz - 2016-08-25 (2016-08-25, 22:55)fritsch Wrote:(2016-08-25, 22:21)kelsdogz Wrote:(2016-08-25, 17:14)kelsdogz Wrote: Is there any way to force HW decoding? Sorry my ignorance! Be gentle..... Trying to figure out what changed from 16.1 to cause my cpu usage to go up on 1080 playback on same system with 17.0 Thought maybe I had HW decoding that wasn't being used. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Milhouse - 2016-08-26 New LibreELEC.tv Krypton build #0825: Generic (Supercedes previous build) Code: # uname -a Based on tip of LibreELEC.tv master (20e8843a, changelog) and tip of XBMC master (23efa213, changelog) with the following modifications:
RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - fritsch - 2016-08-26 (2016-08-25, 23:52)kelsdogz Wrote:Will look again tonight. Please try a build from one week ago and use Bob deinterlacer please.(2016-08-25, 22:55)fritsch Wrote:(2016-08-25, 22:21)kelsdogz Wrote: LOG RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - kelsdogz - 2016-08-26 (2016-08-26, 07:29)fritsch Wrote:(2016-08-25, 23:52)kelsdogz Wrote:Will look again tonight. Please try a build from one week ago and use Bob deinterlacer please.(2016-08-25, 22:55)fritsch Wrote: You are kidding me? This device has no hw decoding support at all. Log from 8/19 build with Bob deinterlacer. http://sprunge.us/OWBD RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - fritsch - 2016-08-26 And now with v16 - same use case, please. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - kelsdogz - 2016-08-26 (2016-08-26, 15:01)fritsch Wrote: And now with v16 - same use case, please. Log using 16.1 with BOB deinterlacing. Same machine, 1080, showing only half the CPU usage with no stuttering, smooth playback. http://sprunge.us/TCUJ RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - wizziwig - 2016-08-26 Don't want to take this thread off topic, but if any developers here are interested in helping me build LibreElec with latest Intel upstream driver code, please check this thread. Thanks. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - fritsch - 2016-08-26 I think you should go the Ubuntu route for debugging this - I can build you whatever kernel you want, after you are ready and working with: http://forum.kodi.tv/showthread.php?tid=231955 RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - jan-g - 2016-08-26 @ Milhouse/Fritsch since build #0823 my system is a bit slow. Using a Zotac ID41 (intel atom d525 with ion2). navigating the library is sluggish and the rss feed stutters. playing 1080p content is fine but the processor load seems to have more than doubled during playback, normally it totals at 60% but since @0823 it goes as high as 160% (same video) when i look at the system info i noticed that the processor speed (normally always at 1800 MHz) now goes down to as low as 225 MHz (AFAIK atom d525 has no idle states nor speedstep). going back to #0822 and all is fine again debug log #0823 - http://sprunge.us/RcXG idling for about 5 min. at system info screen after a reboot. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - fritsch - 2016-08-26 Yeah - it's from the deinterlacing changes - will hopefully be fixed until end of week. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - moontan77 - 2016-08-26 (2016-08-13, 08:10)fritsch Wrote: @moontan77: Disable VDPAU, it is not used on your hardware anyways. After next out of memory crash, please also provide dmesg | pastebinit - then we can see what the kernel does. Using memory is not an issue per se, as it works differently on linux: http://www.linuxatemyram.com/ Here is kernel log after crash - http://sprunge.us/cjHE RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - fritsch - 2016-08-26 (2016-08-26, 21:42)moontan77 Wrote:(2016-08-13, 08:10)fritsch Wrote: @moontan77: Disable VDPAU, it is not used on your hardware anyways. After next out of memory crash, please also provide dmesg | pastebinit - then we can see what the kernel does. Using memory is not an issue per se, as it works differently on linux: http://www.linuxatemyram.com/ Yeah OOM - too much memory used and nothing to swap. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - fritsch - 2016-08-26 (2016-08-26, 13:49)kelsdogz Wrote:(2016-08-26, 07:29)fritsch Wrote:(2016-08-25, 23:52)kelsdogz Wrote: Sorry my ignorance! Be gentle.....Will look again tonight. Please try a build from one week ago and use Bob deinterlacer please. The input is totally broken - no matter v16 or v17. Please verify your findings with a recording. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - moontan77 - 2016-08-26 (2016-08-26, 21:50)fritsch Wrote:(2016-08-26, 21:42)moontan77 Wrote:(2016-08-13, 08:10)fritsch Wrote: @moontan77: Disable VDPAU, it is not used on your hardware anyways. After next out of memory crash, please also provide dmesg | pastebinit - then we can see what the kernel does. Using memory is not an issue per se, as it works differently on linux: http://www.linuxatemyram.com/ Any suggestions as to what i can do? |