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) - hdmkv - 2015-10-12 Okay, trying both, one at a time, and will report back. I see there was a typo in what @popcornmix had. Thanks. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - hdmkv - 2015-10-13 (2015-10-12, 23:55)woronczak Wrote: I have found (with my projector W1070) that 1920*1080 @50, I don't have issues. If the GUI is set to 1920*1080 @ 23.98, once I stop the 3d iso, the projector gets stuck in frame Packing mode (hence the GUI is not right). I know you have a different projector now, but maybe try 50HzAwesome... this did the trick , but why?! 1080p/60 and 59.94 should work too. Using build #1012 now. I have an Epson 5025UB and a BenQ W1070 (in different rooms), with Pi2 connected to each. (2015-10-12, 23:53)Milhouse Wrote: Try: Noticed that when reboot is done via SSH, Pi's UI rez goes to 23.98 (when I'd last set it to 60.00 or 59.94). RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-10-13 I'll probably jinx myself by saying this but with #1009 I haven't seen the problem I've been having with my tuners disappearing from tvheadend, so maybe there were some fixes to power saving issues or something that might have been causing that? I have been seeing glitches which look like frames being skipped, making movement appear jumpy, with quite low resolution/bitrate AVC files though. Some of these seem to be due to poor encoding and repeat if I replay and also happen playing the files with VLC on my PC but others seem to be caused by OE and don't repeat when I replay the section. The overlay tends to show something like "drop:0 skip:5 pc:1" in total when watching the video but most of those seem to happen near the start, as after just a few seconds it might show "skip:3 pc:1" so these stats don't reflect the issues I notice and don't tend to have increased when I check after noticing them. I've noticed that the err stat on the 2nd line of the overlay is about +/-10ms in most cases with these files, although sometimes nearer 20ms but if I skip this jumps to around 75ms and then slowly decreases over time, so it appears this does not reset when jumping through the file and continues to calculate an average. Also aq is locked at a solid 99% whilst vq (video quality?) constantly fluctuates between 95-99% but if I skip backwards or forwards sometimes this drops to 91-95% or even 87-91%. Code: General RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - woronczak - 2015-10-13 (2015-10-13, 00:15)hdmkv Wrote:(2015-10-12, 23:55)woronczak Wrote: I have found (with my projector W1070) that 1920*1080 @50, I don't have issues. If the GUI is set to 1920*1080 @ 23.98, once I stop the 3d iso, the projector gets stuck in frame Packing mode (hence the GUI is not right). I know you have a different projector now, but maybe try 50HzAwesome... this did the trick , but why?! 1080p/60 and 59.94 should work too. Using build #1012 now. I have an Epson 5025UB and a BenQ W1070 (in different rooms), with Pi2 connected to each. The W1070 only supports frame packing at "24p" for 1920*1080. It seems like after stopping a 3d MKV / bluray iso, Kodi doesn't send a message to the projector to say that it should turn frame packing off (the projector tells me Frame Packing is still on) so the GUI looks wrong (or in your case, it just goes blank). If I set the GUI at anything other than 23.98 / 24 @ 1920*1080, as the projector does not support frame packing for those rates, it works normally. I don't fully understand what is happening under the hood, but through trial and error, I found that it works that way. No great loss to have the GUI at 50hz (other than a flicker when the projector shifts modes). Cheers RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Caramba69 - 2015-10-13 All 3D ISO's work with #1012 now. Great work!!! Bluetooth on #1003 - cdvreede - 2015-10-13 just got myself a bluetooth dongle for one of my pi2's running #1003. Having issues as in managed to pair once but lost connection. Deleted connections and cannot pair again. Tried Android phone and Bluetooth speaker - both connect (they show up as devices - allow to connect or trust and connect) but then give Bluetooth error - no such file or directory and disconnect. No idea what this is all about - any ideas?? thnx Dennis RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-10-13 (2015-10-12, 23:55)woronczak Wrote: I have found (with my projector W1070) that 1920*1080 @50, I don't have issues. If the GUI is set to 1920*1080 @ 23.98, once I stop the 3d iso, the projector gets stuck in frame Packing mode (hence the GUI is not right). I know you have a different projector now, but maybe try 50Hz Can you also report output of: Code: tvservice -s when you believe projector is incorrectly in FP mode. I'd like to know if firmware believes it is signalling FP or not. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - parcel - 2015-10-13 I found solution for mystery bookmark crash problem. There is a lot of "10025-xxxx.fi" files and then I delete them, no more crash. I don't know what is this file, but first number of filename is window ID. Delete all ".fi" files in folder '.kodi/temp', it solves bookmark crash problem. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - woronczak - 2015-10-13 (2015-10-13, 11:26)popcornmix Wrote:(2015-10-12, 23:55)woronczak Wrote: I have found (with my projector W1070) that 1920*1080 @50, I don't have issues. If the GUI is set to 1920*1080 @ 23.98, once I stop the 3d iso, the projector gets stuck in frame Packing mode (hence the GUI is not right). I know you have a different projector now, but maybe try 50Hz state 0x12000a [HDMI CEA (32) RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive (which is different to when the movie is actually playing = "state 0x12000a [HDMI CEA (32) 3D FP RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive" RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - hdmkv - 2015-10-13 For me, it's not just 3D (frame-packed mode and coming out of it) that had the issue, but 2D as well with UI set to 59.94 or 60.00. Re: RE: Bluetooth on #1003 - Milhouse - 2015-10-13 (2015-10-13, 11:08)cdvreede Wrote: just got myself a bluetooth dongle for one of my pi2's running #1003. Having issues as in managed to pair once but lost connection. Deleted connections and cannot pair again. Tried Android phone and Bluetooth speaker - both connect (they show up as devices - allow to connect or trust and connect) but then give Bluetooth error - no such file or directory and disconnect. Test with 5.95.5. If you have the same problem you'll need to report it to the OpenELEC developers as it's going to be a core issue as there are no Bluetooth changes in these builds. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-10-13 (2015-10-13, 12:58)woronczak Wrote: state 0x12000a [HDMI CEA (32) RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive Okay. Sounds like if the refresh rate doesn't change, but the 3D FP mode does then either we don't re-initialise everything, or we do, but the display doesn't see the change. I'll step through the code and see if anything is skipped when switching from 1080p23.98 FP to 1080p23.98. Does disconnecting and reconnecting the HDMI cable have any effect? It it does that would suggest we are outputting the correct signal but the display didn't switch correctly. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-10-13 I've been playing with setting GUI resolution to [email protected] and playing MVC files. My display seems to switch back correctly to non-3D mode when stopping. I've stepped through the firmware code, and while it can skip the mode change if it believes nothing has changed, it does check the 3D mode, so should spot switches into and out of 3D mode. I'm interested in the results of "disconnecting and reconnecting the HDMI cable". Ideally you should add "hdmi_force_hotplug=1" to config.txt to ensure the Pi doesn't notice the unplug/plug events. Can you also report output of: Code: vcgencmd measure_clock pixel when stopping (and gui being wrong). It should be about 74MHz when in 2D mode and 148MHz when in 3D FP mode. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - rudrood - 2015-10-13 @popcornmix, Want to start using the testbuilds on my Pi2. Are there any of my config.txt settings that are obsolete for these builds? arm_freq=1050 core_freq=550 over_voltage=4 gpu_mem=320 gpu_freq=400 hdmi_pixel_encoding=2 dtoverlay=sdhost,overclock_50=84 over_voltage_sdram_c=0 over_voltage_sdram_i=0 over_voltage_sdram_p=2 avoid_pwm_pll=1 v3d_freq=300 force_turbo=1 Thanks RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-10-13 (2015-10-13, 22:24)rudrood Wrote: @popcornmix, You can remove avoid_pwm_pll with latest builds. You now get the effect of that by default without harming analogue audio. You can remove over_voltage_sdram_c and over_voltage_sdram_i as they are set to zero (and also have no effect on Pi2). Otherwise looks okay. |