I can access that file, but can't run setup-looks like it's specific to Lenovo (I have an Intel Nuc HTPC). I think my main problem is driver signature....looks like it always stays disabled with Windows 11 and BIOS set with Secure Boot. I'm hesitant to disable Secure Boot, but it looks like that's really the only way. The web pages I linked should work for more PCs. Since this is more complicated, I'm going to get back to experimenting at a later date.
I don't understand why you'd think the sound wouldn't be on left side surround on a non Atmos system. I've been trying to indicate that when the ADM sound file gets rendered to DD+ Atmos in a movie file, there's a legacy 5.1 surround track. It has all audio channels for FL, C, FR, RL, RR (and if you have a legacy 7.1 speaker system, the receiver matrixes the RL with SL and RR with SR). I think maybe where hasn't been clarity-I've been saying that the Atmos decoder in the receiver (or A16) is interpreting the surround stream along with the JOC stream to first determine where the sound is in 3D space, and then maps that to what speakers you have. So even though a 5.1 stream might have a sound rear left, the Atmos decoder uses positional data to know what's intended for a height speaker with Atmos. You also indicated a theory about Atmos decoding using ratios in determining pans to speakers that aren't present in surround. From literature I've read, I think it's more complicated in order to be more versatile. When you setup a receiver, it has its microphone that sets each speakers characteristics (level from distance, crossover level for LFE, bass management, etc). If the Atmos decoder first renders an object based 3D field, it's easier to rely on the receiver's speaker config to map to each speaker. The concept is also more necessary with cinemas having a larger space and more speakers.
I already thought is was just a misunderstanding. When you answered "no" to one of my questions ("are they audible if the track is played with a normal Dolby Digital or TrueHD decoder ...") I understood that as "no, they are not audible" but I guess the "no" was about the second part ("or are they simply not audible when played by a normal Dolby Digital or trueHD decoder?"). Everything is clear now I think?
Of course I formulated it a bit simplified, of course in my example the 0.5 * Y to one and 0.5 * Y to another speaker would have to be refined with the proper application of level and delay etc. according to the speaker set-up.
Referring back to your question and my answer, I think my no was that "positional sounds" wouldn't be present in the legacy 5.1 stream. I also hadn't had my morning coffee
. But technically the JOC is positional data and not sounds (and makes this difficult to conceptualize) 
. That's what I find interesting from a software development side: there must be some sophisticated programming to be able to render out a base 5.1 layer that's compatible with legacy systems. Then use the JOC to create objects, take the audio channels for sound characteristics, and map them to the objects for a system that has an Atmos decoder.I think Dolby formulated the 3D object field approach to make it easier to map any given number of audio channels to a 3D space. I haven't been able to find much info with Dolby's new Dolby Surround format that's on Atmos systems (that takes a 5.1 or 7.1 movie and "matrixes" it to 3D). Or maybe it uses certain algorithms to figure out where that sound is in space, and renders a 3D object field like Atmos. Giving how convincingly it (and DTS:Neural) places objects that should be up above, it's either sophisticated matrixing or utilizing methods for first rendering to 3D audio.
