Kodi Community Forum
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... Smile

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
Code:
tvservice -m CEA
or post a debug log (wiki)

Trying to watch 3D Bluray ISO outputs 2d only. Besides this issue, If i enable Frame packing i get a black screen with audio on some MKV movies.

this is my output for an LG 3D TV and RPi2;

Code:
Group CEA has 15 modes:
           mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
           mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
           mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
  (native) mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive 3D:FP|TopBot|SbS-HH
           mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced 3D:TopBot|SbS-HH
  (prefer) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive 3D:SbS-HH
           mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
           mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
           mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive 3D:FP|TopBot|SbS-HH
           mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced 3D:TopBot|SbS-HH
           mode 21: 720x576 @ 50Hz 4:3, clock:27MHz x2 interlaced
           mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive 3D:SbS-HH
           mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive 3D:FP|TopBot|SbS-HH
           mode 33: 1920x1080 @ 25Hz 16:9, clock:74MHz progressive
           mode 34: 1920x1080 @ 30Hz 16:9, clock:74MHz progressive 3D:TopBot|SbS-HH

EDIT: Sorry, I just read that this topic is not for OpenElec builds and i'm using OE isengard Beta 2

(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

Correct, this is not a general OpenELEC support thread... Smile

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.

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
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : [email protected]
Format settings, CABAC                   : Yes
Format settings, ReFrames                : 2 frames
Codec ID                                 : V_MPEG4/ISO/AVC
Duration                                 : 2h 10mn
Nominal bit rate                         : 16.0 Mbps
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 23.976 fps
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.322

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
when playing the 3D video (in both FP enabled and disabled cases).


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
Code:
tvservice -s
when playing the 3D video (in both FP enabled and disabled cases).

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 Smile
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
Linux rpi512 4.0.5 #1 Wed Jun 17 21:26:09 BST 2015 armv6l GNU/Linux

# vcgencmd version
Jun 17 2015 13:33:27
Copyright (c) 2012 Broadcom
version 1352d17ed6bd078120ac262b8c45b5b3a0d398de (clean) (release)

# lsb_release
OpenELEC (Milhouse) - Version: devel-20150617212443-#0617-gbd0c825 [Build #0617]

# vcdbg log msg 2>&1 | grep DTOK
001551.492: Kernel trailer DTOK property says yes

# Kernel device tree status: Enabled

Based on tip of OpenELEC master (bd0c8255, changelog) and tip of XBMC master (5506bb39, changelog) with the following modifications: Build Highlights:
  1. New firmware
  2. FontTTF scissor fix
Build Details:
  1. Firmware (Jun 17):
    • firmware: dispmanx: Rotate clipped coordinated when display is rotated. See: link
    • firmware: arm_display: Avoid holding lock while waiting for vsync with rotated display. See: link
    • firmware: dispmanx: Fix order of scale and flip for dispmanx_snapshot. See: link
    • firmware: arm_loader: Fix force_core for 2836 and add disable SMP/L2 option
    • firmware: qpu_execute: Optionally launch qpus explicitly on first N qpus
    • firmware: qpu_execute: Enable profiling options for qpu_execute
  2. OpenELEC:
    • Configure RPi/RPi2 platform with optimal CPU and IO settings (PR:4200, 1 commit, 2 files changed)
    • linux: switch to linux-4.1 for generic/legacy (PR:4193, 1 commit, 29 files changed)
    • move 'set ondemand threshold' to init (PR:4201, 1 commit, 3 files changed)
    • xorg-server: update to xorg-server-1.17.2 (fae869a3)
    • pvr.vbox: update to pvr.vbox-b8dff38 (8b130e53)
  3. XBMC:
    • dvdplayer: fix ff/rw after ea6e82997bd6087a7beff1be0ef9b34847fe3cc7 (PR:7292, 1 commit, 1 file changed)
    • [pvr] bump pvr.hts to 2.1.10 (PR:7295, 1 commit, 1 file changed)
    • dvdplayer: fix vc1 hwaccel like vdpau - work around an ffmpeg issue (PR:7298, 1 commit, 1 file changed)
    • [lang] Fix overlapping kaitoast messages (PR:7296, 1 commit, 1 file changed)
    • [win32] Fixed libcurl initialization when the env variable OPENSSL_CO… (PR:7294, 1 commit, 1 file changed)
  4. pvr.hts:
    • Lower required HTSP version to 10 (allows tvh 3.4 again). (PR:42, 1 commit, 5 files changed)
  5. newclock4:
    • New commits in this build:
      • Fixed: FontTTF breaks scissor which causes bad rendering with dirty regions. (0b5dda53)
  6. kernel 4.0.y:
    • New commits in this build:
      • BCM270x_DT: Default Compute Module i2c, i2s and spi support (077e7ea6)



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.

ffmpeg supports SBS and TAB but not MVC. The Pi has support for MVC in firmware, therefore MVC will be an upcoming feature of Kodi 15 but *only* on Pi hardware (which has "native" hardware support).

MVC will be supported in a future Kodi release on all platforms if/when ffmpeg adds MVC support (although there is little sign of this happening any time soon - the changes required are not trivial). Platforms are also free to add their own native support if they choose to do the legwork (ask your device manufacturer).

If you want to discuss MVC support in Kodi for non-Pi platforms, you should start a new thread.

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:
(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.
Thanks for the explanation there Milhouse.
I'll try adjusting the sdclock back to stock.