OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) 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 (Kodi 15.0) Part 2 (/showthread.php?tid=224025) |
Re: RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-06-17 (2015-06-17, 15:53)rubenmb Wrote: EDIT: Sorry, I just read that this topic is not for OpenElec builds and i'm using OE isengard Beta 2 Correct, this is not a general OpenELEC support thread... Switch to one of the test builds announced in this thread and continue posting if you still have a 3D problem, or start a new thread if you are having problems with the official OpenELEC build. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - rubenmb - 2015-06-17 (2015-06-17, 15:53)rubenmb Wrote:(2015-06-17, 12:20)popcornmix Wrote: Is your TV reporting 3D support in it's edid? Can you post output of (2015-06-17, 16:02)Milhouse Wrote:(2015-06-17, 15:53)rubenmb Wrote: EDIT: Sorry, I just read that this topic is not for OpenElec builds and i'm using OE isengard Beta 2 Ok, just switched to latest testbuild: Exact same behaviour shown on both 3D Bluray ISO (tried with FP both on and off and it still seems as Kodi won't detect its 3D) and MKV outputting blackscreen. MKV mediainfo: Code: Video Sorry for long post, just trying to keep things comprehensible. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-06-17 @rubenmb: Upload a full debug log (wiki) to xbmclogs.com, include your attempts to play your file in the debug log. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - popcornmix - 2015-06-17 @rubenmb can you report output of Code: tvservice -s RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - rubenmb - 2015-06-17 (2015-06-17, 16:40)Milhouse Wrote: @rubenmb: Upload a full debug log (wiki) to xbmclogs.com, include your attempts to play your file in the debug log. Here ya go: http://goo.gl/SlhuPP (2015-06-17, 16:47)popcornmix Wrote: @rubenmb can you report output of Frame-Packing ON: MKV (Black Screen) Code: state 0x12001a [HDMI CEA (32) 3D FP RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive 3D Bluray ISO (No 3D detected, monoscopic playback only) Code: state 0x12001a [HDMI CEA (32) RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive Frame-Packing OFF: MKV (3D display H-OU) Code: state 0x12001a [HDMI CEA (32) 3D T&B RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive 3D Bluray ISO (No 3D detected, monoscopic playback only) Code: state 0x12001a [HDMI CEA (32) RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive Although that output will show 23.98Hz, my TV says 24Hz is being displayed on OSD. This may sound stupid, but just to make sure... We are supposed to initiate 3D Bluray playback through "Play Main Title" right? Thank you both for taking the time to implement and debug this feature, which is, for me personally, a must have. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - popcornmix - 2015-06-17 Are you saying you get a blank screen in both cases? Is it just video that is blank, or whole gui (i.e. can you see OSD?) RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - rubenmb - 2015-06-17 I only get black screen on MKV with FP ON in certain files, others still display correctly. BluRay will display image but only 2D. In all cases GUI will display correctly including subtitles. EDIT: After further testing i realized i can only reproduce the blackscreen issues on H-OU / H-TB movie files. Which seems reasonable to assume given the fact its an underestimated and a bit forgotten format Anyway, all my SBS files play fine with Frame-Packing on. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - wezley98 - 2015-06-17 @Milhouse think I know what was causing the issue with disabling tv in #616 Vbox tv addon was enabled by default which meant I had tvheadend and Vbox PVR enabled. This caused live tv not to work and kodi to crash when disabling live tv in settings. Note to anybody else having the issue, goto PVR addons and disable any PVR addon's that have become enabled other than the one you use, in my case tvheadend. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-06-17 Thanks wezley98. Although uploading the crashlog may still be useful (assuming it contains anything useful) as enabling multiple PVR clients shouldn't result in a crash. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - bagofcrap24 - 2015-06-17 Have been using the same build (529) for quite some time without issues. Twice tonight i have a kodi.bin crash loop. (kodi crashes, goes back to kodi startup screen and just keeps repeatedly crashing on the startup screen) here a crashlog - http://pastebin.com/ie2nFq9G The only thing I have touched recently is changing from "resamle audio" for sync method to "adjust pll". could this have any effect as i dont use adjust refresh rate to match display. (video signal is required to be at 60hz, dont ask why) I will update to the latest build and see how things go. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-06-18 (2015-06-17, 23:54)bagofcrap24 Wrote: I will update to the latest build and see how things go. Nothing very useful in the crashlog unfortunately, although this might actually suggest it's not a software bug but instead hardware instability. You are overclocked, including sdram_freq=500, and build #0523c introduced new firmware that means a few high powered bits of code are now running simultaneously (e.g. ARM+VPU+QPU+H264 code) which stresses the Pi a bit more. I fell foul of this change myself, experiencing odd/unexplainable crashes, kodi restart loops etc., and rather than bump over_voltage_sdram to stabilise the system I simply dropped the sdram_freq=500 overclock as this provides marginal benefit on the Pi2 (the Pi2 has more cache than the Pi1, and the sdram package is on the other side of the board unlike the Pi1 where the sdram package is on top of the CPU) . Since reverting to stock sdram_freq my Pi2 has been solid as a rock (again). So my money at this stage would be on your overclock being slightly marginal. Remove the sdram overclock or, if you prefer, try bumping the sdram voltage. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-06-18 New OpenELEC Isengard build #0617: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (bd0c8255, changelog) and tip of XBMC master (5506bb39, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - popcornmix - 2015-06-18 (2015-06-17, 23:54)bagofcrap24 Wrote: The only thing I have touched recently is changing from "resamle audio" for sync method to "adjust pll". could this have any effect as i dont use adjust refresh rate to match display. (video signal is required to be at 60hz, dont ask why) Well, the obvious thing to try is to switch it back, but no I don't think that is your issue. As Milhouse says, at the first sign of instability disable overclock. Most likely the sdram overclock. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - brummfax - 2015-06-18 (2015-06-17, 15:55)Milhouse Wrote:(2015-06-17, 12:07)brummfax Wrote: I don't understand your answer. 3D support for SBS and TAB-files was one of the main features of XBMC 13.2 regardless of any specific firmware. So my question is whether or not the support of the MVC-codec discussed in this thread will also be a feature of the upcoming Kodi 15.0 or higher. Thanks for the explanation. Now I understand the problem and will start a thread in the QNAP forum to bring attention to the (possible) MVC support of their firmware. Best wishes! RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - bagofcrap24 - 2015-06-18 (2015-06-18, 00:19)Milhouse Wrote:Thanks for the explanation there Milhouse.(2015-06-17, 23:54)bagofcrap24 Wrote: I will update to the latest build and see how things go. I'll try adjusting the sdclock back to stock. |