•   
  • 1
  • 47
  • 48
  • 49(current)
  • 50
  • 51
  • 187
  •   
  Thread Closed
v17 LibreELEC Testbuilds for x86_64 (Kodi 17.0)
You know - with a Debug Log things would be much easier, cause there I could see which samplerate / speaker configuration would have been enumerated. And if you would be really cool, you would also pastebin /proc/asound/HDMI/* for me :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
And I did post logs: 2350275 (post) but not that last one. But hey, not an issue anymore Smile It's a firmware issue on the PS175 chip.

Thanks for the help anyways Smile
I want them with the new firmware ... and the /proc/asound thingy, cause with that I can tell you if it's a handshake issue. Waiting with the sheep is not my philosopy :-). When the BDW nucs came out - IR was non functional - so I disassembled the DSDT and showed them their bugs ... 5 days later it was fixed :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Ah. New logs. Gimme a sec.

EDIT:
Kodi.log http://sprunge.us/ZPci

pastebinit /proc/asound/*
http://sprunge.us/OcVe

pastebinit /proc/asound/PCH/*
http://sprunge.us/OMOG

That good enough logging?
Read: kodi.log please and this /proc/asound thingy ... not the other Kladderadatsch (as we say in germany for useless log parts).
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2016-06-08, 17:16)fritsch Wrote: IR was non functional - so I disassembled the DSDT and showed them their bugs ... 5 days later it was fixed :-)

With all the issues there still are I would hardly call it functional.
Yeah - use something else. I suggest a FireTV stick - good bye.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
@fritsch did you see anything in the logs? Or did I post the wrong logs again Tongue
I don't get mails if you edit posts.

Quote:sad2_coding_type [0x7] DTS
sad2_channels 6
sad2_rates [0x6c0] 44100 48000 88200 96000
sad2_max_bitrate 1536000
sad3_coding_type [0xa] E-AC-3/DD+ (Dolby Digital Plus)
sad3_channels 8
sad3_rates [0xc0] 44100 48000
sad4_coding_type [0xb] DTS-HD
sad4_channels 8
sad4_rates [0x1ec0] 44100 48000 88200 96000 176400 192000
sad5_coding_type [0xc] MLP (Dolby TrueHD)
sad5_channels 8
sad5_rates [0x1ec0] 44100 48000 88200 96000 176400 192000
monitor_present 0
eld_valid 0
monitor_present 0
eld_valid 0
PCH

All fine. Nothing we can do.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
That's fine. Thanks! Smile I will keep pushing Intel.
(2016-06-08, 13:01)Milhouse Wrote:
(2016-06-08, 12:54)john.cord Wrote: Is there is reason caused by Kodi that after i boot a client all drives of the NAS gets busy? Is kodi by default set to scan some sort of file metadate or something?
Try with a "clean" .kodi ("mv .kodi .kodi.bak" and restart Kodi). This well ensure you have no additional add-ons, and using default settings. If problem guess away it's either a third-party add-on (watchdog?) or a setting (scan/clean library on startup?)

Ok, thanks. I will check this. Another Question. If the NAS is busy and Kodi doesnt get enough data for seamless video playback. Is there a possible case that the videoplayer drops frames instead of pausing playback and caching data for seamless playback?
VideoPlayer has an internal cache of some seconds - if that is running dry - you have a sever network problem.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Quote:... 5 days later it was fixed

5 days, my a** Smile
(2016-06-08, 22:27)fritsch Wrote: VideoPlayer has an internal cache of some seconds - if that is running dry - you have a sever network problem.

And this sort of network problem can cause dropped frames? How does a spined down HDD affect this in the caste that i pause playback, hdd spins down and after some time playpack is continued and hdd needs some seconds to spin up.
New LibreELEC.tv Krypton build #0608: Generic
(Supercedes previous build)

Code:
# uname -a
Linux LibreELEC 4.6.2 #1 SMP Wed Jun 8 22:36:58 BST 2016 x86_64 GNU/Linux

# lsb_release
LibreELEC (Milhouse) - Version: devel-20160608222301-#0608-g2f965b3 [Build #0608]

Based on tip of LibreELEC.tv master (2f965b37, changelog) and tip of XBMC master (d432df0b, changelog) with the following modifications: Build Highlights:
  1. New 4.6.2 kernel
  2. Drop Intel modesetting
Build Details:
  1. LibreELEC.tv:
    • docker: update to 1.11.2 (PR:429, 1 commit, 4 files changed)
  2. XBMC:
    • VideoPlayer: switch back to Kodi method of counting CPUs (PR:9931, 3 commits, 1 file changed)
    • VideoPlayer: keep value of m_vSyncAdjust on Discontinuity (PR:9932, 1 commit, 2 files changed)
  3. Additional commits/pull requests/changes not yet merged upstream:
    • Added: [env] PR:431: Revert "Merge pull request #136 from lrusak/modesetting"
    • Added: [env] PR:434: linux: Update to 4.6.2
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.
  •   
  • 1
  • 47
  • 48
  • 49(current)
  • 50
  • 51
  • 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