[chester24]

Hi @manfeed 

I really like your skin, a small problem I have now is I cannot get Logos for all my TrueHD Atmos movies/shows and also not for the DDPlus Atmos ones.
What I get shown is always TrueHD for the TrueHD Atmos versions and nothing for the DDPLus Atmos versions.
Do you have any plans to support this?
My folders and files are named truehd.atmos and ddplus.atmos accordingly.

Thanks!

Hi @chester24,

This is a known issue, nothing wrong with your settings. Aeon Tajo does not pick Atmos flags from the file name, this must be scrapped by KODI when adding the movie. It appears that it is KODI/Scraper that adds TrueHD and ignores Atmos. For dolby digital plus, my scraper can pick "EAC3" from file name, I have never tested with "DDPLus", there is a chance it will ignore that.

Solution.
1st, test by replacing DDPLus with EAC3 in the file name, see if the scrapers can pick it up, this way, the skin should show DD plus flag. 
2nd, are you using NFO files? The only way I know of adding Atmos flag is editing NFO file. This method was recommended to me by manfeed.
Open the movie nfo file, under stream details edit the audio streams. Currently it should show truehd only, just add atmos, like so. I prefer Atmos comes first. Number of channels and language is same as truehd since its the same audio stream.

xml:


            <audio>

                <codec>atmos</codec>

                <language>eng</language>

                <channels>8</channels>

            </audio>

            <audio>

                <codec>truehd</codec>

                <language>eng</language>

                <channels>8</channels>

            </audio>

Now when your rescrap (Refresh) this movie, the scrapper should pick Atmos from NFO and not the file name and the skin will show the flag. If you have many Atmos movies, this is going to be quite some work.

Hi @TimeZone 

thanks for your reply. While I appreciate it I won't mess up my correct .NFOs for KODIs "wrong" behavior. I handle everything from .NFOs. Also all pictures and everything else is done before Kodi even gets its hands on it. I do not use any online scraper in Kodi, just the local one.
Here are my thoughts on that :
a) I think you misunderstood the DDPlus thing. DDPlus is correctly mentioned/scraped in Kodi. This is with eac3 in the info files. But this does not apply to DDPlus with Dolby Atmos. If this what you proposed works then it is wrongly implemented in Kodi in every possible way. As Atmos is no codec. That is what I mean I won't mess up my correct .NFOs with a "codec" that is simply not existing. DDPlus with Dolby Atmos is EAC3 codec, exactly like DDPlus without Atmos. Difference lies in the format and also it is mentioned in the "Commercial name", but the codec is no different.
b) The very same is true for TrueHD, Atmos is no Codec, it is an extension on TrueHD. TrueHD Atmos, like DDPLus Atmos, codec is simply TRUEHD.

So if it is implemented in Kodi that Atmos is scraped as a codec then a bug report should be opened on that. Because with Atmos as a "codec" no one would know if it is actually TrueHD with Atmos or DDPlus with Atmos.
Then, if at all, Kodi should be able to scrape eac3_atmos (eac3.atmos) or truehd_atmos (truehd.atmos) because this would be the only thing that comes close to the reality and how Atmos is implemented in the audio streams. You cannot scrape a codec that is not existing, nor put it in a .NFO file (from my point of view).

While I have way over 150 files with Atmos I would write a python script for it, but it would be simply wrong.

So, can you tell me where this should be posted so Kodi development takes note of it?

Many thanks