OpenELEC Testbuilds for RaspberryPi Part 2 - 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 Part 2 (/showthread.php?tid=184866) 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
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
RE: OpenELEC Testbuilds for RaspberryPi Part 2 - jpcolin - 2014-02-01 (2014-01-29, 22:57)jpcolin Wrote: Hi, Hi just to that i managed to install Millhouse build on my Pi using this "how to" http://tasksofohm.wordpress.com/hardware/openelec-on-raspberry-pi/ I'm using windows so the wiki did not help me. thanks for the work millhouse, it seems to work great, i seems as "fast" if not faster in the menus as my ATV2. The only problems i have but i might be related to gotham, is - with the subtitles, really slow to find the subtitles. and it does not always works - some "stutering" with fast scenes, i read about the 25hz, 50 and 60 problem, but at first look changing the setting does not seems to make a difference Next step is to install a USB stick. Regards and keep going on. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2014-02-01 (2014-02-01, 17:32)jpcolin Wrote: - some "stutering" with fast scenes, i read about the 25hz, 50 and 60 problem, but at first look changing the setting does not seems to make a difference Make sure "Adjust display refresh rate to match video" is turned on: http://wiki.xbmc.org/index.php?title=Settings/Videos RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2014-02-02 New OpenELEC Gotham build: #0202 (Supercedes previous build) Code: # uname -a Based on tip of XBMC master (fc8358e, changelog) and tip of OpenELEC master (0c71539, changelog) with the following modifications:
Additional Testing Notes:
RE: OpenELEC Testbuilds for RaspberryPi Part 2 - b1m1 - 2014-02-02 Hi Guys, Thanks for your ongoing work. Do the latest alsa changes resolves the crackling/clicking issue? https://github.com/raspberrypi/linux/issues/320 Thanks. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - RichG - 2014-02-02 I've just upgrade to latest MilhouseVH build. Not sure if this is new to this build, but I'm seeing issues with step back and rewind (controlled via IR remote) when playing a movie with DVDPlayer. When stepping back the sound jumps back and continues from the correct point (or so it seems) while the picture just freezes (or starts to play very slowly) at the point it was at. The picture sometimes recovers when the sound 'catches up' to the point the video is frozen at. When rewinding the picture and sound go back to different points and play out of sync for a while (seconds) until the picture (in a very jerky manner) 'catches up'. No problems with step forward or fast forward, and also no apparent problems with OMXplayer. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2014-02-02 (2014-02-02, 10:31)b1m1 Wrote: Do the latest alsa changes resolves the crackling/clicking issue? That issue doesn't affect xbcm (which doesn't use alsa). RE: OpenELEC Testbuilds for RaspberryPi Part 2 - b1m1 - 2014-02-02 @popcornmix Thanks, that is disappointing to hear as I have been experiencing clicking and crackling in the last couple of builds. I had my pi connected directly to my tv which only supports 2ch PCM and I was experiencing this type of distortion. This prompted me to connect to my Amp which supports the common codecs and switch on pass through but the clicks and crackling still persist. Thanks for your feedback and great support. Will have a look through my settings and check my media files to see if I can find a fault. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - jpcolin - 2014-02-02 Hi, just a question for popcorn, on your youtube video, (wich seems a lot faster than my setup, but still have to do the usb stick trick), is your GUI setup in 720 or 1080? Of course the movie play in 1080p right? RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2014-02-02 (2014-02-02, 15:12)jpcolin Wrote: Hi, just a question for popcorn, on your youtube video, (wich seems a lot faster than my setup, but still have to do the usb stick trick), is your GUI setup in 720 or 1080? GUI resolution and HDMI resolution were both 1080p in video. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - doveman2 - 2014-02-02 I know it's a bit OT and I'll start a new thread for further advice depending on the answer to this question but I was wondering if there's any way for me to add an OpenVPN server to my OE install? I could use another RPi just for that but it seems a bit wasteful, as I'll only be connecting to the OpenVPN server when I'm out and thus not using XBMC, so using one RPi for both seems more sensible and cuts down on clutter/cabling/PSUs. I realise I can't expect any support with such a non-standard OE install but I'm just asking if there's a way to do this, as I see apt-get is locked out in OE so I can't just install OpenVPN that way? RE: OpenELEC Testbuilds for RaspberryPi Part 2 - delinend - 2014-02-02 Questien regarding the "Audio output"->"Normalize levels on downmix" I have a 2 speaker setup (screen only), and installed last Milhouse build r17587. Here my "Audio output" settings: Audio output device = HDMI Number of channels = 2.0 Stereo upmix = Disable Normalize levels on downmix = Enable . "The rest is default" When I play a 5.1 content movie, the sound is LOW on my system If I Disable the "Normalize levels on downmix", the sound is NORMAL/HIGH. Hmmm.. Am I missing somthing.. Is that not the function of "Normalize levels on downmix", to give higher sound, when enabled ? I looks to me, that this setting is reversed, or am I misunderstanding something ? Best regards. Btw: I use omxplayer, and the 5.1 audio/video content, is DVD/MPEG2/ISO. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2014-02-02 (2014-02-02, 15:45)doveman2 Wrote: I know it's a bit OT and I'll start a new thread for further advice depending on the answer to this question but I was wondering if there's any way for me to add an OpenVPN server to my OE install? http://openelec.tv/forum/69-network/66714-openvpn-solution-butchered-together-solution-open ? RE: OpenELEC Testbuilds for RaspberryPi Part 2 - markius - 2014-02-02 I'm not sure if this is a development build issue or not but I'm having some problems with timeouts on my NFS mounted /storage cmdline.txt Code: ip=10.150.213.5::10.150.213.30:255.255.255.224:OpenELEC:eth0:off boot=LABEL=SYSTEM disk=NFS=10.150.213.2:/volume1/openelec console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 ssh Code: OpenELEC:~ # mount | grep 10.150.213.2 The NFS server is connected to the same switch as the Pi. The timeouts seem to occur randomly but I can usually reproduce them by transferring a lot of data to/from the NFS mount at the same time: Code: OpenELEC:~ # dd if=/dev/zero of=/storage/test.data bs=8M count=512 What I've found is that if I change the rsize and wsize to smaller values, I don't have any problems: Code: OpenELEC:~ # mkdir /var/media/test Is there a way to change the default wsize and rsize for NFS /storage when it's mounted via cmdline.txt? RE: OpenELEC Testbuilds for RaspberryPi Part 2 - javaboyuk - 2014-02-02 Hi May I make some comments? Yes you should be able to change the read/wite size when mounting, see the man pages (welI I can on Solaris) Anyway the real worry for me, your mounting the NFS mount with SOFT option, generally you should NEVER do this if your going to write to it, and really unlikely even if its read only unless you have multiple source to switch bettween, with specialist code to detect that etc. So always mount NFS with HARD "hard" as the option. Now that is based on quite old knowledge, but I can't see that level of fundamental approach changing :-) So please mount it hard, the timeouts will still happen, but you will not loose data ie get the IO errors your seeing, especally dangerous post flush() when the code does not bother to check the return you effectively get silent data corruption. Enjoy. JB Code: OpenELEC:~ # mount | grep 10.150.213.2 The NFS server is connected to the same switch as the Pi. The timeouts seem to occur randomly but I can usually reproduce them by transferring a lot of data to/from the NFS mount at the same time: Code: OpenELEC:~ # dd if=/dev/zero of=/storage/test.data bs=8M count=512 What I've found is that if I change the rsize and wsize to smaller values, I don't have any problems: Code: OpenELEC:~ # mkdir /var/media/test Is there a way to change the default wsize and rsize for NFS /storage when it's mounted via cmdline.txt? [/quote] RE: OpenELEC Testbuilds for RaspberryPi Part 2 - javaboyuk - 2014-02-02 Guys the mount of /Storage from cmdline.txt would appear to be a SOFT mount from markius's output. this is very dangerous as the writes will time out on busy/overloaded servers leading to possible data corruption, I believe. Should he riase bug on openelec, or our builds for RPI builds? For sort of an interesting discussion I saw this.. http://discussions.citrix.com/topic/274380-nfs-soft-mount-vs-hard-mount/ So they have made changes for NFS-Version 3, but HARD is still probabily the way to go, |