• 1
  • 2(current)
  • 3
  • 4
  • 5
  • 9
Philips 6501 - Passthrough problems
#16
As fritsch said, the TV is using API 22, which means that Android only supports AC3/EAC3 playback.
The Netflix app is an example of an Android app with EAC3 support.

DTS will not be supported as long as the TV is on API 22.
It should be supported if they release firmware with API 23 or 24, but they don't make any promises on that part yet afaik.

The TV supports DTS (core) in the builtin mediaplayer and on HDMI.
Best solution atm is to put Kodi on an external mediaplayer like an rpi or shield (if you really want surround sound).
When I find the time, I'll try to find out some transcode settings that provide guaranteed playback.

@fritsch: I suspect you want me to enable explicit audio debug logs.. anything else?
Reply
#17
normal Debug Log is fine.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#18
I hope this one helps you out: http://paste.ubuntu.com/23143095/

CTRL-F on 'finding audio codec'

Success at 800 and 929 (secondary audio track).
Ignore 1356, it's DTS.
Fail at 1479.
Success at 1844
Fail at 2275
Success at 2780
Fail at 3045 (eac3)
Reply
#19
Nice. Compare the media info between working and non working, please. Seems the higher bitrates it fails. Firmware bug, sadly.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#20
I always open 256ms in time for ac3, meaning: 10228 for 1536, e.g. 1536*8 or 1792*8 or 2048*8 and 3840 *8 if the underlying fw only thinks of max 10228 it has a problem.

Please identify those files so we can verify.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#21
thanks. I'll have a look tonight (or later this week Wink )

This is the clean output
1 - OK - Stream #0:1(dut): Audio: ac3, 48000 Hz, 5.1(side), fltp, 384 kb/s (default)
2 - OK - Stream #0:2(eng): Audio: ac3, 48000 Hz, 5.1(side), fltp, 448 kb/s
3 - IGNORE - Stream #0:1(eng): Audio: dts (DTS), 48000 Hz, 5.1(side), fltp, 1536 kb/s (default) (forced)
4 - NOK - Stream #0:2(dut): Audio: ac3, 48000 Hz, 5.1(side), fltp, 640 kb/s
5 - OK - Stream #0:1: Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz, 5.1(side), fltp, 384 kb/s
6 - NOK - Stream #0:1(eng): Audio: ac3, 48000 Hz, 5.1(side), fltp, 640 kb/s (default) (forced)
6.b - TODO - Stream #0:2(dut): Audio: ac3, 48000 Hz, 5.1(side), fltp, 640 kb/s ---------- (NOK expected)
6.c - TODO - Stream #0:3(dut): Audio: ac3, 48000 Hz, 5.1(side), fltp, 448 kb/s ----------- (OK expected)
7 - OK - Stream #0:1(eng): Audio: ac3, 48000 Hz, 5.1(side), fltp, 384 kb/s (default)
8 - NOK - Stream #0:1(eng): Audio: eac3, 48000 Hz, 5.1(side), fltp, 640 kb/s (default)
Reply
#22
Perfect, makes sense. Will prepare a test build for youlimiting the byte buffer (buffer time)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#23
@fritsch

believe it or not, but my Sony does AC3 passthrough via RAW for a 384kbps sample, but not for 640kbps.

Same MediaTek chipset as put into Philips. However in my log there was no error. Only no stream on S/PDIF.
Reply
#24
Yeah, let's see what happens with that build: http://jenkins.kodi.tv/job/Android-ARM/9136/ after it is finished. Should appear as: fritsch-androidpt-77​1a32d in the testbuild folder.

Edit: http://mirrors.kodi.tv/test-builds/andro...bi-v7a.apk (wait until mirror syncs)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#25
Still only passthrough for the 384kbps sample here.

I am attaching a log where I first started playback for the 640kbps sample which does not work and then for the 384kbps sample.


kodi.log
Reply
#26
Yeah - nothing I can do :-( firmware bug. It opens correctly but gets stuck when feeding data.

Too bad - everything is broken in that regard, when using the official API.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#27
Can you produce an adb log - this we can send to your vendor, so that they can fix it, please.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#28
OK, will try to create an adb log in the evening.

BTW, I assume I tried the correct version which is the one you linked to, because in the test-builds folder I see 2 androidpt builds, one from 19:56 (771a32d, which is the one from the link above) and one from 21:46 (188f6bc) which I did not try.
Reply
#29
The second one cares for a wraparound after 1h 33 minutes on AML devices.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#30
OK, so I did another test now with 640kbps and here are the logs:

kodi.log
adblog_ac3_640kbps_nok.txt
Reply
  • 1
  • 2(current)
  • 3
  • 4
  • 5
  • 9

Logout Mark Read Team Forum Stats Members Help
Philips 6501 - Passthrough problems1