[C.Taylor]

What would be the point of adding Atmos support by adding an extension to the filename? This is a hack not a solution to the problem. When support for flagging at the source is possible, then such a change would make sense.

Based on the reviews I've read, object-oriented surround sound is here to stay. Is not going the way of 3D. I've heard from several sources, and it does work and it does work well -- even without placing speakers in the ceiling.

So the real problem is this debate has raged for several pages but has failed to stay on topic. If not available from the source stream, then it shouldn't be added. A filename hack is not very useful to the majority of users.

You want to know why people would like to identify their Atmos files as such but then state it's here to stay and useful? Why do people care to identify their sources as Blu-ray or DVD? Or signify things as 3D? How are those hack flags helpful to the majority of users? Why have any media flags at all

A filename "hack" has been used multiple times by the devs to resolve issues they can't through "proper" means. How long will the majority of users wait until Blu-ray can be pulled from the stream? Or 3D information? Certainly all of those things should eventually be possible in ffmpeg, no? I mean it's already possible to note MVC in a MKV yet Kodi won't show 3D flags for those files as a source by default.

What if it NEVER becomes possible to pull Atmos, Auro3D or dtsX through ffmpeg?

The only problem with the debate is there is a new (and more coming) audio format that could be flagged as such in Kodi but the devs don't feel any need to make it possible for everyone by default, even if that default is a "hack" which would take one of these pros a few minutes to code into the only skin the devs support. Oh well, I asked for the masses and was shunned for it. Good day.