[scotty144]

Hello, first post here.

I am very excited to have my raspberry pi2 up and running with the latest Milhouse build. I am however having some issues with 3D.

All of my 3d iso files are stored on external hard drives on my PC and I am using windows SMB share to connect.

The movies will all play fine in 2D but unfortunately the vast majority will not work in 3D. When I am presented the option after it loads the ISO I choose "play with 3D mode". Most times it attempts to start the movie and then Kodi stops and reboots itself. Some instances, the movie will play for a minute or two and then reboots in the same fashion.

I have configured it as was instructed in the first post.

Am I missing something? or perhaps someone may have other suggestions.

Thanks in advance.

[Milhouse]

My latest builds are now based on Kodi 16, you should try a test build from here or if you prefer to continue using Kodi 15 then download the latest official OpenELEC 5.95.5 beta.

[scotty144]

Thanks for the suggestion Milhouse. I upgraded to your latest test build but unfortunately I'm still experiencing the same problem. Do I need to purchase the codecs to get it to function?


Thanks

[Milhouse]

I wouldn't have thought so - post a link to your debug log (wiki) from build #0924 while playing one of your movies, in the Kodi 16 test thread.

[bledd]

Hi Milhouse, is there a latest 15.2 nightly?

I seem to get buffering issues on the 5.95.5 beta build.

[Milhouse]

Hi Milhouse, is there a latest 15.2 nightly?

I seem to get buffering issues on the 5.95.5 beta build.

No, I'm no longer building 15.x. If you want continued nightlies you'll need to switch to Kodi 16.

[bledd]

Gotcha

[lollo78]

These are my (@Milhouse) benchmark results when using a class 6 NOOBS 8GB SD card in a RPi2. Results are from this script:

Code:

Overlay config                      core_freq   turbo   overclock_50    WRITE        READ        HDPARM
dtoverlay=mmc                          250        0      41.667 Mhz    6.06 MB/s   18.21 MB/s   18.54 MB/s   [1]
dtoverlay=mmc,overclock_50=63          250        0      62.500 Mhz    5.95 MB/s   26.47 MB/s   26.58 MB/s
dtoverlay=sdhost                       250        0      50.000 Mhz    5.90 MB/s   21.49 MB/s   21.64 MB/s
dtoverlay=sdhost,overclock_50=63       250        0      62.500 Mhz    5.93 MB/s   26.34 MB/s   26.80 MB/s
dtoverlay=sdhost,overclock_50=84       250        0      83.333 MHz    5.98 MB/s   34.00 MB/s   34.87 MB/s

dtoverlay=mmc                          250        1      41.667 MHz    6.03 MB/s   18.28 MB/s   18.48 MB/s   [1]
dtoverlay=mmc,overclock_50=63          250        1      62.500 MHz    6.01 MB/s   26.61 MB/s   27.15 MB/s
dtoverlay=sdhost                       250        1      50.000 MHz    6.03 MB/s   21.50 MB/s   22.00 MB/s
dtoverlay=sdhost,overclock_50=63       250        1      62.500 MHz    6.06 MB/s   26.35 MB/s   27.15 MB/s
dtoverlay=sdhost,overclock_50=84       250        1      83.333 MHz    6.00 MB/s   34.02 MB/s   35.41 MB/s

dtoverlay=mmc                          500        0      41.667 MHz    5.89 MB/s   18.21 MB/s   18.32 MB/s
dtoverlay=mmc,overclock_50=63          500        0      62.500 MHz    5.96 MB/s   26.48 MB/s   26.58 MB/s
dtoverlay=mmc,overclock_50=84          500        0      62.500 MHz    5.90 MB/s   26.46 MB/s   26.58 MB/s   [2, 3]
dtoverlay=sdhost                       500        0      50.000 MHz    5.99 MB/s   11.25 MB/s   11.18 MB/s   [4]
dtoverlay=sdhost,overclock_50=63       500        0      62.500 MHz    5.94 MB/s   13.97 MB/s   13.91 MB/s   [4]
dtoverlay=sdhost,overclock_50=72       500        0      71.429 MHz    5.96 MB/s   15.89 MB/s   15.79 MB/s   [4]
dtoverlay=sdhost,overclock_50=84       500        0      83.333 MHz    6.01 MB/s   18.35 MB/s   18.30 MB/s   [4]
dtoverlay=sdhost,overclock_50=100      500        0     100.000 MHz    6.00 MB/s   21.78 MB/s   21.76 MB/s   [4]

dtoverlay=mmc                          500        1      41.667 MHz    6.11 MB/s   18.31 MB/s   18.48 MB/s   [1]
dtoverlay=mmc,overclock_50=63          500        1      62.500 MHz    6.14 MB/s   26.67 MB/s   27.24 MB/s
dtoverlay=mmc,overclock_50=84          500        1      62.500 MHz    6.06 MB/s   26.66 MB/s   27.24 MB/s   [2]
dtoverlay=sdhost                       500        1      50.000 MHz    6.12 MB/s   21.50 MB/s   22.01 MB/s
dtoverlay=sdhost,overclock_50=63       500        1      62.500 MHz    6.11 MB/s   26.34 MB/s   27.15 MB/s
dtoverlay=sdhost,overclock_50=72       500        1      71.429 MHz    6.05 MB/s   29.69 MB/s   30.82 MB/s
dtoverlay=sdhost,overclock_50=84       500        1      83.333 MHz    6.06 MB/s   34.01 MB/s   35.53 MB/s
dtoverlay=sdhost,overclock_50=100      500        1     100.000 MHz    6.14 MB/s   39.81 MB/s   41.72 MB/s

Observations:

1. The MMC driver with default clock won't achieve a 50MHz clock due to even divisor requirement (250/50 => 5, which isn't supported by the mmc driver). Nearest clock frequency with an even divisor (6) is 41.667MHz. However, at 500MHz core_freq, an even divisor of 10 would give 50MHz...
   
2. The MMC driver won't accept an 84MHz overclock with core_freq=500 - this should be a divisor of 6 (even) (see explanation)
   
3. The performance of the SDHost driver is comparable with the MMC driver at lower overclocks, however the former supports both odd/even divisors whereas the latter is limited to even divisors
   
4. The performance of the SDHost driver suffers significantly at higher core_freq with force_turbo disabled. Probably best not to use sdhost at higher core_freq unless force_turbo is enabled. Turbo can be enabled in config.txt, or with:
   
   Code:

   echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
   (Edit: Fixed in build #0616 with the introduction of PR:4200)
   

Possible mmc/sdhost overclocks, based on various core frequencies - adjust core frequency to enable a specific overclock_50 frequency (bracketed items may be too high/unstable):

Code:

Core     mmc            sdhost
Freq     overclock_50   overclock_50

250      63             63,84
275      63             55,69,92
300      63             60,75,100
325      63             55,65,82,(109)
350      63             59,70,88,(117)
375      63             54,63,75,94
400      63             58,67,80,100
425      63             54,61,71,85,(107)
450      63             57,65,75,90,(113)
475      63             53,60,68,80,95,(119)
500      63             56,63,72,84,100

[/list]
Build Details:

1. OpenELEC:
   • linux: for imx6 include soc fan and status led packages (PR:4152, 1 commit, 1 file changed)
     
2. XBMC:
   • [Libcurl] 404 fix + misc. tweaks (PR:7137, 2 commits, 2 files changed)
     
   • Added KEY_PLAYCD and KEY_PAUSECD for linux support of BT headphones (PR:7132, 1 commit, 1 file changed)
     
   • FIX: [stf;3D] stagefright is no longer flipped in Y (PR:7140, 1 commit, 1 file changed)
     
   • [cmake] add libplatform to kodi-platform depends (PR:7069, 5 commits, 29 files changed)
     
3. dcadec:
   • Don't force 2.0 downmix with KEEP_DMIX_2CH flag alone. (bc08f9ef)
     
   • Add a test suite. (37d8e689)
     
4. newclock4:
   • New commits in this build:
     • squash: shadertoy: Fix include file path (ffeb97af)
       
     • [omxplayer] Make unsupported when ac3transcode is enabled (8b322831)
       
5. kernel 4.0.y:
   • New commits in this build:
     • bcm2835-sdhost: Error handling fix, and code clarification (63c657c6)
       
     • bcm2835-sdhost: Adding overclocking option (0dee18d8)
       
     • bcm2835-mmc: Adding overclocking option (ea47dbff)
       
     • dmaengine: bcm2708: set residue_granularity field (22374422)
       
     • Merge pull request #965 from HiassofT/dmafix-4.0 (6fc1a8cf)
       
     • BCM2708_DT: Adding starter Compute Module DTS files (125160bc)
       
     • squash: Fix up the mmc overlay (36080081)
       

@Milhouse
Hi dear! I see your post about mmc and sdhost overclock, with your test and benchmark.
I'm little confused... I don't undestand if I can use both mmc and sdhost overclock at the same time of if I have to use only one of it.

A configuration like this could be OK?

Code:

arm_freq=980
  core_freq=400
  sdram_freq=400
  over_voltage=2
  dtoverlay=mmc,overclock_50=63
  dtoverlay=sdhost,overclock_50=80

or I have to use only one from

Code:

arm_freq=980
  core_freq=400
  sdram_freq=400
  over_voltage=2
  dtoverlay=mmc
  dtoverlay=sdhost
  dtoverlay=sdhost,overclock_50=80

or

Code:

arm_freq=980
  core_freq=400
  sdram_freq=400
  over_voltage=2
  dtoverlay=mmc
  dtoverlay=sdhost
  dtoverlay=mmc,overclock_50=63

??
thx a lot

[Milhouse]

@lollo78: Use only one.

[Warez]

You can use this to set the overclock: https://copy.com/QxVJviOzkwf3yjzH/script...download=1

[Tsyko]

I searched the thread for HDMI Passthrough but none of the issues seem the same as mine

When I run the Public 6.0.0 on the RPI2 using my Yamaha amp. The amp says DTS or Dolby Digital with passthrough enabled.

When I run the Chris Swan devel builds I run Jarvis and the amp behaves the same.

On the millhouse builds even with Passthrough enabled the amp says PCM.

Am I doing something wrong with my setup?

Thanks for the help in advance

[Milhouse]

There's no further support for these old test builds which pre-date current official releases. Switch to the Kodi 16 test builds and post there if you still have a problem.

[Milhouse]

Closing thread - testing continues in the Kodi 16 thread.