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) - Milhouse - 2016-08-12 (2016-08-12, 15:37)axbmcuser Wrote: @Milhouse Test with stock Estuary when reporting issues against these builds. MusicOSD opens for me (although I only applied the steps from your first test, and I don't have PVR enabled). If you see different behaviour with Confluence and not Estuary (or vice versa) then report it in the relevant skin forum. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - kaiseruk - 2016-08-12 Occasionally my mce remote doesn't work after startup but disconnecting and reconnecting the usb IR receiver fixes the issue. Anyone else experience this? RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - dirtydesaster - 2016-08-12 (2016-08-12, 02:23)Milhouse Wrote: [*]Restore Intel limited range support, with limited range now the default for Intel GPUs Which is the best config, for this? Kodi > limited + TV > limited Kodi > normal + TV > normal Kodi > normal + TV> limited ? RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Milhouse - 2016-08-12 (2016-08-12, 18:55)dirtydesaster Wrote:(2016-08-12, 02:23)Milhouse Wrote: [*]Restore Intel limited range support, with limited range now the default for Intel GPUs I would have thought the first, as TV limited is considered "the norm", but maybe just use whatever looks best to your eyes... RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Hufvudet - 2016-08-12 (2016-08-12, 18:55)dirtydesaster Wrote:(2016-08-12, 02:23)Milhouse Wrote: [*]Restore Intel limited range support, with limited range now the default for Intel GPUs Kodi > limited + TV > limited = the best option, no conversions.. You can leave dithering off. Kodi > normal + TV > normal = second best option. Looks very good with dithering enabled. But 1 conversion from limited range source to full range (normal in kodi). Kodi > normal + TV> limited = WRONG. Black crush. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - fritsch - 2016-08-12 +1 Always keep in mind: This does only work that way cause of the special kernel patch OpenELEC ships. On all other distributions this won't work that way ... RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Milhouse - 2016-08-12 (2016-08-12, 22:40)fritsch Wrote: +1 Ahem, s/Open/Libre/g. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Milhouse - 2016-08-13 New LibreELEC.tv Krypton build #0812: Generic (Supercedes previous build) Code: # uname -a Based on tip of LibreELEC.tv master (54cf9f34, changelog) and tip of XBMC master (9b913533, changelog) with the following modifications:
RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - moontan77 - 2016-08-13 (2016-08-10, 22:45)moontan77 Wrote: For as long as I can remember i've had a memory leak problem with krypton builds where kodi would just freeze completely eventually and before that would happen I would see through the system info screen that one cpu was pinged to 100% while most of the 2gb ram would be used up (but after boot the CPU' usage would be in the single digits and ram usage would be ~300mb). Previous log is too big to upload to pastebin etc but this is another one from evening. Had pvr client disabled to rule that out but in the space of 3 hours, ram usage increased from about 250mb to 1050mb while just watching videos over the 3 hours. It didnt seem to be constantly going up as during the last video it was around the 1050mb any time i checked it. If anyone could have a look and see if theres anything that stands out it would be appreciated. https://paste.ee/p/EbveF RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - fritsch - 2016-08-13 @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/ RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - fritsch - 2016-08-13 @Milhouse: You can use our new "hack" to disable VDPAU by default if we are running on intel hardware automatically and disable VAAPI if not. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Milhouse - 2016-08-13 Then we should change the name of the method from ShouldBeLimited to IsIntel... I can change it later today or tomorrow. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - cypher242 - 2016-08-13 With Build #0812 music (mp3/flac) playback (local/remote (smb)) is broken. RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - fritsch - 2016-08-13 And without a Debug Log no one cares ... RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Milhouse - 2016-08-13 (2016-08-13, 12:53)cypher242 Wrote: With Build #0812 music (mp3/flac) playback (local/remote (smb)) is broken. I've just tested build #0812 playing both flac and mp3 over smb://, and don't have any problems. As per @fritsch's comment, a debug log is required. If you're sure this problem started with #0812, can you confirm the last working build. |