Kodi Community Forum

Full Version: Passthrough Changes with v17
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Dtshd, TrueHD won't work with N Api. Google missed to include support for it, we are in contact with them.
For TrueHD it is decoder to 8 channels pcm, which the hw fails to open properly. Please enable debuglogging, so we can see.
(2016-10-04, 15:21)fritsch Wrote: [ -> ]For TrueHD it is decoder to 8 channels pcm, which the hw fails to open properly. Please enable debuglogging, so we can see.

Latest nightly Kodi 20161004(PT patch merged), debugging enabled
https://paste.ubuntu.com/23276438/
GetMinimum returns a huge buffer, for everything. How do you compute that in the fw?
(2016-10-04, 21:41)fritsch Wrote: [ -> ]GetMinimum returns a huge buffer, for everything. How do you compute that in the fw?

Can you perhaps point in https://android.googlesource.com/ where/how they do it?
I can then try to find the method they use in my firmware.
It is a bit technical, so maybe I will need help from the manufacturer next week as they might know better if I don't find it.
Just downloaded latest nightly. Been having issues with audio delay with pass through enabled on SPMC. No issues with v17.


Sent from my iPhone
I just noticed in the changelog for Krypton Beta 3, this line.

'Workaround amlogic passthrough on devices running Android 5'

Can anybody elaborate further on what the workaround is and what element(s) of passthrough issues is resolves?
User should not get noise, that's all about it.
(2016-10-07, 17:58)fritsch Wrote: [ -> ]User should not get noise, that's all about it.

Thank you.
And besides that, every AML box should get what it supports, including AC3, EAC3, DTS, DTS-HD, TrueHD (but this is a side effect, the future android devs will hate me).

All AML users with Android 6 and later get what the official API supports.
(2016-10-04, 15:18)fritsch Wrote: [ -> ]Dtshd, TrueHD won't work with N Api. Google missed to include support for it, we are in contact with them.

Please keep us updated if something is heard back from Google for IEC61937 or if they plan to make a new API for eg. Android 'O' that can be backported to Android firmwares and also be used by Kodi.
(2016-10-07, 19:52)fritsch Wrote: [ -> ]And besides that, every AML box should get what it supports, including AC3, EAC3, DTS, DTS-HD, TrueHD (but this is a side effect, the future android devs will hate me).

All AML users with Android 6 and later get what the official API supports.

Any issue found? Or have you achieved to passthrough all the audio format on AML android M system?
Implementation is ready and working on capable Android devices. Everything else not working is a Firmware bug :-)
What does this mean for Android TV devices? Will things like the mi box ever get proper passthrough or is it up to the manufacturer of the device?
Up to the manufacturer. We speak THE documented Android api.