• 1
  • 84
  • 85
  • 86(current)
  • 87
  • 88
  • 134
WeTek Core (24p HD Netflix / HD Audio / Lollipop / OpenELEC / 4K / HEVC)
(2016-02-08, 09:54)Koying Wrote: Yeah, for clarification, I tested on S905 (NEO U1).
I haven tried on the core.

I used the Core - so - all fine :-) - Core in combination with a Marantz NR1402. Btw. as I have some intermittent stutter I tried to increase the buffer values for passthrough: http://mirrors.kodi.tv/test-builds/andro...bi-v7a.apk
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Hi fritsch,

Working with WeTek Core and build you posted.

DTS-HD OK

TrueHD OK

Just what I noticed with this build is that sometimes on AVR is lost signal and then DTS-HD MSTR/TrueHD icon appear again and audio comes.

Here is kodi.log
Reply
If you can, please post a Debug Log. No intermittant stutter as I saw on my Core, which basically made it quite unusable? ... I was recalculating the buffers, therefore I'd be happy for another test with: http://jenkins.kodi.tv/job/Android-ARM/7114/ when it is finished.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Log posted to my previous post, it is 18mb :-) . Sure, I will wait for new build and then re-test.
Reply
On Core for being extra sure that is not the framerate automation modifying audio clocks disable it with "echo 0 > /sys/class/tv/policy_fr_auto"
Reply
(2016-02-08, 12:27)ChristianTroy Wrote: On Core for being extra sure that is not the framerate automation modifying audio clocks disable it with "echo 0 > /sys/class/tv/policy_fr_auto"

I am not yet convinced this is the issue - still calculating with the buffers.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
What I notice now is that after 1-2 minutes, it totally stabilised, and no more audio drops with fritsch build.
Reply
(2016-02-08, 12:29)droidelec Wrote: What I notice now is that after 1-2 minutes, it totally stabilised, and no more audio drops with fritsch build.

I see that from your log - whenever you open e.g. the codec screen or something it will directly start to drop out again - the sink runs dry. Let's wait for the currently building testbuild -quite curious.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
fritsch not good with latest build, I get only PCM logo shown on AVR display and no audio at all. Log here
Reply
Got a link for that build that in case I try here as well?
Reply
(2016-02-08, 14:10)ChristianTroy Wrote: Got a link for that build that in case I try here as well?

The log file makes the problem clear. I did not account the "AMLogic tunneling" into account. Please try with next build again: http://jenkins.kodi.tv/job/Android-ARM/7117/ http://mirrors.kodi.tv/test-builds/andro...mirrorlist
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Tested on 905

https://mega.nz/#!55Ix1SIb!ukD4MrKRoDgHc...ql3mKNUBXk

AC3: OK
DTS: OK
E-AC3: like the build from last night, just some farts/pops and apparently no audio output recognized by the AVR
TrueHD: OK
DTS-HD: OK
Reply
(2016-02-08, 16:02)ChristianTroy Wrote: Tested on 905

https://mega.nz/#!55Ix1SIb!ukD4MrKRoDgHc...ql3mKNUBXk

AC3: OK
DTS: OK
E-AC3: like the build from last night, just some farts/pops and apparently no audio output recognized by the AVR
TrueHD: OK
DTS-HD: OK

Do you have any version where EAC3 works? Did it ever work?

Edit: BTW. I always like debuglogs cause in there I exactly see how the sink behaves.

Debug Log (TRueHD)
Debug Log (EAC3)
Debug Log (DTSHD)

Can't work without those .-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
The debug log is enabled (in fact I have the OSD visible), do you want that I enable the specific codec logging and flag audio there?

Using Jarvis rc3 modified with Koying patch DD+ works fine
Reply
(2016-02-08, 16:07)ChristianTroy Wrote: The debug log is enabled (in fact I have the OSD visible), do you want that I enable the specific codec logging and flag audio there?

Using Jarvis rc3 modified with Koying patch DD+ works fine

Nope Debug Log is enough - don't turn on ffmpeg logging as this will spam the log ...
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
  • 1
  • 84
  • 85
  • 86(current)
  • 87
  • 88
  • 134

Logout Mark Read Team Forum Stats Members Help
WeTek Core (24p HD Netflix / HD Audio / Lollipop / OpenELEC / 4K / HEVC)4