(2017-01-08, 15:10)fritsch Wrote: That's a "hidden hack" or a combination of features. Sync Playback to Display will use the display clock to time the video image to screen. While PT audio runs at wallclock (most of the time not the Display Clock), Sync Playback to Display would plain disable PT and output LPCM.

Though - as we did not want that SPDIF users with 2.0 pcm channels only, would loose surround sound, we go the Transcode path in that combination. So for your Sony TV that only supports 384 Kbit/s with the official API - you cannot output normal 640 Kbit/s AC3, right? Therefore this setting combination will decode it and reencode it to 384 Kbit/s AC3. Clever isn't it? (Without the Sync playback, no need to reencode and 640 Kbit/s would be output).

(2016-12-13, 07:16)fritsch Wrote: You are free to do so ... if you look at the pr it's a setting already.

via: https://github.com/xbmc/xbmc/pull/11138/commits/9865028663177fbc161ffaddb7b656c8e74f4679

Code:

<advancedsettings>
  <audio>
     <forcepcmpassthrough>true</forcepcmpassthrough>
  </audio>
</advancedsettings>

(2017-01-05, 12:41)fritsch Wrote: Just set pcm channels to 2.0 and enable Dolby / AC3 Transcoding and all those DTS / DTS-HD will come out as AC3 ...

(2017-01-11, 20:09)ssarava9 Wrote:

(2017-01-11, 19:36)Martijn Wrote:

(2017-01-11, 19:34)Geniy Wrote: DTS passthrough in Kodi 17 RC don't work. In 16.1 and another alternative playyer all ok. Checkboxes on "Allow passthrough" and "DTS Capable reciever" active. No sound than I select DTS track at all.

Logs http://paste.ubuntu.com/23782631/
See 20:11:45

Throw it away a wait till you get new firmware update on it. Sorry but not our problem

Have the latest firmware released in November 2016, can anyone confirm getting DTS in android using Kodi 17?
It is a bug in Kodi 17

Quote:Welcome to Android MediaCodec standards only

One of the last custom implementation we had was Amlogic related code which was the device were it all started with Kodi on Android. We had to resolve to this custom implementation back then to access certain hardware parts which Android officially couldn’t yet. Due to this legacy and how we had things implemented we couldn’t switch this off just yet in past releases.

Over the past months with the help of MINIX we have been working closely with the Amlogic to get everything in order and we can say Android Marshmallow and onward will have the best experience possible for devices containing these chipsets.

Amlogic even went as far as adding the IEC61937 audio passthrough back into Android Marshmallow which normally is only available since Android Nougat. We would certainly like to thank Amlogic and MINIX for going to this extend of cooperation making the experience and support of Kodi on Android a bit better.
Now Amlogic has done their part on proving a good bases it’s up to manufacturers and vendors to supply updates for their devices over coming months....

(2017-01-14, 05:26)wrxtasy Wrote:

(2017-01-11, 20:09)ssarava9 Wrote:

(2017-01-11, 19:36)Martijn Wrote: Throw it away a wait till you get new firmware update on it. Sorry but not our problem

Have the latest firmware released in November 2016, can anyone confirm getting DTS in android using Kodi 17?
It is a bug in Kodi 17

As Martjn, Fritsch and others have been saying its NOT a bug in Kodi 17 but the shitty Android Firmware you have on your box.

You better hope like hell that wherever/whomever you got your box from updates its Android Firmware to fix your DTS Audio issues otherwise throw the device away and get a Android Box with Firmware support OR if its an AML S905 use LibreELEC OR as a last resort look for 3rd party Android Firmware on the Freaktab Website.
Chalk it down to an educational experience. We all have one or two dud, unsupported devices in our Skeleton closet

This needs to be read as well if not done already....

https://kodi.tv/kodi-v17-krypton-release-candidate-1/

Quote:Welcome to Android MediaCodec standards only

One of the last custom implementation we had was Amlogic related code which was the device were it all started with Kodi on Android. We had to resolve to this custom implementation back then to access certain hardware parts which Android officially couldn’t yet. Due to this legacy and how we had things implemented we couldn’t switch this off just yet in past releases.

Over the past months with the help of MINIX we have been working closely with the Amlogic to get everything in order and we can say Android Marshmallow and onward will have the best experience possible for devices containing these chipsets.

Amlogic even went as far as adding the IEC61937 audio passthrough back into Android Marshmallow which normally is only available since Android Nougat. We would certainly like to thank Amlogic and MINIX for going to this extend of cooperation making the experience and support of Kodi on Android a bit better.
Now Amlogic has done their part on proving a good bases it’s up to manufacturers and vendors to supply updates for their devices over coming months....

And as an Example of a vendor providing good support. The AMLogic Marshmallow S905x Xiaomi Mi Box got a Firmware update a couple of days ago that contains this IEC Audio support. It can now passthrough 5.1/7.1 Dolby Atmos/TrueHD, DTS:X/HD-Master Audio with Kodi Krypton RC3. This is exactly what we mean by supported Android Kodi boxes.

In fact I see very few reasons why a person would purchase a cheap unsupported Android device if they want regular Firmware updates and Kodi support to be improved upon and Kodi A/V features to actually work.

(2017-01-14, 11:43)wrxtasy Wrote: @Numus,
What you are missing in all this is that to lesson the workload of Kodi Android developer coding support, everyone vendor that wants Kodi Krypton to run relatively smoothly on their device has to adhere to the exact same Android standards. And use the same Android Application Programming Interfaces.

Krypton v17 is the Line in the Sand moment when the Kodi devs have gone enough is enough. There will be no more custom hacks. Its no longer possible for everyone to do their own thing if they want proper A/V support into the future. The freely given Kodi developer resources are just not there.
Plus there are too many Android devices to provide custom programming support. Its simply impossible.

Simply put the burdon of adhering to well known Google Android standards rest solely with the Vendors and Chipset manufacturers from Krypton onwards.

Amazon hardware is very likely sold at cost price mainly to generate revenue from paid video streaming services. That it happened to run Kodi Jarvis using custom hacks has been fine up to this point. Amazon now have to get with the program and start adhering to publish standards. Sony as well, and all others that want Kodi support. Otherwise there will be continual pain for end Kodi users of such hardware going forward.

(2017-01-14, 11:55)Jeffers24 Wrote: +1

What is the standard that a buyer should look for, when buying an Android box??

(2017-01-14, 12:40)wrxtasy Wrote:

(2017-01-14, 11:55)Jeffers24 Wrote: +1

What is the standard that a buyer should look for, when buying an Android box??

Personal opinion...

Well Kodi sponsors obviously have a particular interest in the Kodi project itself so will provide better Firmware support & Kodi developer dialogue than others as they already have a vested interest in the project.

Then you have manufacturer developer resources.
Multinational Tech companies like nVIDIA & Xiaomi will naturally have more resources to call upon to develop and provide regular updates to known standards. nVIDIA is in a very unique position of being the hardware manufacturer and Android Firmware support / seller of the Shield. This naturally has extra benefits, especially when interacting with Google and Android TV.

AMLogic themselves look to be taking a serious interest in Android and doing their best lately to adhere to standards, which is a nice turn of events. LibreELEC developers are seeing some nice benefits from AMLogic now as well.

Sony and Amazon, well it's hard to see what they want to do. Sony seems slow providing any Android OS support to the required standards, and Amazon have made no mention of Android Nougat which will give IEC Audio support.

You will still then have the passionate guys like MINIX, WeTek, Himedia and Zidoo releasing Niche Android products to compete against the Multinationals. Again trying to release stable Firmware, with regular updates that meets the Android standards. Experience over a period of time with the same hardware chipset family is important here for getting decent Android Firmware.

In the end its all about priorities and resources made available by the manufacturer and willingness to adhere to Google standards.
Oh and avoid the cheap Ship and Forget Android sellers, hopeless Firmware support lies down that pathway.

---

And after all that I probably still did not answer the question.
As already posted above, for the Audio standard used for Kodi Krypton - that being IEC61937 audio passthrough, currently only nVIDIA when they release Android Nougat on the Shield and AMLogic, with backported Nougat into Marshmallow Audio code will meet it.

At this present point in time the Xiaomi Mi Box is the only device I know of that meets the IEC61937 audio passthrough standard.