MMH already does everything but make my breakfast. ![Unsure :unsure: :unsure:](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Well as you found out, DTS-HD does not hold Atmos. I believe it can hold Auro3D.Finally, I got myself a copy of Oppenheimer and for some reason thought that DTS HD MA 5.1 actually holds some ATMOS data. My judgment was clearly tainted by my desire to get nuked, but... anyways...
The ATMOS decoder still happily allows decoding the track. However, probably because there is no actual ATMOS data, it silently fails (delivering a 0kb .w64 file) with no error and simply says "done" when choosing anything above a 5.1 configuration.
It would have been nice if it could decode the highest possible configuration up to whatever you chose. Doing it manually through a Python decoder simply spits out empty tracks with no data for those channels. MMH could possibly do the same or even something smarter.![]()
Or separate the channels with MMH also, missed editing this yesterday. Thanks @Sylfest for reminding.Well as you found out, DTS-HD does not hold Atmos. I believe it can hold Auro3D.
The quick and dirty way to decode Atmos into separate tracks would be to use the Dolby Reference Player and live capture the tracks in a DAW. I can't tell you all involved, I just know some people do it.
If you're ripping an actual disc with Atmos content, or have extracted the decrypted .iso file, you can use makeMKV to encode as MKV. Then you can use MMH to convert to flac or wav. Then you could separate individual channels with a DAW, if that's what you're looking to do.
MMH can do that also.hen you could separate individual channels with a DAW, if that's what you're looking to do.
You are of course right. After I quoted myself above I meant to add that but got sidetracked. lol.MMH can do that also.
Do you think one day MMH will be able to convert audio from MKV to ADM BWF?
Also, although I think I understand the intent, we're drifting afar from an enthusiasts program into professional grade applications. If the content is being taught at an advanced level, one would hope the school is providing the necessary software and the instructors school themselves on using it.No. Your best hope is Cavern will eventually decode Atmos TrueHD.
I might have not been clear. What I meant is that it would have been great if MMH ATMOS Decoder could understand mistakes in the provided configuration and "fix them," either by showing a notification like "channel configuration incorrect please lower the channel count" or by simply outputting what it can.
What I was describing is that the decoder accepted DTS HD MA 5.1 as having Atmos data.. I was expecting then for the decoder to output silent tracks as you have described but instead it silently fails.The Atmos decoder just "render" the input provided (TrueHD or DD+ Atmos) to the configuration setting (either 5.1.2, 7.1.4 or whatever) the same way an AVR Atmos decoder does with the available speaker configuration. If the mix is done in such a way that there is no content for a bed channel, neither object location content for that "channel", that channel will be "empty" or "silence". It cannot be "flagged" as a "mistake", it was just the way the mixer engineer did. That "mistake" can be seen by us if we find a complete empty channel after the decode.
With the "decoding" we lose the information of Object Metada and get only a multichannel file with the channel number specified. Some channels could be empty, if the original mix is done that way.
If the objective is to tune the mix, by editing individual channels (altering the level, mixing/merging content, etc.) then I would decode to the maximum available channels of the tool 9.1.6. Then see if there is content or not in some channels, and after the editing of individual channels, "re-encode" to the number of channels apropriate for our system (i.,e. our same speakers configuration). This way the re-encoded Atmos will behave the same way it will behave in our speakers configuration system. The resulting encode will have the Object metadata altered, with respect to the original input. Or even inexistant if we re-encode to the max bed channels 7.1.2, or less.
I guess I can add code to reject input files without an Atmos stream but I assumed users would realise an Atmos Decoder will only function with Atmos input. I know the docs says that but who reads them, right?What I was describing is that the decoder accepted DTS HD MA 5.1 as having Atmos data.. I was expecting then for the decoder to output silent tracks as you have described but instead it silently fails.
Well it is an Atmos decoder it is in its nameI guess I can add code to reject input files without an Atmos stream but I assumed users would realise an Atmos Decoder will only function with Atmos input. I know the docs says that but who reads them, right?
I’ll add to my TO DO list.
Enter your email address to join: