•   
  • 1
  • 110
  • 111
  • 112(current)
  • 113
  • 114
  • 187
  •   
  Thread Closed
v17 LibreELEC Testbuilds for x86_64 (Kodi 17.0)
(2016-08-25, 22:21)kelsdogz Wrote:
(2016-08-25, 17:14)kelsdogz Wrote: Is there any way to force HW decoding?
I get high CPU usage when watching 1080p and discovered that system is using SW decoding no matter what setting are in player.
Same settings always used in previous versions(Helix, Jarvis), on same system, and it showed same CPU usage whether 1080 or not.

THANKS FOR ALL YOUR HARD WORK!

LOG
http://sprunge.us/aTYH

Quote:16:10:05 10.383188 T:139818767374400 NOTICE: GL_RENDERER = Mesa DRI Intel® 965GM
16:10:05 10.383207 T:139818767374400 NOTICE: GL_VERSION = 2.1 Mesa 12.0.1

You are kidding me? This device has no hw decoding support at all.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2016-08-25, 22:55)fritsch Wrote:
(2016-08-25, 22:21)kelsdogz Wrote:
(2016-08-25, 17:14)kelsdogz Wrote: Is there any way to force HW decoding?
I get high CPU usage when watching 1080p and discovered that system is using SW decoding no matter what setting are in player.
Same settings always used in previous versions(Helix, Jarvis), on same system, and it showed same CPU usage whether 1080 or not.

THANKS FOR ALL YOUR HARD WORK!

LOG
http://sprunge.us/aTYH

Quote:16:10:05 10.383188 T:139818767374400 NOTICE: GL_RENDERER = Mesa DRI Intel® 965GM
16:10:05 10.383207 T:139818767374400 NOTICE: GL_VERSION = 2.1 Mesa 12.0.1

You are kidding me? This device has no hw decoding support at all.

Sorry my ignorance! Be gentle.....
Trying to figure out what changed from 16.1 to cause my cpu usage to go up on 1080 playback on same system with 17.0
Thought maybe I had HW decoding that wasn't being used.
New LibreELEC.tv Krypton build #0825: Generic
(Supercedes previous build)

Code:
# uname -a
Linux NUC 4.7.2 #1 SMP Wed Aug 24 23:09:44 BST 2016 x86_64 GNU/Linux

# lsb_release
LibreELEC (Milhouse) - Version: devel-20160825234304-#0825-g20e8843 [Build #0825]

Based on tip of LibreELEC.tv master (20e8843a, changelog) and tip of XBMC master (23efa213, changelog) with the following modifications: Build Highlights:
  1. AESinkPULSE: Try to resolve channel layout
Build Details:
  1. LibreELEC.tv:
    • xf86-video-nvidia: update to 367.44 (PR:655, 1 commit, 3 files changed)
    • mono: update to 4.2.1.102 (PR:627, 4 commits, 7 files changed)
    • repository.kodinerds: initial package (PR:500, 1 commit, 4 files changed)
    • Odroid_C2: CEC/IR wake-up and boot-logo.bmp.gz support (PR:637, 8 commits, 15 files changed)
    • packages/linux-drivers/brcmap6xxx-aml: enable 40MHz channels for 2.4G (PR:656, 1 commit, 1 file changed)
    • tvheadend42: add debugging fix (PR:652, 1 commit, 4 files changed)
    • linux: update to linux-4.7.2 (PR:653, 4 commits, 30 files changed)
  2. XBMC:
    • [PVR] Recordings window: Respect setting SETTING_MYVIDEOS_SELECTACTIO… (PR:10333, 1 commit, 1 file changed)
    • [skin.estuary] Fix broken addon message (PR:10340, 1 commit, 1 file changed)
    • AESinkPULSE: Try to resolve channel layout - fallback if not possible fixes #16862 (PR:10341, 1 commit, 1 file 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.
(2016-08-25, 23:52)kelsdogz Wrote:
(2016-08-25, 22:55)fritsch Wrote:
(2016-08-25, 22:21)kelsdogz Wrote: LOG
http://sprunge.us/aTYH

Quote:16:10:05 10.383188 T:139818767374400 NOTICE: GL_RENDERER = Mesa DRI Intel® 965GM
16:10:05 10.383207 T:139818767374400 NOTICE: GL_VERSION = 2.1 Mesa 12.0.1

You are kidding me? This device has no hw decoding support at all.

Sorry my ignorance! Be gentle.....
Trying to figure out what changed from 16.1 to cause my cpu usage to go up on 1080 playback on same system with 17.0
Thought maybe I had HW decoding that wasn't being used.
Will look again tonight. Please try a build from one week ago and use Bob deinterlacer please.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2016-08-26, 07:29)fritsch Wrote:
(2016-08-25, 23:52)kelsdogz Wrote:
(2016-08-25, 22:55)fritsch Wrote: You are kidding me? This device has no hw decoding support at all.

Sorry my ignorance! Be gentle.....
Trying to figure out what changed from 16.1 to cause my cpu usage to go up on 1080 playback on same system with 17.0
Thought maybe I had HW decoding that wasn't being used.
Will look again tonight. Please try a build from one week ago and use Bob deinterlacer please.


Log from 8/19 build with Bob deinterlacer.
http://sprunge.us/OWBD
And now with v16 - same use case, please.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2016-08-26, 15:01)fritsch Wrote: And now with v16 - same use case, please.

Log using 16.1 with BOB deinterlacing. Same machine, 1080, showing only half the CPU usage with no stuttering, smooth playback.

http://sprunge.us/TCUJ
Don't want to take this thread off topic, but if any developers here are interested in helping me build LibreElec with latest Intel upstream driver code, please check this thread. Thanks.
I think you should go the Ubuntu route for debugging this - I can build you whatever kernel you want, after you are ready and working with: 231955 (thread)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
@ Milhouse/Fritsch

since build #0823 my system is a bit slow.
Using a Zotac ID41 (intel atom d525 with ion2).
navigating the library is sluggish and the rss feed stutters.
playing 1080p content is fine but the processor load seems to have more than doubled during playback,
normally it totals at 60% but since @0823 it goes as high as 160% (same video)
when i look at the system info i noticed that the processor speed (normally always at 1800 MHz) now goes down to as low as 225 MHz (AFAIK atom d525 has no idle states nor speedstep).
going back to #0822 and all is fine again

debug log #0823 - http://sprunge.us/RcXG

idling for about 5 min. at system info screen after a reboot.
Yeah - it's from the deinterlacing changes - will hopefully be fixed until end of week.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2016-08-13, 08:10)fritsch Wrote: @moontan77: Disable VDPAU, it is not used on your hardware anyways. After next out of memory crash, please also provide dmesg | pastebinit - then we can see what the kernel does. Using memory is not an issue per se, as it works differently on linux: http://www.linuxatemyram.com/


Here is kernel log after crash - http://sprunge.us/cjHE
(2016-08-26, 21:42)moontan77 Wrote:
(2016-08-13, 08:10)fritsch Wrote: @moontan77: Disable VDPAU, it is not used on your hardware anyways. After next out of memory crash, please also provide dmesg | pastebinit - then we can see what the kernel does. Using memory is not an issue per se, as it works differently on linux: http://www.linuxatemyram.com/


Here is kernel log after crash - http://sprunge.us/cjHE

Yeah OOM - too much memory used and nothing to swap.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2016-08-26, 13:49)kelsdogz Wrote:
(2016-08-26, 07:29)fritsch Wrote:
(2016-08-25, 23:52)kelsdogz Wrote: Sorry my ignorance! Be gentle.....
Trying to figure out what changed from 16.1 to cause my cpu usage to go up on 1080 playback on same system with 17.0
Thought maybe I had HW decoding that wasn't being used.
Will look again tonight. Please try a build from one week ago and use Bob deinterlacer please.


Log from 8/19 build with Bob deinterlacer.
http://sprunge.us/OWBD

The input is totally broken - no matter v16 or v17. Please verify your findings with a recording.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2016-08-26, 21:50)fritsch Wrote:
(2016-08-26, 21:42)moontan77 Wrote:
(2016-08-13, 08:10)fritsch Wrote: @moontan77: Disable VDPAU, it is not used on your hardware anyways. After next out of memory crash, please also provide dmesg | pastebinit - then we can see what the kernel does. Using memory is not an issue per se, as it works differently on linux: http://www.linuxatemyram.com/


Here is kernel log after crash - http://sprunge.us/cjHE

Yeah OOM - too much memory used and nothing to swap.


Any suggestions as to what i can do?
  •   
  • 1
  • 110
  • 111
  • 112(current)
  • 113
  • 114
  • 187
  •   
  Thread Closed
 
Thread Rating:
  • 11 Vote(s) - 3.91 Average



Logout Mark Read Team Forum Stats Members Help
LibreELEC Testbuilds for x86_64 (Kodi 17.0)3.9111