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) - doveman2 - 2015-10-17 (2015-10-17, 02:35)Milhouse Wrote: Doesn't tvheadend have it's own log? Is tvheadend listening on port 9981? Does tvheadend work with #1015 (the only difference between the two builds should be the way libnfs is compiled)? Thanks. I uninstalled the existing one and installed the new #1015 tvh addon and that got it working. The tvh client does have a "Trace debugging" option but I don't know where it's meant to create the log, as I can't see it in temp or addon_data/pvr.hts RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - hdmkv - 2015-10-17 (2015-10-17, 00:19)BubbleBobble Wrote: For me 3D is working out great. I had no stuttering whatsoever. Frame packing at 1080p/23.97 and it goes as smooth as my stand alone bluray players.Not for me . Going to do a clean install and try build #1014 as you have. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - BubbleBobble - 2015-10-17 (2015-10-17, 15:47)hdmkv Wrote:(2015-10-17, 00:19)BubbleBobble Wrote: For me 3D is working out great. I had no stuttering whatsoever. Frame packing at 1080p/23.97 and it goes as smooth as my stand alone bluray players.Not for me . Going to do a clean install and try build #1014 as you have. My base install was OpenELEC-RPi2.arm-5.95.5 http://releases.openelec.tv/OpenELEC-RPi2.arm-5.95.5.img.gz?mirrorlist Then I updated to build #1014. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - hdmkv - 2015-10-17 Just tried that, same issues no matter what (UI at Desktop, 1080p/60.00Hz, 1080p/59.94Hz, or even 1080p/50.00Hz, which previously seemed to do the trick). I have 2x Pi2's with different mSD cards in them, so this isn't some issue with a particular Pi2. I even kept original Confluence skin, no add-ons, and just did plain vanilla file playback of 2D and 3D. Same problems with both Pi2's and my Epson 5025UB PJ, via Onkyo NR636 AVR. No issues with my Chromebox with exact settings with same 2D files, and no such issues with my HiMedia Q5 and same 2D and 3D files. At this stage, I'm pretty frustrated with Pi2 and may give up for a while at least. Spent way too many hours trying to get it to work right, even with 2D. Always same issue... play a video for 15-20 secs, stop, then play next and blank screen. Or, if I'm lucky, happens after 3rd video playback or 4th. With 3D, same damn thing. There's something with Pi2 and the signal switches (the way it's sending them) that my PJ doesn't like. Not just Epson 5025UB, but also BenQ W1070. But, issue is worse on Epson. At this point, I've tried most builds from #0916 to #1016. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - BubbleBobble - 2015-10-17 It could be a hdmi handshake issue? Have you tried to connect your Raspberry directly to your projector? To get the most simple hdmi setup. No AVR and other splitters/switches. We have the same projectors, raspberry's and software. I used to have an Yamaha AVR and no issues. My Anthem MRX 300 AVR however is a screw-up with handshaking. I split the hdmi signal so my AVR doesn't need to feed my projector. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - hdmkv - 2015-10-17 Worth a shot. Will try later today. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - BubbleBobble - 2015-10-17 If you happen to have a 6ft or longer hdmi cable then try with that. On several forums like Curtpalme and AVSforums there has been talk shorter hdmi cables might produce bugs. For example https://www.avforums.com/threads/darbee-visual-presense-darblet-owners-thread.1659965/page-28#post-17611543 RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-10-17 (2015-10-09, 17:35)Milhouse Wrote:(2015-10-09, 14:18)doveman2 Wrote: Is there anything in this log that shows why Putty/SSH isn't working on my brother's RPi v2? I checked in the OE settings addon that SSH is enabled and deleted the files in .cache/ssh to let it recreate them. I can connect with WinSCP, which I think uses the same SSH key but when I try with Putty it can't connect and I just get an empty black window until I cancel it. I just had a chance to gather a PuTTY log from his machine. It gets to "Doing Diffie-Hellman group exchange" before it gets stuck. http://pastebin.com/FNiWv8YQ RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-10-17 (2015-10-17, 19:41)hdmkv Wrote: Worth a shot. Will try later today. Also I'd like to know if unplugging and replugging the hdmi cable fixes the issue. If it does it means we are outputting a valid signal, but the projector didn't spot the change. If it doesn't it probably means we are outputting the wrong signal. I did ask our hdmi expert about this issue: Quote:he "old" HDMI spec does not specify a way of exiting 3D mode (shame on HDMI LLC). Hence some TVs will get stuck when the source is no longer sending a 3D signal. HDMI 2.x spec mandates TVs must switch back to 2D mode when the 3D side band signal is absent (basically we just stop sending VS infoframe when exiting 3D mode). I don't think there is anything the source can do other than unplug/plug back the cable or output a different format to force the TV to resync again. I'm surprised TVs will not react to the difference between full frame packing and 2D signal as the timings are different. I will expect TV not reacting to switching between side by side/top-bottom and 2D mode only. [Of course there will always be TVs which can only enter 3D mode and remember the last seen 3D mode until "no signal" and a new 3D mode is observed, which is probably the user's problem]. My suspicion is that the projector is badly implemented and doesn't react to the 3D signalling going away. It must be possible to "persuade" it to switch to 2D. It seems sending many seconds of "muted" video didn't help. Other options are to drop the signal for a short period (i.e. power off the HDMI output), or switch temporarily to a very different signal (e.g. VGA60). I attempted the second option before, but obviously broke something. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - speising - 2015-10-17 (2015-10-17, 03:09)doveman2 Wrote:(2015-10-17, 02:35)Milhouse Wrote: Doesn't tvheadend have it's own log? Is tvheadend listening on port 9981? Does tvheadend work with #1015 (the only difference between the two builds should be the way libnfs is compiled)? You can see the tvh logging in journalctl. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - hdmkv - 2015-10-17 Quote:Also I'd like to know if unplugging and replugging the hdmi cable fixes the issue.Nope. @BubbleBobble, thanks for your suggestion. Should have thought of this myself before. Anyway, after months of trying to figure out why the display blanking out was happening, I've found the cause... my AVR, an Onkyo TX-NR636. When I connect directly to my Epson 5025UB, no problems... it always comes back to the Kodi UI after every playback & stop. So, I looked at my NR636's menu and ensured video was being passed through as it, without any processing. Lip synch under HDMI was enabled, so turned that off too. Also made sure latest firmware was installed on the Onkyo. Didn't help, as issue returned as soon as I connected my Pi2 via the Onkyo. I don't get it why though... my Chromebox, HiMedia Q5, Zidoo X6 and TiVo, all connected by this same AVR don't exhibit the issue. Why only Pi2? Also, the Onkyo NR636 is/was a hugely popular AVR. When I have time tomorrow, may drag my Pioneer 5.1 AVR from another room and try via Epson. Edit: Just found this; Onkyo may indeed have some HDMI connectivity issues . Rated best receiver by Wirecutter too. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-10-17 (2015-10-17, 22:28)speising Wrote: You can see the tvh logging in journalctl. Ah, thanks. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - BubbleBobble - 2015-10-17 @hdmkv Glad you tackled your problem I feel your pain... my Anthem AVR got great reviews too but messes up when it comes to hdmi. I solved it by splitting hdmi and demoted my AVR to just decode audio, no display connected to it. (I am using this splitter. Port 3 & 4 strips hdcp too btw.. see video on the seller page) Before the splitter i have 'Dr HDMI' so every source "gets" the right info (EDID) I have 7.1 audio, 3D, full HD, etcetera. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-10-18 New OpenELEC Jarvis build #1017: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (3f210547, changelog) and tip of XBMC master (3acbdec9, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-10-18 (2015-10-17, 22:53)hdmkv Wrote: @BubbleBobble, thanks for your suggestion. Should have thought of this myself before. Anyway, after months of trying to figure out why the display blanking out was happening, I've found the cause... my AVR, an Onkyo TX-NR636. When I connect directly to my Epson 5025UB, no problems... it always comes back to the Kodi UI after every playback & stop. I've seen a few issues with Onkyo and banding or stutter caused by its video processing. Even in "through" mode, it still replaces the video signal with its own version (so it can overlay OSD info) and there are reports that this causes issues. Some Onkyo models have a secret mode which disables any processing (including OSD) which has fixed issues for some. See: https://www.avforums.com/threads/onkyo-video-processor-is-the-cause-of-video-colour-banding.1957818/ BTW, I have an Onkyo TX-NR609 and that doesn't have the 3D switching issue. |