Correct, it saves me a lot of time from now on as for a rack space i have done already once before I no longer need to connect widgets to plugins.
Therefore I would organise this in a hierarchical structure (like you do in software or hardware design). Then you would not get the A, B problem you mention above as these would be local to the track space and they both can be A.
I would have audio-ins and audio-outs only on the top layer. Rackspaces would not have their own audio-in/out. They would be connected at the top layer. This can be done quickly at the end. Panel and wiring need to be one unit. What costs most of my time is the re-wiring of widgets on panels to plugins in wiring which I had already done one before. Why do it again.
I have all my main sounds setup in global and I just bypass the sounds I don’t need for each rackspace in local. Works a charm.
I can’t remember off the top of my head but I think I have about 27 instruments in global with their eqs and reverbs…
When everything is bypassed, the total GP CPU reading is about 2 - 3 % so that’s awesome.
Saves RAM and is really easy to create new rackspaces with repeated instruments…
Do you then have 27 Panels in the global rackspace.
Can you refer me to a page in the manual where it is described how sounds setup in global rackspace are then bypassed in the local rackspace, if they are not needed.