Well...I would rather see something definitive from Dolby. You well be right, but I never heard it in that way before, that is, having to null the objects between the bed and height? layers.
I notice that with the lossy encoding from the streamers, there is often only one bed channel, Lfe, and the rest is objects, at least according to Mediainfo.
Since I seldom break down a Blu Ray beyond .iso, I don't think I've examined on a track level with Mediainfo in quite some time how it recognizes bed/objects.
Still, it's fascinating. My only goal here is to get more knowledge.
Dolby does definitely define a nulling process is happening, as Dolby uses nulling for actually storing channels. This is described in the Dolby TrueHD White Paper, and can be witnessed looking at the source code for open-source decoders such as FFMPEG. I'll recap what I said in the missing thread.
See, when TrueHD was still Meridian Lossless Packing and still being developed, one of the requirements was to minimize the work lower-end players have to do. So, MLP was designed to store a downmix (which could be decoded by low-end stereo players easily) and recovery channels. What MLP would do on higher-end multichannel players is take the downmix, null out the rears, center, and sub from it, and place them in the respective channels. The end result would be a reconstructed 5.1 mix that perfectly matches the original source file.
When MLP got changed to TrueHD and 7.1 sound hit the scene on Blu-ray, Dolby thought, "Hey, we'll just do the same thing, it makes sense and it's backwards compatible" so they made the two extra channels for 7.1 was made into extra data that 5.1 players could ignore. Same lossless nulling principle.
So at this point, TrueHD stored its audio like this:
Section 1: Stereo Downmix
Section 2: Recovery Channels to Reconstruct 5.1 Mix
Section 3: Recovery Channels to Reconstruct 7.1 Mix
And if your player didn't support a section it could ignore it. Well Dolby calls them TrueHD sub streams but people get that confused with actual sub streams of a feature so I'm calling them sections.
Now with Atmos, Dolby did the same thing again, adding a 4th section. However, we've got objects now, and so we need to store some position data and stuff.
The thing that calls into question and requires testing to verify claims is that unlike 5.1 and 7.1, Atmos in TrueHD is not getting encoded from a static set of channels that it can perfectly match the data of. Atmos is encoding from a ADM BWF, which means the Atmos encoder is doing some processing to fold that humongous data down to a normal stream, and the decoder is doing some extra work reproducing the positions of said objects and nulling them out from the bed. And object nulling from the bed may not be entirely lossless in theory, as it may be relying on some psychoacoustic nulling rather than pure simple math (at least that was what was implied).
Rather long message from someone like me but I hope that explains where I'm coming from. I am trying to understand how Atmos audio at home is stored, but it's a bit harder when the secrets are locked away!