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-11-10 also tried vdr and it is more unreliable with my rpi2 hd channels are stuttering, playback stops etc. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - gurabli - 2015-11-10 Something must be wrong with your setup, I'm watching live tv atm, rpi2, milhouse build, vdr vnsi. Perfect, HD channels too. Strange. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-11-10 (2015-11-10, 20:39)gara93 Wrote: There is a stable OE 6 with jarvis 16? i try the stable version with isengaardand I have Always problems with pvr.. No, stable OE6 is Isengard. Trying a nightly/jarvis build is not likely to make things more stable. These builds are experimental and really only for testers. If you just want a stable build then you will be better off trying to get your pvr working with OE6/Isengard (post on the OE forum if you are having trouble). RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - gara93 - 2015-11-10 (2015-11-10, 20:47)popcornmix Wrote:(2015-11-10, 20:39)gara93 Wrote: There is a stable OE 6 with jarvis 16? i try the stable version with isengaardand I have Always problems with pvr.. Isengard is a problem...because the version of iptv simple client have a bug: channel switching is very slow (15sec)..with the new version of iptv simple client added in jarvis the problem dissapered.. then I can't installa isengard if i want a fast pvr client RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - gurabli - 2015-11-10 I guess something must be wrong with the dvb-x tuner or the signal, or both. VDR is working perfect on Isengard and Jarvis OE versions running rpi2. Test your signal strength with tv or box, if good troubleshoot the dvb device. But this is off topic here. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Boremc - 2015-11-10 This build accepts dolby hd and true hd making passtrought using raspb pi2? thanks RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - herrmeier01 - 2015-11-10 For VDR it's importand to to change default value of priority in VDR VNSI Client from "-1" to "0" RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - .bismarck - 2015-11-10 @popcornmix, currently play a 3D MVC file(makemkv), then takescreenshot: Code: kodi-send --action="TakeScreenshot" Result: 3DTAB. Why? GUI is in 3DSBS Mode. Code: tvservice -s .bismarck RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-11-10 (2015-11-10, 23:31).bismarck Wrote: 3DTAB. Why? What is the problem exactly? 3D FP is a TAB mode. Turn off "full frame" in video/acceleration settings and you'll get a half-SBS image. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-11-11 New OpenELEC Jarvis build #1110: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (2a7db0dc, changelog) and tip of XBMC master (aa42e1b8, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - parcel - 2015-11-11 In video Addons list I click 'more...' button clicked, Kodi crashes, http://xbmclogs.com/pelfff3an RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-11-11 (2015-11-11, 12:23)parcel Wrote: In video Addons list I click 'more...' button clicked, Kodi crashes, Do you mean the Video -> Addons -> "Get more..." button, as this is working for me with build #1110 (ie. not crashing). Can you try with a clean .kodi? Based on the crashlog, it doesn't look like the crash has anything to do with the addons... at least nothing to do with you clicking the "Get more..." button, however the log does mention: Code: 16:35:16 128.451538 T:1965400064 ERROR: exception in CApplication::FrameMove() It seems that once this CApplication::FrameMove() error occurs - which I suspect is causing some internal screw up - it's only a matter of time before Kodi eventually falls over. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - parcel - 2015-11-11 (2015-11-11, 12:36)Milhouse Wrote:(2015-11-11, 12:23)parcel Wrote: In video Addons list I click 'more...' button clicked, Kodi crashes, Yes, 'Get more...' button. I'm try to delete related cache file or something (edit) delete all '.fi' files in temp folder, problem is gone. Thank you! RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-11-11 (2015-11-11, 12:55)parcel Wrote: (edit) delete all '.fi' files in temp folder, problem is gone. Thank you! Actually I've seen that has been needed a few times with nightly builds. They are cache files which I think can become invalid when a PR gets modified (as often happens when they are pulled into these builds before merging). I wonder how much cost you'd suffer from deleting them on each boot? If it's negligible it might be worth doing this on each boot (or each update). RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-11-11 I'll add a quick fix that cleans the *.fi every time kodi is started. It's probably overkill (I'm assuming there's a benefit from having old cache files lying around, until that is they break the current build) but cleaning the cache files from init isn't ideal either. If the cache files cause problems with different builds then perhaps the cache files need to be versioned... |