v17 LibreELEC Testbuilds for RaspberryPi (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: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166) +---- Thread: v17 LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) (/showthread.php?tid=269814) 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
|
RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Korrigan - 2016-10-10 (2016-10-10, 19:02)popcornmix Wrote: You are not losing anything. The Pi knows if the video is limited or full range.But I tried a full range video (http://www.avsforum.com/forum/139-display-calibration/948496-avs-hd-709-blu-ray-mp4-calibration.html) and I can't get 0-15 to show. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-10-10 (2016-10-10, 19:37)Korrigan Wrote: But I tried a full range video (http://www.avsforum.com/forum/139-display-calibration/948496-avs-hd-709-blu-ray-mp4-calibration.html) and I can't get 0-15 to show. That's rather a long article and includes several downloads. Can you describe exactly which video file you played? (ideally provide a sample that shows the problem). RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Korrigan - 2016-10-10 (2016-10-10, 19:48)popcornmix Wrote:I tried the MP4 version from the above link -> Basic Settings -> 1-Black Clipping.mp4 (https://drive.google.com/open?id=0B_-WwzV-6UosOTR0YUx6RHc1T1U)(2016-10-10, 19:37)Korrigan Wrote: But I tried a full range video (http://www.avsforum.com/forum/139-display-calibration/948496-avs-hd-709-blu-ray-mp4-calibration.html) and I can't get 0-15 to show. Works as intended on my PC but I cant get Kodi/RPi to show 0-15 RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-10-10 Code: mediainfo "./MP4-2c/Basic Settings/1-Black Clipping.mp4" Note the Code: Color range : Limited RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Korrigan - 2016-10-10 (2016-10-10, 20:02)popcornmix Wrote: Note theSo the video contains 0-15 but is set to "limited"? And that causes Kodi to scale from Limited to Full and discard 0-15? RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-10-10 (2016-10-10, 20:09)Korrigan Wrote: So the video contains 0-15 but is set to "limited"? And that causes Kodi to scale from Limited to Full and discard 0-15? Yes, any values from 0-15 in a limited range video are out of spec and should be clamped (to the same value that 16 produces - effectively as black as possible). RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Korrigan - 2016-10-10 (2016-10-10, 20:11)popcornmix Wrote:But why scale at all if the Wiki says Kodi limited -> GPU full -> TV limited produces the best results?(2016-10-10, 20:09)Korrigan Wrote: So the video contains 0-15 but is set to "limited"? And that causes Kodi to scale from Limited to Full and discard 0-15? RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-10-10 (2016-10-10, 20:17)Korrigan Wrote: But why scale at all if the Wiki says Kodi limited -> GPU full -> TV limited produces the best results? The wiki is for PCs where it is unknown whether the video driver defaults to limited or full range. The Pi doesn't have this problem and shouldn't normally require changing. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-10-11 (2016-10-10, 19:29)cojms1 Wrote: I did a little bit of research and it seems that TP-LINK have a linux driver but only for kernel versions 2.6-3.16 (http://www.tp-link.com/en/download/Archer-T1U.html#Driver). Is there anything that can be done to get this available in LibreELEC?You probably should have done your research before buying, that way you would have avoided buying unsupported hardware. LibreELEC is not a general purpose distribution (such as Raspbian) and for that reason doesn't support the thousands of different wireless devices that are available (often very badly supported by the chip manufacturers with outdated drivers), it focuses instead on those devices that are well supported by the mainline kernel plus a handful of incredibly common Realtek devices. You could try asking on the LibreELEC forum if support can be added for this dongle (apparently it needs the mt7610 driver) but this thread isn't for feature requests. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-10-11 (2016-10-10, 18:17)polo_joe Wrote: @Milhouse tl;dr: the file is correct, the addon.xml is garbage. The version number in my file (4.1.2267) is automatically generated from git - the top of tree in the tvheadend42 git is 4.1.2267. The file is correct. The addon.xml for tvheadend42 is generated from the version number configured in LibreELEC master, which is not top of tree - it is 4.1.2236. This appears only in the description text for tvheadend42, it is garbage as I don't build the addon using that version. It's not typical for addons to include a version number in their description - there's absolutely no reason to do this - and the fact that tvheadend42 does this is annoying but not something I have any intention of fixing. I'll remove the bogus version from addon.xml, that will end this. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-10-11 New LibreELEC.tv Krypton build #1010: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of LibreELEC.tv master (5661f325, changelog) and tip of XBMC master (57eb7af8, changelog) with the following modifications:
RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - polo_joe - 2016-10-11 (2016-10-11, 02:33)Milhouse Wrote:(2016-10-10, 18:17)polo_joe Wrote: @Milhouse I got the build number from webui of tvheadend and in journalctl tvheadend also reported build 4.1.2236, so I thought it is not top of tree. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - cojms1 - 2016-10-11 (2016-10-11, 01:59)Milhouse Wrote: You probably should have done your research before buying, that way you would have avoided buying unsupported hardware. LibreELEC is not a general purpose distribution (such as Raspbian) and for that reason doesn't support the thousands of different wireless devices that are available (often very badly supported by the chip manufacturers with outdated drivers), it focuses instead on those devices that are well supported by the mainline kernel plus a handful of incredibly common Realtek devices. I'll ask in the LibreELEC forum. It's not an issue either way. The dongle was actually bought for another purpose, I just thought I'd plug it in and see if it worked - knowing that at some point I'd probably end up attempting to reuse it. Thanks for the reply. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - drdwridav - 2016-10-11 (2016-08-12, 17:26)drdwridav Wrote:(2016-08-12, 15:11)popcornmix Wrote:(2016-08-10, 23:30)drdwridav Wrote: EDIT: one other quick finding. If I disable adjust display refresh rate -obviously playback jerky - but kodi does switch back to 2d properly on exiting. Interesting? Hi popcornmix. You may recall the conversation above from a few weeks ago about my Samsung TV not switching back to 2D after a 3D film. With the increased delay it's now ok with OMX, but with MMAL it's the same old problem regardless of the delay set. MMAL is the better player now (especially as there are no issues fast forwarding 3D films) so this is getting to me a bit (only because I'm a perfectionist and want it all flawless!). It's a pretty mainstream TV (48 inch H series 2014) so I'm surprised no one else is getting the issue too! What I have noticed though which might be of interest is that on exiting the 3D film the TV does momentarily switch to 2D (you can see the menu fine for a glimpse), it then goes black and switches back to a garbled 3D image. Is there any other adjustment I can try? Failing that is it possible to remote keymap change resolution or refresh rate? Because at the moment my way to cure this after a 3D film is to go into system settings, select a different refresh rate or resolution - then reject the change when it is offered....back to normal. Cheers RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-10-11 (2016-10-11, 17:46)drdwridav Wrote: Is there any other adjustment I can try? Yes, I did add some settings for this sort of thing. Let me check... okay, by default there is a config.txt setting: Code: hdmi_muting=0x00640032 which decodes to: hdmi_mute_period_before_change_in_ms=0x64=100ms hdmi_mute_period_after_change_in_ms=0x32=50ms When changing hdmi mode we "mute" the signal (not an audio mute, but telling the display to ignore the signal during the change). Possibly your display will be happier with a longer mute either before or after the hdmi mode change. What I would suggest is to try doubling it a few times to see if that helps. Try, in order, one setting at a time each of these: Code: hdmi_muting=0x00640032 e.g. Add "hdmi_muting=0x00640032", reboot. Test video playback. If no better try "hdmi_muting=0x00c80064", reboot. Test video playback, etc. |