Kodi 18 - LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

  Thread Rating:
  • 6 Vote(s) - 4.83 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
Kougami Offline
Junior Member
Posts: 28
Joined: Nov 2015
Reputation: 0
Post: #1591
(2017-04-26 22:51)Milhouse Wrote:  
(2017-04-26 11:19)Kougami Wrote:  Seems "Adjust display refresh rate: Always" cause the very low free gpumem.

Playing my testfile 4x with disabled "Adjust display refresh rate":
bcmstat: https://pastebin.com/Km8syTLS


Playing my testfile 4x with always "Adjust display refresh rate":
bcmstat: https://pastebin.com/DWqiq6RC
log: http://sprunge.us/DAaF
Thanks, this has been reproduced and a fix should be in tonight's build (which should be available in an hour or two from now).

I can confirm with #0426, my issue is fixed. Thanks.
find quote
asavah Offline
Senior Member
Posts: 256
Joined: Sep 2014
Reputation: 10
Post: #1592
(2017-04-27 09:46)skylarking Wrote:  To see native functions removed and migrated to an add-ons seems OK on the surface.
And if the end result is a cleaner code base that supports aded features, it can only be a good thing.
However, when there seems to be a waning desire for the coders to actually keep the functionality that made Kodi what it is, it becomes a little concerning as to what lovers of Kodi will end up with.

And yes, 'waning desire' is speculation on my part as 'i know nothing' about how the team coordinates the tasks at hand, nor the people involved.
I know it's open source and all, but i'd have thought as part of a cleanup and add-on migration activities, the coders actually removing stuff would have at least migrated the functionality into an add-on and verified that the functionality they moved still works.

It just seems odd to me that code and thus functionality can be so easily removed, a wild west of coding as such with an obvious end result of a loss of functionality.

@Millhouse, i don't believe it's an issue of your making and do appreciate your efforts in providing these edgy LE PRi builds.
If your not too busy, maybe you can enlighten me as to why this is happening and what features we may fall from the table?

You should be aware that these excellent @Milhouse's builds are bleeding edge, and are based on current master code, which may contain bugs and regressions, that's why these builds exist - to help the devs hunt the bugs long before new code hits the rest of the users who use release versions.
Eventually new binary addons replacing built-in functionality will be fixed. AFAIK there is huge rework of addon related code incoming, so it may be inefficient to spend developer time now to fix/improve this stuff. We'll have to wait.

If you want stable non-breaking functionality - use releases, but if you want to help Kodi become better and better by testing 0day stuff you may have to suffer a breakage or two from time to time Tongue
find quote
popcornmix Offline
Team-Kodi Member
Posts: 7,865
Joined: Feb 2011
Reputation: 326
Post: #1593
(2017-04-22 10:51)SpokV Wrote:  Hi. I've uploaded crashlog from 420,421. Happens when streaming video via network.419 works fine.
It seems to do with the ffmpeg buffer increase. Not sure...

Can you confirm if this crash still occurs with latest build?
I think it will be resolved in tonight's build (when ffmpeg buffer increase is reverted) but there is a possible fix in last night's build we'd be interested in knowing about.
(This post was last modified: 2017-04-27 14:45 by popcornmix.)
find quote
SpokV Offline
Junior Member
Posts: 44
Joined: Mar 2016
Reputation: 0
Post: #1594
(2017-04-27 14:44)popcornmix Wrote:  
(2017-04-22 10:51)SpokV Wrote:  Hi. I've uploaded crashlog from 420,421. Happens when streaming video via network.419 works fine.
It seems to do with the ffmpeg buffer increase. Not sure...

Can you confirm if this crash still occurs with latest build?
I think it will be resolved in tonight's build (when ffmpeg buffer increase is reverted) but there is a possible fix in last night's build we'd be interested in knowing about.

I've checked on today's build and it's still there. I'll check the tonight's build too.
find quote
doveman2 Offline
Posting Freak
Posts: 1,135
Joined: Nov 2012
Reputation: 2
Post: #1595
(2017-04-27 08:09)Milhouse Wrote:  The "Install from Zip file" home screen widget has never worked.

If you want to install from a zip file, use Addons > Add-on browser > Install from zip file

Thanks, that did the trick.

I'm still not having any luck with TVheadend using #426 with your TVheadend build #426 though. lsusb shows my tuner is recognised

Bus 001 Device 005: ID 1b80:e409 Afatech IT9137FN Dual DVB-T [KWorld UB499-2T]
Bus 001 Device 007: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 006: ID 046e:5577 Behavior Tech. Computer Corp.
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

but no tuners are listed in the browser GUI (http://192.168.1.85:9981) under Configuration - DVB Inputs - TV Adapters.

There's some errors in the log about TVheadend Client but I don't think they matter at the moment, it's the service I'm having problems with.

http://sprunge.us/DBWN

Quote:It looks like you have two NFS shares, and Kodi maintains only a single NFS context. When you're requesting information from Media and then from Torrents, and then again from Media, and then again from Torrents, Kodi is continually having to refresh it's single NFS context (which then spams the debug log).

Perhaps if you had a single NFS export, eg. 192.168.1.64/share, and then within your "share" export you have Media and Torrents directories, so that Kodi can access all of the content via a single NFS context.

However I don't really know if refreshing the NFS contexts is a particularly "expensive" (time consuming) process, so it may not be worthwhile and you'll just have to put up with the debug log spam.

Ah, OK. I'll limit it to one NFS share then. Even if it's not causing any resource issues, I'd like to stop the log spam occurring.
(This post was last modified: 2017-04-27 19:38 by doveman2.)
find quote
bkuhls Offline
Junior Member
Posts: 47
Joined: May 2013
Reputation: 1
Post: #1596
(2017-04-25 12:40)popcornmix Wrote:  So are you happy with the last ffmpeg 3.3 build?
Hopefully we'll be returning to that soon (maybe tonight) as we have some possible audio fixes.
Hi,
do you mean the patch "AESinkPULSE: Return to PA's delay infrastructure"?

If yes, then I can say that backporting this patch to Krypton fixed the
audio crackles with ffmpeg-3.3 Smile Imho this patch should be backported
to Krypton.
find quote
SpokV Offline
Junior Member
Posts: 44
Joined: Mar 2016
Reputation: 0
Post: #1597
(2017-04-27 16:46)SpokV Wrote:  
(2017-04-27 14:44)popcornmix Wrote:  
(2017-04-22 10:51)SpokV Wrote:  Hi. I've uploaded crashlog from 420,421. Happens when streaming video via network.419 works fine.
It seems to do with the ffmpeg buffer increase. Not sure...

Can you confirm if this crash still occurs with latest build?
I think it will be resolved in tonight's build (when ffmpeg buffer increase is reverted) but there is a possible fix in last night's build we'd be interested in knowing about.

I've checked on today's build and it's still there. I'll check the tonight's build too.

It seems that 427 solved this issue. I'll continue run it and update for any change...thanks
find quote
Milhouse Offline
Team-Kodi Member
Posts: 12,883
Joined: Jan 2011
Reputation: 643
Post: #1598
New LibreELEC.tv Leia build #0427: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.10.13 #1 Thu Apr 27 21:08:33 BST 2017 armv6l GNU/Linux

# vcgencmd version
Apr 27 2017 17:27:25
Copyright (c) 2012 Broadcom
version 17af5814bb19dbb7c70ccd2c845b80a160943811 (clean) (release)

# lsb_release
LibreELEC (Milhouse) - Version: devel-20170427210352-#0427-ga5bf4d2 [Build #0427]

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

Based on tip of LibreELEC.tv master (a5bf4d28, changelog) and tip of XBMC master (69f4545b, changelog) with the following modifications: Build Highlights:
  1. New firmware (revert max_usb_current for B+/Pi2)
  2. New 4.10.13 kernel
  3. connman: update to 1.34 and drop patches
  4. Kodi: Revert "DVDDemuxFFMPEG: Increase FFMPEG_FILE_BUFFER_SIZE to 128K"
  5. Drop incompatible pvr.iptvsimple bump
Build Details:
  1. Firmware (Apr 27):
    • firmware: bootcode: Revert Set max_usb_current pin for B+ and Pi2 See: link
  2. LibreELEC.tv:
    • connman: update to 1.34 and drop patches (PR:1569, 1 commit, 3 files changed)
  3. XBMC:
    • AE: improve tempo filter (PR:12002, 1 commit, 5 files changed)
    • Revert "DVDDemuxFFMPEG: Increase FFMPEG_FILE_BUFFER_SIZE to 128K" (PR:12013, 1 commit, 1 file changed)
    • [buildsteps][windows] correct evaluation of make jobs (PR:12010, 1 commit, 3 files changed)
    • [gui][refactor] add window id as arg to GetWindow template because window instance is not unique (PR:12003, 1 commit, 87 files changed)
    • For addon created ListItems dont overwrite playcount data from DB (#11998) (27dc9a69)
  4. newclock5:
    • Commits no longer in build:
      • filesystem: Make support of browsing into archives optional (b49b0cc9)
      • AE: improve tempo filter (23bc89b7)
      • DVDDemuxFFmpeg: Increase lifespan of probe_buffer (ffee0111)
  5. kernel 4.10.y:
    • New commits in this build:
      • brcmfmac: Ensure pointer correctly set if skb data location changes (326f7d87)
      • brcmfmac: Make skb header writable before use (c5139cc9)
      • clk: bcm2835: Limit PCM clock to OSC and PLLD_PER (ab508717)
      • dwc_otg: Add the dependency on FIQ (5f788bfc)
    • Commits no longer in build:
      • smsc75xx: use skb_cow_head() to deal with cloned skbs (ab3f594e)
  6. Additional commits/pull requests/changes not yet merged upstream:
    • Reverted: [pkg] PR:118: Remove not used part (reason: depends on unmerged PR12011) (pvr.iptvsimple)
    • Updated: [env] compare: linux: update to linux-4.10.13

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.
(This post was last modified: 2017-04-28 00:18 by Milhouse.)
find quote
Milhouse Offline
Team-Kodi Member
Posts: 12,883
Joined: Jan 2011
Reputation: 643
Post: #1599
@SpokV pvr.iptvsimple should be working again.

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.
find quote
SpokV Offline
Junior Member
Posts: 44
Joined: Mar 2016
Reputation: 0
Post: #1600
(2017-04-27 23:24)Milhouse Wrote:  @SpokV pvr.iptvsimple should be working again.

Yep. Many thanks.
find quote
Memphiz Offline
Kodi MVP
Posts: 16,092
Joined: Feb 2011
Reputation: 227
Location: germany
Post: #1601
@Milhouse - nfs contexts are refreshed only if a file is kept open on an export. As that folder is called "torrents" he might use a torrenting addon which of course has file handles open on that export.

AppleTV4/iPhone/iPod/iPad: HowTo find debug logs and everything else which the devs like so much: click here
HowTo setup NFS for Kodi: NFS (wiki)
HowTo configure avahi (zeroconf): Avahi_Zeroconf (wiki)
READ THE IOS FAQ!: iOS FAQ (wiki)
find quote
Milhouse Offline
Team-Kodi Member
Posts: 12,883
Joined: Jan 2011
Reputation: 643
Post: #1602
Ah right, yes that would make sense - thanks for the clarification.

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.
find quote
popcornmix Offline
Team-Kodi Member
Posts: 7,865
Joined: Feb 2011
Reputation: 326
Post: #1603
(2017-04-27 21:08)bkuhls Wrote:  do you mean the patch "AESinkPULSE: Return to PA's delay infrastructure"?

No. That will only affect users with pulse audio as the output device, which for the main distributions would only be bluetooth audio.
The patch that fixed the audio crackles for most users was PR12002.
find quote
mm00 Offline
Junior Member
Posts: 8
Joined: Apr 2016
Reputation: 0
Post: #1604
Milhouse, could you create a patched testbuild without this commit? https://github.com/Pulse-Eight/libcec/co...7d91f0f573

It might cause LG tvs strange behaviour in this topic: https://github.com/Pulse-Eight/libcec/issues/307
find quote
doveman2 Offline
Posting Freak
Posts: 1,135
Joined: Nov 2012
Reputation: 2
Post: #1605
(2017-04-28 07:39)Memphiz Wrote:  @Milhouse - nfs contexts are refreshed only if a file is kept open on an export. As that folder is called "torrents" he might use a torrenting addon which of course has file handles open on that export.
I'm not using any torrenting add-on, the folder just contains files I've downloaded via torrent on my PC, that I haven't moved to my Media folder yet.
find quote
Post Reply