Join now - be part of our community!

5.1 DD and DTS passthrough on XD80 model

SOLVED
profile.country.GB.title
diodorus
Member

5.1 DD and DTS passthrough on XD80 model

Hello,

 

I have a XD80 Bravia (KD-43XD8099) connected to a 5.1 receiver via optical.

 

I have never been able to passthrough any 5.1 audio (DD or DTS) in any app (e.g. PLEX or NETFLIX) other than:

 

  • the built in sony video app (which however doesn't let me correct the bad lip-sync issues)
  • KODI v17, but only until a couple of weeks ago. Now I can only get **some** results using the "Enable Sync Playback to Display" option within KODI, but it's not a good enogh solution.

I read on KODI forums that DD (but not DTS) audio passthrough should actually work on KODI v17 (?)

 

Can you please share your experience/settings with passthrough, especially in KODI (and/or PLEX)?

 

I'm puzzled on why it suddenly stopped working for me.

 

Thanks

diodorus

1 ACCEPTED SOLUTION

Accepted Solutions
profile.country.AT.title
Kuschelmonschter
Hero

It is not easy to explain. When Android started out on the TV, it lacked respective APIs for audio passthrough. So SoC manufacturers started to implement some private APIs in their drivers which mostly only the stock apps (like the Video app) used.

 

Another approach to get AC3/DTS out of the TV was using the so-called "PCM Hack". It misuses the uncompressed audio (PCM) channel to output compressed bitstream audio. Now you can do all kinds of operations on uncrompressed audio like changing the volume or mixing it with some other audio. And if somebody along the PCM pipeline perfoms any operation on the compressed bitstream audio, you effectively end up with garbled AC3/DTS which can harm your audio hardware or even your ears. Kodi Jarvis (16) used this "PCM Hack" for example.

 

Google strongly discouraged developers from using the "PCM Hack" due to the above reasons. So with every Android version, new formats got added to a standard raw bitstream API:

 

Lollipop (intial Android TV version): AC3 (Dolby Digital), E-AC3 (Dolby Digital Plus)

Marshmallow: DTS, DTS-HD

Nougat: Dolby True HD

 

Bitstream audio won't get altered along this path. The problem however is that MediaTek (being the SoC manufacturer for Sony) is very slow in adopting the standardized APIs which are used by 3rd party apps (like Kodi Krypton).

 

Until recently, the only thing you could get out of the Sony via standardized API was AC3 with bit rates up to 448kbps, but not with 640kbps. This got fixed with latest ATV1 driver (2015 line-up, spring 2016 line-up). Your TV is ATV2. So you will probably have to wait for this fix (don't know whether V6.1004 fixes it). DTS unfortunately is still a no-go.

 

You will never be able to output HD/3D audio from today's TVs (via ARC or S/PDIF). So you will always be limited to AC3/DTS which is more than good enough for the average Joe. HD/3D audio via ARC won't be supported until HDMI 2.1 (eARC).

 

So that's the current situation. Sony needs to kick MediaTek in the ass. But with the 640kbps issue fixed, I am confident that we might also get DTS at some point in time. It is just another bitstream that needs to be carried over the cable, so it is actually not any different from AC3.

View solution in original post

16 REPLIES 16
profile.country.AT.title
Kuschelmonschter
Hero

It is not easy to explain. When Android started out on the TV, it lacked respective APIs for audio passthrough. So SoC manufacturers started to implement some private APIs in their drivers which mostly only the stock apps (like the Video app) used.

 

Another approach to get AC3/DTS out of the TV was using the so-called "PCM Hack". It misuses the uncompressed audio (PCM) channel to output compressed bitstream audio. Now you can do all kinds of operations on uncrompressed audio like changing the volume or mixing it with some other audio. And if somebody along the PCM pipeline perfoms any operation on the compressed bitstream audio, you effectively end up with garbled AC3/DTS which can harm your audio hardware or even your ears. Kodi Jarvis (16) used this "PCM Hack" for example.

 

Google strongly discouraged developers from using the "PCM Hack" due to the above reasons. So with every Android version, new formats got added to a standard raw bitstream API:

 

Lollipop (intial Android TV version): AC3 (Dolby Digital), E-AC3 (Dolby Digital Plus)

Marshmallow: DTS, DTS-HD

Nougat: Dolby True HD

 

Bitstream audio won't get altered along this path. The problem however is that MediaTek (being the SoC manufacturer for Sony) is very slow in adopting the standardized APIs which are used by 3rd party apps (like Kodi Krypton).

 

Until recently, the only thing you could get out of the Sony via standardized API was AC3 with bit rates up to 448kbps, but not with 640kbps. This got fixed with latest ATV1 driver (2015 line-up, spring 2016 line-up). Your TV is ATV2. So you will probably have to wait for this fix (don't know whether V6.1004 fixes it). DTS unfortunately is still a no-go.

 

You will never be able to output HD/3D audio from today's TVs (via ARC or S/PDIF). So you will always be limited to AC3/DTS which is more than good enough for the average Joe. HD/3D audio via ARC won't be supported until HDMI 2.1 (eARC).

 

So that's the current situation. Sony needs to kick MediaTek in the ass. But with the 640kbps issue fixed, I am confident that we might also get DTS at some point in time. It is just another bitstream that needs to be carried over the cable, so it is actually not any different from AC3.

profile.country.GB.title
diodorus
Member

Kuschelmonschter,

 

Thanks a lot for the detailed explanation!  I'd be happy with "just" AC3 and DTS, or even AC3 only, to be honest.

 

A couple of final questions, if I may:

 

  • What has actually triggered the change (and is that something that can be rolled back)? Was it an android update (from Lollipop to Marshmallow)? To be honest I thought I was always on Marshmallow: have I completely missed that? Or maybe the update from Kodi 17.0 to 17.1... (although I don't think so)?
  • Do you think this is likely to be fixed, and is there anything we could do to highlight this (again?) to Sony?

Thanks!

diodorus

oo.viper.oo
Member

Go through this thread: http://forum.kodi.tv/showthread.php?tid=298273

You'll also find there links to custom Kodi buids with PCM hack.

profile.country.AT.title
Kuschelmonschter
Hero


What has actually triggered the change (and is that something that can be rolled back)? Was it an android update (from Lollipop to Marshmallow)? To be honest I thought I was always on Marshmallow: have I completely missed that? Or maybe the update from Kodi 17.0 to 17.1... (although I don't think so)?

There has neither been a regression between 17.0 and 17.1, unless you used a custom build as pointed out by @oo.viper.oo, nor between versions of the operating system.

 


Do you think this is likely to be fixed, and is there anything we could do to highlight this (again?) to Sony?

Dunno. Bothering the support won't help. They wouldn't understand your concern and just discard your request. Bad press on social media is probably the only thing they will listen to...

 


oo.viper.oo schrieb:

Go through this thread: http://forum.kodi.tv/showthread.php?tid=298273

You'll also find there links to custom Kodi buids with PCM hack.


I discourage the use of the PCM hack. It works for a lot of people, but also fails for a lot of them. I can easily provoke the issue. People really had to go to the doctor because they were getting high-pitched noise only.

 

If you try it, turn down the volume initially!

 

Sony/MediaTek need to fix the standard Android raw bitstream API!

profile.country.GB.title
diodorus
Member

Yes i saw that post before, and I'm also not keen in the pcm hack.

 

What still puzzles me is how come everything was working fine until a couple of weeks ago. I've always been on official Kodi versions, and the fact it was working was the reason why i even purchased a Plex pass (to be used within Kodi), so I'm sure I'm not dreaming... I can provide the test files i always use to check 5.1 pass through if anyone is curious...

 

Thanks for your input anyway!

profile.country.GB.title
johayne98
Member

Why is this thread shown to be resolved ( a solution is shown ) ? 


I have been trying at every Firmware update to get the 5.1 DD and/or DTS decoding working from within the Kodi App . As you may know the Native App allows the passthough of DTS/ DD 5.1 , this has been the case for some time . Why is it that thrid Party Apps/ API cannot passthrough the Audio Stream correctly ? Has there been any official mention of this from Sony 

 

How will we know when  ( if ever ) this gets addressed ?  It is a waste of time testing each firmware update, hoping for a fix  , if there is no official release notes or plan around this Codec issue . 


Is this worth raising with SOny support ?

profile.country.HR.title
kinggo01
Contributor


@johayne98wrote:

Is this worth raising with SOny support ?


No. There's a quite long list of bugs on Android TV platform on this very SUPPORT forum for quite a long time and very litle has changed.

Basically, 95% of people don't care about smart part of the TV so the only things that SONY tries to improve is the DVB-T and those built in services like netflix, amazon and such. And in the process of doing so and raising android versions they break some core functionality that was there since 2015. And google also doesn't give a :poop: since there's mostly no add's here.

profile.country.GB.title
johayne98
Member

Hmm , it maybe worth me returning this TV then , I guess only the Real techies  will notice the DTS and DD who will notice passthough issues . As per my reply here Mediatek passthrough screwed , does this affect all Sony Bravia Android TV's ( assuming they all use the Mediateck Chipset) ? If so we may want to consider a phillps  for PAssthough on Third Party apps ?

 I am using game stream and find it frustrating having to have a PC next to the TV just to have the sound 

 

 

profile.country.HR.title
kinggo01
Contributor

well, the thing is that all sony and philips TVs use the same mediacrap SoCs with pretty much the same issues. Android TV goes the same way as google TV did before. The fact is that it was potentially the most advanced platform, at least when it comes to 3rd party apps, services and various smart integration but in the end it's just another embedded platform with tons of issues even for the embedded apps.