not fully, I don’t think you’ll get any extra Atmos identification info in media tags in the library, but this info is available during playback in the PlayerProcessInfo dialog in CPM’s build (WIP atm)
Currently, there is an issue with the detection of EAC3 and Dolby Atmos (EAC3) in the Player Info.
I have reported the problem to cpm.
Yes, in your samples.
My library working good, no issues, but I havent similar files. 
I actually would want to bitstream DD+ Atmos but not regular DD+, in order to use Auro3D up mixing.
A reliable detection must work correctly with all types of files. 
My files are standard (the original versions), they just have multiple audio tracks.
I know, Its little bug, but not for me.
I have maybe 20 movies with eac3 atmos, all works fine with the detection.
The other 3-400 movie has just truhd atmos or dts-x …
I have one movie with an issue detecting Atmos (EAC3), but the rest work fine as long as we don’t try to trigger the “Atmos” bug.
Triggering the Atmos bug (in Player Info) on multi-track files that don’t contain Atmos at all is not normal (even if it has to be triggered manually).
Same as you for Atmos (TrueHD) and DTS:X, I haven’t seen any issues so far (I don’t have any files with TrueHD only, without Atmos).
Yes, its very small issue, but agree, you can force that.
When improvement coming then ok, when not, for me its perfect the current state.
I made these skin modification for myself, but pleasure share with others.
1 Like
Despite the open issue with EAC3 and Dolby Atmos (EAC3) could you please make a version you planned for cpm A5 for Arctic Fuse. When the problem is solved you can update.
1 Like
I will do it.
Thank you.
The problem is with non-Atmos streams with eac3 being shown as Atmos, so of course all your Atmos files are working ok 
It’s not 100% reliable in both cases (Atmos with EAC3 and EAC3 only).
The “Atmos” bug can be triggered if there are multiple EAC3 audio tracks (whether Atmos or not).
Edit: or single EAC3 audio tracks.
Arctic Fuse | Arctic Fuse 2 | Arctic Horizon 2
for CPM A5 Build and up.
Update:
• Improved detection of Dolby Atmos (E-AC3)
• Added Dolby Vision metadata indication
• Added temperature and CPU frequency indication with an alternative version of CPU usage
• Fixed memory usage bar
• Multiple minor correction
Extended version:
Download:
Arctic Fuse Extended version: 48.12 MB file on MEGA
Arctic Fuse 2 Extended version: 18.9 KB file on MEGA
Arctic Horizon 2 Extended version: 46.26 MB file on MEGA
I thank once again the community who are doing incredible work. 
8 Likes
Replacing the Includes_Labels.xml file in Arctic Fuse 2 loses this fix introduced in version v2.1.0 - Display add-on title in the main hub header #168:
Not that it’s a problem, but if you can correct it.
Corrected, I uploaded the latest version (v2.1.2).
2 Likes
Very good job. I felt in love with horizon 2 back again. But I still got one issue guys. When I play higher bitrate stream, the player cache fills pretty fast. But once I open media info I can see how slowly (lets say 1% per 2s) goes down. If I left it long enough I’m able to go to the 0% till the stream stops. So it seems that the info stops downloading.
Which one skin ?
Anyway I completelly switched off the kodi cache, with the new builded dinamic cache, that seems no need for me.
I’m currenly on horizon 2, but I switched to zephyr to test it and it’s the same. What do you mean by dynamic cache? I tought there’s just new caching options to set it via gui.
New dinamic cache separate to video and audio.
Its a part of CoreElec.
Not in the setting, builded.