•  Previous
  • 1
  • 238
  • 239
  • 240(current)
  • 241
  • 242
  • 249
  • Next 
 
Thread Rating:
  • 8 Vote(s) - 4.88 Average
Kodi 18 - LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)
Hey,

first of all thank you very much Milhouse for providing these builds.
However, when I try to download those testbuilds, it is only possible using an insecure http connection. Could you provide sha256 hashes via some https website for your testbuilds? That would be really kind Smile

Oh and a different thing! Is there already a coarse estimate on when the first official alpha/beta of libreelec 9 will be released? (I guess in recent years stable releases often showed up around the end of the year....)
Reply
When playing netflix 720p streams on my non-overclocked RPi3 I noticed that sometimes playback would become juddery, a/v get out of sync and then eventually recover after some time. My guess is this could be caused by bitrate spikes which the RPi can't quite handle and the usual A/V sync not kicking in (no skipped/dropped frames).

I can reproduce that repeatedly with Black Mirror S01E02, seeking to 59:30 after start:
- stream runs fine for a while, codecinfo overlay shows the usual +/- a few ten ms of AV offset
- after 20-30 seconds playback starts to get juddery and av offset increases, up to about 3 seconds. no skipped or dropped frames (I see skip 1 right from the beginning)
- as soon as the ending credits are displayed av offset goes back to normal

Here's a kodi debug log of that: http://sprunge.us/jWbJ

RPi3 temperature during this test was OK, although I didn't have a heatsink installed on that test system temperature didn't go up beyond 75°C (checked with vcgencmd measure_temp) and after the test vcgencmd get_throttled reported 0x0.

Any ideas how to improve that? Could limiting max bandwidth in inputstream.adaptive maybe help (haven't tried that)?

I've got a small heatsink installed on my main RPi3, so I could try a tiny bit of overclocking there, temps are a bit lower there but probably not much headroom for overclocking.

so long,

Hias
Reply
(2017-10-26, 16:33)HiassofT Wrote: When playing netflix 720p streams on my non-overclocked RPi3 I noticed that sometimes playback would become juddery, a/v get out of sync and then eventually recover after some time.

Limiting the bitrate to 5 MBit/s (5000000) should do the trick. I'm currently testing 6 MBit/s with an overclocked RPi 3 and get some stuttering from time to time.
Reply
(2017-10-26, 16:20)Mysterious Wrote: first of all thank you very much Milhouse for providing these builds.
However, when I try to download those testbuilds, it is only possible using an insecure http connection. Could you provide sha256 hashes via some https website for your testbuilds? That would be really kind Smile

I don't have any plans to create a separate checksum file (also, I don't have an https website available to me to host such a file).

If you use the built-in update mechanism it employs a sha256 checksum extracted from releases.json (in the same folder as the tar files) however this fails your https requirement.

If the lack of https is an issue with these test builds then I suggest you stick with official releases.

(2017-10-26, 16:20)Mysterious Wrote: Oh and a different thing! Is there already a coarse estimate on when the first official alpha/beta of libreelec 9 will be released? (I guess in recent years stable releases often showed up around the end of the year....)

December-ish.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
(2017-10-26, 16:33)HiassofT Wrote: I've got a small heatsink installed on my main RPi3, so I could try a tiny bit of overclocking there, temps are a bit lower there but probably not much headroom for overclocking.

Try this overclock:
Code:
arm_freq=1300
gpu_freq=500
over_voltage=4

sdram_freq=580
over_voltage_sdram=5
sdram_schmoo=0x02000020

It bumps the Pi3 ARM frequency by 100MHz, the GPU frequency by 200Mhz, and increases the SDRAM frequency by 130Mhz (580 is as high as I can go, but some can hit 600). This should help performance although it might increase temperatures a little so a heatsink or FLIRC case is recommended.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
Lightbulb 
little OT ...
I've got a big heatsink (Handmade) installed on all RPi3 & 2 :-)

Have a look to ->

https://drive.google.com/open?id=0B2rgZ0...zlreVZ4QWs

works fine for me with Milhouse config.
Reply
(2017-10-26, 19:06)Milhouse Wrote: I don't have any plans to create a separate checksum file (also, I don't have an https website available to me to host such a file).

If you use the built-in update mechanism it employs a sha256 checksum extracted from releases.json (in the same folder as the tar files) however this fails your https requirement.

If the lack of https is an issue with these test builds then I suggest you stick with official releases.

Well... how about posting hashes in this thread? The kodi.tv website uses https and I guess the overhead would not be too large... :/
Reply
(2017-10-26, 16:36)dantist Wrote:
(2017-10-26, 16:33)HiassofT Wrote: When playing netflix 720p streams on my non-overclocked RPi3 I noticed that sometimes playback would become juddery, a/v get out of sync and then eventually recover after some time.

Limiting the bitrate to 5 MBit/s (5000000) should do the trick. I'm currently testing 6 MBit/s with an overclocked RPi 3 and get some stuttering from time to time.

think thats a Netflix (addon) problem, not a limiting of Bitrate. 
Do you use a gigabite switch or a separate cable from router?

Because i notice this (your) problem also, if i switch my router from 100MB to 1 GB on the RPI Lan. 
BD50 Files over Network are stuttering, with 100MB all is ok.

Didn't find a working solution  - btw, I can live with 100MB ;-)
Reply
(2017-10-26, 16:36)dantist Wrote: Limiting the bitrate to 5 MBit/s (5000000) should do the trick. I'm currently testing 6 MBit/s with an overclocked RPi 3 and get some stuttering from time to time.
Thanks a lot for the hint, that was a good starting point!

I had to decrease the limit to 3 MBit/s to get good results with my testcase, when set to 4 MBit/s the actual max bitrate was still about 5.5-5.8 MBit/sec and I'd get stuttering and a/v delay.


(2017-10-26, 19:18)Milhouse Wrote: Try this overclock:
Code:
arm_freq=1300
gpu_freq=500
over_voltage=4

sdram_freq=580
over_voltage_sdram=5
sdram_schmoo=0x02000020

It bumps the Pi3 ARM frequency by 100MHz, the GPU frequency by 200Mhz, and increases the SDRAM frequency by 130Mhz (580 is as high as I can go, but some can hit 600). This should help performance although it might increase temperatures a little so a heatsink or FLIRC case is recommended.

Thanks for the hint as well, I'll do some test with these settings!

BTW: Does gpu overclock have any benefit for netflix / SW decoding?

I've got an I2S soundcard installed on my RPis, so cooling options are somewhat limited (there's about 1.5-2cm of vertical space between RPi and soundcard) and unfortunately a FLIRC case is out of question. I'm using no case though which could help a bit. But I'd better be on the conservative side concerning overclocking, the tiny heatsinks I have here don't look like they can dissipate too much heat.

so long & again thanks for your help,

Hias
Reply
New LibreELEC.tv Leia build #1026: RPi / RPi2
(Supercedes previous build)

SHA256 Checksum: c96ca3620b7d0749722c9487c9575aee896139f472ef52971299966d726951d7 (RPi)
SHA256 Checksum: 54739f66acd94478814017acf403a8beb9bd85bb4eb0660c65125a3bcb04e291 (RPi2)

Code:
# uname -a
Linux rpi512 4.13.9 #1 Thu Oct 26 21:04:41 BST 2017 armv6l GNU/Linux

# vcgencmd version
Oct 24 2017 17:13:32
Copyright (c) 2012 Broadcom
version a3d7660e6749e75e2c4ce4d377846abd3b3be283 (clean) (release)

# lsb_release
LibreELEC (Milhouse): devel-20171026210330-#1026-gb35141f [Build #1026]

# Kodi version
(18.0-ALPHA1 Git:e3d2cb5). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (b35141f, changelog) and tip of XBMC master (e3d2cb5, changelog) with the following modifications: Build Highlights:
  1. Fix for PVR service restart issue reported by @Gismo112
Build Details:
  1. LibreELEC.tv:
    • samba: fix authentication with Win10 Fall Creators Update (PR:2140, 1 commit, 1 file changed)
  2. XBMC:
    • [PVR] Ignore non-pvr addon changes. Fixes trac#17626. (PR:12958, 1 commit, 4 files changed)
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
(2017-10-26, 20:41)HiassofT Wrote: I've got an I2S soundcard installed on my RPis, so cooling options are somewhat limited (there's about 1.5-2cm of vertical space between RPi and soundcard) and unfortunately a FLIRC case is out of question. I'm using no case though which could help a bit. But I'd better be on the conservative side concerning overclocking, the tiny heatsinks I have here don't look like they can dissipate too much heat.

I had heat problems in my case from wdlabs, coming from the 2gb hdd i put in there with my RasPi.

Used a cooler from an old graphics card with a 2mm peace of copper as a spacer (so the cooler can't touch any electronics on the board). Used thermal adhesive instead of pads and the cooler is cut out to fit in between gpio, hdmi and camera connector. Works well, considering there is no active cooling.

Other option would be to use an old ide cable as an extender and place the soundcard somewhere else. Then you can cool down the RasPi however you want
Reply
(2017-10-26, 20:41)HiassofT Wrote: BTW: Does gpu overclock have any benefit for netflix / SW decoding?

Correct, a GPU overclock won't help with SW decoding, but it will help with hardware decoding (including HEVC).
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
(2017-10-26, 20:16)Mysterious Wrote: Well... how about posting hashes in this thread? The kodi.tv website uses https and I guess the overhead would not be too large... :/

OK, I've added the sha256 checksums to the last release post #1026, and will include them in future release posts.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
(2017-10-26, 20:27)doldi Wrote: think thats a Netflix (addon) problem, not a limiting of Bitrate. 
Do you use a gigabite switch or a separate cable from router?

I wasn't even aware that the RPi 3 has GBit LAN. Nice Smile And yes, it is connected through a GBit switch to my router. I'm pretty sure that bandwidth is not the problem, it's the software decoding.
Reply
That's because the Pi3 doesn't have any Gbit Lan...Image
Reply
  •  Previous
  • 1
  • 238
  • 239
  • 240(current)
  • 241
  • 242
  • 249
  • Next 



LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)4.888