Originally Posted by Lasalle
Thank you, if supported this seems to provide enough flexibility. It looks like the only issue you would need to be careful of is the initial assignment of those speakers that (in some configurations) you would want to have arrayed copies of and those speakers that on one configuration would be an input channel and in another be a copied array.
The speakers that you want to be the input channel that is the source of a copied array would need to be assigned in 1-16. Conversely those that serve dual purpose as a copied array in a second configuration would need to be assigned to channels 17-24.
An example would be the Atmos Top back speakers being used by the Auro 3D configuration to extend the Auro Surround heights back. In this case the Auro SH's would be assigned in 1-16 while the Atmos TB's would be in 17-24. This would preclude the TB's from being the source of an array in any of the configurations.
Is this correct?
Not quite no. The TB could still be the source of an array as they will still be an input channel in an Atmos set-up (1-16). Think of it like this - the output channels can each be physical speakers, the input channels are the independent content 'signals'. The input channels (content signals) are fixed within the limits of the layouts that can be selected within bass management, and will be different depending on which speaker layout is selected (so input channel 16 is VOG for the Auro 13.1 layout, but it might be TBL for an Atmos 9.1.6 layout). But any output channel (physical speaker) can be mapped to an input channel. So you can map all output channels (speakers) to input channel 1 (front left) if you want, but input channel 1 will always be FL.
Your example is a relevant one though as several RS20i owners, including myself, are running 15.1 for Auro with rear surround heights mapped from the Auro side surround height input channel, and intend to use those rear height channels for Atmos.
So running the example, for Auro output channels 13 (SHB-Left) and 14 (SHB-Right) essentially act as array channels, and are mapped to input channels 11 (SH-Left) and 12 (SH-right) - input channels 13 and 14 are left unused. When switching to Atmos I would guess we will assign all four output channels to separate input channels, for example 11 (TM-left), 12 (TM-right), 13 (TB-left), 14 (TB-right), as one example.
This example wouldn't require the expansion card though. An example that uses the expansion card would be the Auro Centre Height and VOG.
So running this example for an Auro layout you might have output channel 15 (VOG speaker) mapped to input channel 15 (VOG), and output channel 16 (centre height speaker) mapped to input channel 16 (Centre height). When you then switch to Atmos you won't want the centre height or VOG speakers playing, so now you turn output channels 15 and 16 off, and then map expansion card output channel 17 (wide 60 degree left speaker) to input channel 15 (60 degree left), and expansion card output channel 18 (wide 60 degree right speaker) to input channel 15 (60 degree right).
Sorry of this isn't very clear - there are so many permutations and combinations possible it becomes difficult to describe in written form. Essentially to summarise:
1. All output channels (1-16 and 17-24 [with expansion card]) will need to be either mapped to one of the 16 input channels (1-16) or switched off (if switching off is possible, I need to check!)
2. The content signal of each input channel is fixed.
3. The content signal of any specific input channel is determined by the specific speaker layout/format selected within bass management. (i.e. 5.1, 7.1, DTS: Neo X, Auro3D 9.1, Auro3D 11.1, Auro3D 13.1 etc etc)
3. Any output channel (physical speaker) can be mapped to any of the 16 input channels such that all speakers mapped to any one input channel will use play the same signal.
Bear in mind with the Atmos examples above I am completely surmising here. Until we see how Datasat actually implement Atmos, and how they go about combining it with Auro, we won't actually know exactly how it will work.
They may have come up with a really smart solution that will auto signal sense and use the correct routing table depending on the input signal, without having to create separate input containers that have to be manually switched to depending on the content being played.