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) - tuxen - 2016-07-11 (2016-07-11, 08:51)Pienoet Wrote:it's available via the libreelec-8 update channel in libreelec settings.(2016-07-11, 08:18)tuxen Wrote: just a little update: RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-07-11 (2016-07-11, 06:33)smp1 Wrote: I have to say that TvHeadend 4.2 performs shockingly bad in Milhouse builds compared to the official LE 7.0.2.Just to confirm, the DVB dongle is a USB device connected to the Pi you are watching? (i.e. frontend and backend are on the same device) Can you test if disabling deinterlace, or switching the deinterlace method from automatic to bob makes a difference? RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Cerv4nteZ - 2016-07-11 (2016-07-09, 21:39)Milhouse Wrote:(2016-07-09, 12:45)stevegal Wrote: Just for information: build #708 still has lirc gpio problems. When I revert to #619 all works okay. Hi, i also have this problem with recent builds, my output of systemctl status | paste : http://sprunge.us/fRNU for me its the ok button that stopped working and doesnt show up on irw anymore (quite annoying) is this a kernel update related problem? RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - smp1 - 2016-07-11 (2016-07-11, 12:41)popcornmix Wrote: Just to confirm, the DVB dongle is a USB device connected to the Pi you are watching?Yes. Quote:Can you test if disabling deinterlace, or switching the deinterlace method from automatic to bob makes a difference?Just tested, no errors when deinterlace is disabled. Lots of errors with Bob and Advanced. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-07-11 (2016-07-11, 16:02)smp1 Wrote: Just tested, no errors when deinterlace is disabled. Lots of errors with Bob and Advanced. Jarvis defaults to bob when deinterlacing HD. Krypton defaults to advanced with HD, Can you double check with Krypton and Jarvis using bob and advanced? I could understand advanced giving errors on both Jarvis and Krypton. I can't think of a reason why bob would give errors on Krypton and not on Jarvis. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - mule1 - 2016-07-11 (2016-07-11, 15:49)Cerv4nteZ Wrote:(2016-07-09, 21:39)Milhouse Wrote:(2016-07-09, 12:45)stevegal Wrote: Just for information: build #708 still has lirc gpio problems. When I revert to #619 all works okay. Same here on RPI2. Anything else we can do/deliver? RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - bubi - 2016-07-11 Regarding the miniDV-AVIs from this post: http://forum.kodi.tv/showthread.php?tid=269814&pid=2372251#pid2372251 ffmpeg is totally capable of decoding CVSD and DVSD. Not MSDV however, maybe I was mistaken about that or that FourCC is just used for type1-AVIs. I'm testing a standalone ffmpeg version for Windows and the video stream is detected as "dvvideo": Code: C:\dv>C:\prg\ffmpeg.x64\bin\ffmpeg -i sample_dvsd.avi -vcodec h264 output_dvsd.avi RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - smp1 - 2016-07-11 (2016-07-11, 16:07)popcornmix Wrote: I can't think of a reason why bob would give errors on Krypton and not on Jarvis.Nevermind my previous post, I did more testing and no errors in Bob mode after 6 hours of running the HD channel. Is it normal that the Advanced mode doesn't work properly with TVH on RPi3? Will it make sense to overclock the GPU? I will try "h264_freq=1000" and leave it on an HD channel overnight. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-07-12 New LibreELEC.tv Krypton build #0711: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of LibreELEC.tv master (1cfefd35, changelog) and tip of XBMC master (874b7bdc, changelog) with the following modifications:
RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - HiassofT - 2016-07-12 (2016-07-11, 15:49)Cerv4nteZ Wrote: Hi, i also have this problem with recent builds, my output of systemctl status | paste :Thanks for the info! systemctl output shows that lircd-uinput is running (this should be disabled in recent Milhouse builds). Just to be sure, could you update to the latest Milhouse build and post the systemctl output of that? Also: what kind of remote are you using? And, as you seem to be using a custom lircd.conf, could you please upload that as well? Code: paste /storage/.config/lircd.conf Quote:is this a kernel update related problem?It seems to be a problem caused by the lircd update a few weeks ago, but not all remotes seem to be affected by it. Therefore it's important to know which kind of remote you are using, which keys are not working and if you are using a custom lircd.conf. That info should help us to reproduce the issue and track down the root cause of it. so long, Hias RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - HiassofT - 2016-07-12 (2016-07-11, 16:15)mule1 Wrote: Same here on RPI2. Anything else we can do/deliver?Could you please tell us which remote you are using and also post the output of "systemctl status | paste" and - if you are using a custom lircd.conf - post that file as well? so long, Hias RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - mule1 - 2016-07-12 (2016-07-12, 00:43)HiassofT Wrote:I'm using a harmony remote which has been programmed as Intel D34010WYK (should be the same as the MCE Remote). I'm not using a custom lircd.conf.(2016-07-11, 16:15)mule1 Wrote: Same here on RPI2. Anything else we can do/deliver?Could you please tell us which remote you are using and also post the output of "systemctl status | paste" and - if you are using a custom lircd.conf - post that file as well? systemctl status | paste using Build #0711 Affected button is for example OK while cursor keys are not affected. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - dias0 - 2016-07-12 Hi. Im using a crypto remote with a custom lircd.conf. Using build 711. http://sprunge.us/eBYO key OK , Numeric keys not working. Cursor keys are ok.. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-07-12 (2016-07-11, 21:52)smp1 Wrote: Nevermind my previous post, I did more testing and no errors in Bob mode after 6 hours of running the HD channel. Is it normal that the Advanced mode doesn't work properly with TVH on RPi3? Will it make sense to overclock the GPU? I will try "h264_freq=1000" and leave it on an HD channel overnight. h264_freq=1000 doesn't make sense. The maximum overclock is around 500. I believe the issue is sdram bandwidth. advanced deinterlace takes enough sdram bandwidth that it can interfere with some types of dvb dongle. polo_joe did have a similar issue, but he changed the dvb dongle to a different make which didn't have the issue. So, options are: use bob deinterlace use a different dvb dongle run the dongle/backend on a separate machine overclock sdram tweak the sdram priorities If you are happy to do some experiments, there are a few controls that affect sdram priorities which I'd like to know if they can help. The most likely one to help is v3d_limiter which defaults to 0x0880f1. The bits define as: Code: bit 0 is "enable" So, to reduce artefacts (although at the cost of making the deinterlace take longer which could result in skips), you want to either increase the "holdoff" (the initial 08), or increase the "increment" (the next 80). As the increment is already quite high, the holdoff is more likely to help. Can you try with it increased to 0x10? i.e. add v3d_limiter=0x1080f1 to config.txt and reboot and test. If that doesn't help, then try v3d_limiter=0x2080f1. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - BobCratchett - 2016-07-12 (2016-07-12, 00:43)HiassofT Wrote: Could you please tell us which remote you are using and also post the output of "systemctl status | paste" and - if you are using a custom lircd.conf - post that file as well? Please see this post for the lircd.conf for one remote that isn't working, along with a list of the buttons that don't work - that remote is from the 'Top Up TV' branded Thomson box DTI6300. (This remote) Also not working is the Xbox 360 Media Remote (this remote), and the associated lircd.conf - I haven't had the time to test this one fully, but at the very least the OK and the Info buttons aren't working. systemctl status from build 0711 Cheers. |