2015-10-16, 21:25
Any way to detect ATMOS extensions to a TrueHD track?
2015-10-16, 21:40
ATMOS uses the standard TrueHD extensions therefore we do passthrough as an accident because we have no idea about the content of the extensions so just blindly pass them through.
2015-10-16, 23:56
EDIT: just found the Atmos thread in the Windows forum... so never mind the below.
Oh, I know it works - I've already used Kodi to listen to a number of Atmos tracks without issue. Just didn't know if ffmpeg was aware enough to actually detect an Atmos stream and pass that information to you, so we could get "TrueHD ATMOS" logos instead of "TrueHD 7.1".
Oh, I know it works - I've already used Kodi to listen to a number of Atmos tracks without issue. Just didn't know if ffmpeg was aware enough to actually detect an Atmos stream and pass that information to you, so we could get "TrueHD ATMOS" logos instead of "TrueHD 7.1".
2015-10-19, 05:26
(2015-10-14, 09:32)jjd-uk Wrote: Note that it's only DTS-HD that we previously had problems with, so all other codecs such as TrueHD and AAC should report 7.1 so if there is an issue with anything other than DTS-HD then this indeed maybe a bug.
Yes, Kodi 15.2 successfully identified TrueHD 7.1 channels ... so the issue with is with DTS-HD MA as you pointed out (pre-Kodi 16.x). The video was actually a 'TrueHD 7.1 ATMOS' labelled title which it scanned correctly into the library.
2015-10-19, 10:02
Yes another issue we have is with ATMOS.
ATMOS is an TrueHD steam with a set of extensions, these extensions were defined long ago in the TrueHD standard but have been unused. The advange to Dolby of this is that any player that previously supported TrueHD could pass through ATMOS without any changes so it would only need users to upgrade their AVR to decode, anything that couldn't decode ATMOS would just use the TrueHD portion.
Hence we were able to pass ATMOS containing streams, however because we can't decode ATMOS and thus know it's ATMOS in the extension, all we can do is identify it as a TrueHD stream.
ATMOS is an TrueHD steam with a set of extensions, these extensions were defined long ago in the TrueHD standard but have been unused. The advange to Dolby of this is that any player that previously supported TrueHD could pass through ATMOS without any changes so it would only need users to upgrade their AVR to decode, anything that couldn't decode ATMOS would just use the TrueHD portion.
Hence we were able to pass ATMOS containing streams, however because we can't decode ATMOS and thus know it's ATMOS in the extension, all we can do is identify it as a TrueHD stream.
2017-05-05, 08:13
Sorry to bring up this old thread again, but the issue still exists in Krypton 17.1
DTS HD MA 7.1 is wrongly scanned as 5.1 into the library. If you pop up the info screen while playing that file it correctly says 7.1
DTS HD MA 7.1 is wrongly scanned as 5.1 into the library. If you pop up the info screen while playing that file it correctly says 7.1
