[movie78]

No receiver will display Atmos, it will display TrueHD of course when using xbmc.

Unless i am using a Bluray Device?

So Xbmc/OpenElec only output the TrueHD track in Dolby Atmos even if i am using an ATMOS receiver?

[robo989]

No receiver will display Atmos, it will display TrueHD of course when using xbmc.

Unless i am using a Bluray Device?

So Xbmc/OpenElec only output the TrueHD track in Dolby Atmos even if i am using an ATMOS receiver?

Correct.

[movie78]

Damn..

I guess I am not buying Dolby Atmos receiver until xbmc fully support it.

[grobbie]

Hi,

I have asked this question before but didn't get an answer. Blu-ray players can passthrough Atmos without firmware updates. This means blu-ray players just pass the Atmos extension data as is, without any parsing at all (how can they). Why can't Kodi do the same?

I read a post in this thread stating Atmos data needs to be parsed by Kodi but I can't understand why (except maybe for making a software Atmos processor). The only thing I can think of is that ffmpeg does not expose the Atmos extension data to Kodi?

Would appreciate it if anyone can clear this up Have just bought an Atmos enabled system and hate to have to dust off the old br-player, endure the annoying br menu's and crappy br player interface just to enjoy Atmos sound. Let alone the physical disks swapping

Thanks in advance,
Grobbie

[Batiatus]

Hi,

I have asked this question before but didn't get an answer. Blu-ray players can passthrough Atmos without firmware updates. This means blu-ray players just pass the Atmos extension data as is, without any parsing at all (how can they). Why can't Kodi do the same?

I read a post in this thread stating Atmos data needs to be parsed by Kodi but I can't understand why (except maybe for making a software Atmos processor). The only thing I can think of is that ffmpeg does not expose the Atmos extension data to Kodi?

Would appreciate it if anyone can clear this up Have just bought an Atmos enabled system and hate to have to dust off the old br-player, endure the annoying br menu's and crappy br player interface just to enjoy Atmos sound. Let alone the physical disks swapping

Thanks in advance,
Grobbie

I wouldn't hold your breth for an answer. Seems the devs aren't even interested in releasing a patch for Gotham so enable just the TrueHD track, instead stating people should download the incomplete and still buggy Kodi if they want HD audio for Transformers, Expendable of Turtles.

Atmos support likely won't come for a long long time. Same with 3D.

[nickr]

Gotham gets no more patches sorry. Kodi is near release. If that weren't so, I'd say yes lets try to patch Gotham. But we are at RC2 with kodi, and thats where the patches have gone.

[Initial G]

This may be interesting to someone. Running Gotham 13.2 , after selecting the wasapi driver bitstreaming of HD audio works, but also: using the Atmos demo bluray rip I get Dolby digital + with Atmos enabled (input atmos and DD+ logo on receiver). The trueHD track doesnt work (no sound). With latest MPC-HC TrueHD + Atmos bitstreaming works flawlessly.

Background: I have an Onkyo TX-NR636 atmos receiver with extra atmos speakers (bookshelfs aimed at ceiling) and was looking to set up the whole bitstreaming HD audio and atmos. I had a zotac ND22 ION(1) htpc box, this doesnt do HD audio bitstreaming. I swapped it for my second htpc, a somewhat older shuttle system that i upgraded with an Nvidia GT730 passive.

[jjd-uk]

Hi,

I have asked this question before but didn't get an answer. Blu-ray players can passthrough Atmos without firmware updates. This means blu-ray players just pass the Atmos extension data as is, without any parsing at all (how can they). Why can't Kodi do the same?

I read a post in this thread stating Atmos data needs to be parsed by Kodi but I can't understand why (except maybe for making a software Atmos processor). The only thing I can think of is that ffmpeg does not expose the Atmos extension data to Kodi?

Would appreciate it if anyone can clear this up Have just bought an Atmos enabled system and hate to have to dust off the old br-player, endure the annoying br menu's and crappy br player interface just to enjoy Atmos sound. Let alone the physical disks swapping

Thanks in advance,
Grobbie

I'm no expert but it goes something like this.

Dolby TrueHD, as specified by Dolby, right from the beginning contained the concept of a main part and an extension part, however although this extension part was defined and documented it has never been used until it repurposed for Dolby Atmos.

Blu-players whether hardware or software will have paid licenses for the technology they use to the BDA and perhaps Dolby & DTS too, so they have access to technical documentation that would otherwise cost several thousand £/$. This would have allowed them to design their products to support the TrueHD extension format even though there was no real world use until Dolby Atmos came along.

For Open Source projects they generally won't have the funds even if they had the will to pay for license fees and documents, so they generally have to rely on someone understanding and reverse engineer something from real world material. Since there's been no real world material using these TrueHD extensions to work with until now there's been no means to code in support for them, hence the 1st step was to just understand how to tell the extension is there, so it can then be discarded in order that the main TrueHD part can be passed through or decoded. Obviously the next step to try and reverse engineer the extension format using the real world material now available, however I'm not sure if anyone has taken up that challenge yet.

[fritsch]

Would appreciate it if anyone can clear this up Smile Have just bought an Atmos enabled system and hate to have to dust off the old br-player, endure the annoying br menu's and crappy br player interface just to enjoy Atmos sound. Let alone the physical disks swapping Wink

There are plenty ffmpeg students out there, that would take a sponsor ship to develop what is still needed.

Edit: As you asked for the details, have a look at: 91992d97880d0378503a413a35756bdca42f9281 there you see what we are currently doing to "skip" this extension.

[grobbie]

Hi,

I have asked this question before but didn't get an answer. Blu-ray players can passthrough Atmos without firmware updates. This means blu-ray players just pass the Atmos extension data as is, without any parsing at all (how can they). Why can't Kodi do the same?

I read a post in this thread stating Atmos data needs to be parsed by Kodi but I can't understand why (except maybe for making a software Atmos processor). The only thing I can think of is that ffmpeg does not expose the Atmos extension data to Kodi?

Would appreciate it if anyone can clear this up Have just bought an Atmos enabled system and hate to have to dust off the old br-player, endure the annoying br menu's and crappy br player interface just to enjoy Atmos sound. Let alone the physical disks swapping

Thanks in advance,
Grobbie

I'm no expert but it goes something like this.

Dolby TrueHD, as specified by Dolby, right from the beginning contained the concept of a main part and an extension part, however although this extension part was defined and documented it has never been used until it repurposed for Dolby Atmos.

Blu-players whether hardware or software will have paid licenses for the technology they use to the BDA and perhaps Dolby & DTS too, so they have access to technical documentation that would otherwise cost several thousand £/$. This would have allowed them to design their products to support the TrueHD extension format even though there was no real world use until Dolby Atmos came along.

For Open Source projects they generally won't have the funds even if they had the will to pay for license fees and documents, so they generally have to rely on someone understanding and reverse engineer something from real world material. Since there's been no real world material using these TrueHD extensions to work with until now there's been no means to code in support for them, hence the 1st step was to just understand how to tell the extension is there, so it can then be discarded in order that the main TrueHD part can be passed through or decoded. Obviously the next step to try and reverse engineer the extension format using the real world material now available, however I'm not sure if anyone has taken up that challenge yet.

That sounds like a logical explanation, thanks! Hope it gets implemented soon but I guess not many ppl have Atmos systems atm let alone developers capable to reverse enginering the thd extension data so it might take a while

[moravec]

Does anybody have a Gotham Version compiled for Windows, which can play DolbyTHD with Atmos?

[TRaSH]

what i've heard it won't happen,
2 options.

1. switch to Helix
2, switch to openelec or use openelec from a USB stick for those Atmos Movies

[A-Swiss]

I was spending hours with investigation of that silly Format - until i remembered the Dolby Atmos included in the True HD Stream. (The Expendables 3 - just to mention)
My conclusion, after reading through this post - wait for Final Helix - and keep this file on stock until migration will happen.

I'm planning to replace my Onkyo TX-NR818 with a newer model, which will have the Atmos Feature included.
Even when I'm not planning to use it in near future, to receive at least the CORE from TrueHD from Kodi will be sufficient.

too bad, that there's no patch for gotham...

[dwalme]

No receiver will display Atmos, it will display TrueHD of course when using xbmc.

With Kodi v14 my AVR (Yamaha RX-A3040) will display Atmos/TrueHD when bitstreaming TrueHD/Atmos tracks (Transformers 4).

However when I bitstream only TrueHD tracks my AVR only displays TrueHD.

As I understand it when bitstreaming Atmos the atmos extension is dropped and only the TrueHD core is sent to the AVR. However something else is coming along with it because my AVR is able to detect that the stream was an Atmos stream.

Looks like the LAV filter devs were able to implement atmos bitstreaming in their directshow filter. Perhaps an opportunity to share.

[jjd-uk]

Are sure LAV filters can bitstream the full ATMOS audio track? As it's based on ffmpeg the same as us & I believe Nev Cairiel (main LAV filter dev) is a contributor to ffmpeg so any work done for LAV filters should make it's way into ffmpeg and thus into Kodi.