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) - polo_joe - 2015-08-31 (2015-08-31, 18:14)popcornmix Wrote:(2015-08-31, 17:44)polo_joe Wrote: I tried both settings together and each alone. unfortunately I don't know anyone else. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-08-31 (2015-08-31, 17:44)polo_joe Wrote: I tried both settings together and each alone. mmal advanced at HD triggers a boost to 300MHz (of v3d clock). The half version doesn't need the boost, nor does automatic (which uses bob for hd). So my guess is that 300MHz v3d is not working on your Pi. However with default config.txt settings (i.e. no v3d_freq or gpu_freq specified) and with disable_auto_turbo=1 you should still be running at 250MHz. When running with default config.txt settings + disable_auto_turbo=1 and when getting the artefacts can you run: Code: vcgencmd measure_clock v3d RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - polo_joe - 2015-08-31 (2015-08-31, 18:42)popcornmix Wrote:(2015-08-31, 17:44)polo_joe Wrote: I tried both settings together and each alone. frequency(43)=250000000 config.txt http://sprunge.us/ifBC RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-08-31 (2015-08-31, 19:46)polo_joe Wrote: frequency(43)=250000000 And with this configuration you get artefacts with "MMAL Advanced" and no artefacts with "MMAL Advanced (half)", "Bob" or "Automatic"? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - polo_joe - 2015-08-31 (2015-08-31, 19:52)popcornmix Wrote:(2015-08-31, 19:46)polo_joe Wrote: frequency(43)=250000000 Yes artefacts with MMAL advanced, no artefacts with mmal half, automatic or bob on 1080i50 livetv channel. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-08-31 (2015-08-31, 20:04)polo_joe Wrote: Yes artefacts with MMAL advanced, no artefacts with mmal half, automatic or bob on 1080i50 livetv channel. Same config settings as before, but add "force_turbo=1". Now I'm interested if "MMAL advanced (half)" has artefacts. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - polo_joe - 2015-08-31 (2015-08-31, 20:06)popcornmix Wrote:(2015-08-31, 20:04)polo_joe Wrote: Yes artefacts with MMAL advanced, no artefacts with mmal half, automatic or bob on 1080i50 livetv channel. mmal half = no artefacts mmal advanced = artefacts config.txt http://sprunge.us/dQNP RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-08-31 (2015-08-31, 20:14)polo_joe Wrote: mmal half = no artefacts Okay, default settings plus: Code: force_turbo=0 RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - polo_joe - 2015-08-31 (2015-08-31, 20:17)popcornmix Wrote: Okay, default settings plus: mmal half = artefacts mmal advanced = artefacts config.txt http://sprunge.us/WZhP RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-08-31 (2015-08-31, 20:25)polo_joe Wrote: mmal half = artefacts I was expecting no artefacts with those settings. It does feel to me like a faulty Pi. Can you remove non-default config.txt settings and try the shadertoy addon: http://forum.kodi.tv/showthread.php?tid=204991&pid=2017239#pid2017239 Enable the shadertoy screensaver and try a number of them. Also can you try a HEVC file. E.g. http://www.elecard.com/assets/files/other/clips/bbb_720p_c.ts If either of these fail, then it would suggest a problem with the 3D hardware on the Pi (which is used by both of these tests). RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - polo_joe - 2015-08-31 (2015-08-31, 20:39)popcornmix Wrote: If either of these fail, then it would suggest a problem with the 3D hardware on the Pi (which is used by both of these tests). screensaver and video are working perfectly fine. config.txt http://sprunge.us/FRBR RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - metaron - 2015-08-31 I'm having problems seeking / with 4:3 to 16:9 transitions on RPi with the latest build (New OpenELEC Jarvis build #0830: RPi) using both the OMXPlayer and MMAL acceleration options. This seems to affect channels when they use different formats/bitrates for ads and shows. I've uploaded a short extract here ( http://www.thomasinfletcher.com/temp/xaa.mpg ) which exhibits the problem. The file is a .ts stream recorded using a WinFast DTV1000-T and mythtv from the 'Yesterday' channel in the UK. It starts with adverts in 16:9 format, then switches to a program in 4:3 format. Symptoms are as follows:
Similar issues happen later in the full recording at the start of the next add break when a 4:3 to 16:9 transition occurs. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-09-01 New OpenELEC Jarvis build #0831: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (494f51df, changelog) and tip of XBMC master (23bc0c1a, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - miigotu - 2015-09-01 Hey, I'm a few days behind, this is a crashlog from #0829 http://sprunge.us/GOAN Came across a crash caused by scp'ing a 2GB file to /storage/videos. It starts bootlooping after awhile, although the scp continues to resume after each loop for awhile and the transfer continues and completes successfully. Afterwards I had to force a reboot to get out of the bootloop, even after the transfer was complete. I assume from the log this probably wasnt fixed in 830,831 RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-09-01 Not seen that before, I'll upload a debug-enabled build in case you're able to reproduce as unfortunately the crash-log isn't providing much information other than a suggestion that something went wrong while servicing a webserver request. |