That is why i created the Conductor and Slave units.
Say you have a 40,000 channel setup.
You divide the show into two sections of ~ 20,000 channels each and you seqence them as two shows with the same music.
Then you create Conductor files out of them and one goes on the conductor and the other goes on the slave.
Now yuo only needed a seqencing software that could handle 20,000 channels. You did no additional work and you have hardware that can easily handle the 20,000 each you needed.
So in the future you may create the megatree of pixels with 12,000 + channels as a seqence all of its own using something like Nutcracker or tranistions in LSP ect. then it would go on a slave of its own, then the next items would be seqenced on their own maybe in a different package like vixen and be loaded to another slave, ect. As long as the same music is used the different parts are alway in sync so it will not matter if they are created seperately. you can use the best tool for that part of the show without issues and it would not lock you into only using that software for the whole show. As long as it converts to run on a conductor or slave file.
I'm breaking the enomous shows into small more managable parts to help on the software and hardware sides both.
RJ