Tried to do this but at the moment VST live cannot remember routing of a global channel to a song group “FOR EACH SONG”, even if you name each song group the same name in each song (workaround send global stack to song stack via virtual audio cables).
The really useful config should be that for a global channel you can set a global output routing AND a per song specific output routing by having TWO dedicated routing out fields in the channel strip.
When a song output routing is present, that takes priority over the global output routing (global out greyed out if a song out selected, otherwise select “no song out” and the global is available; that should work per each song).
so I can have my “vocals” global stack (4 global inserts in stack, 8 global inserts on global channel) routed to global group “global vocals fx”, but also in “song A” I can route to song group “vocals song A FX” (that takes priority over the global routing, so no signal goes to global group FX) for 8 more song specific inserts”. Song B can have another song group FX B, while song C does not have it so the routing fall back to global vocals FX global group.
That would have mega flexibility, and would need 2 out routing field in channel strip, one that only allows global outs, the other that allow per song “song outs”.
Cheers, Ciro.
Edit: something like this:
I guess with such flexibility we will have 10x more questions and issues.
For me the virtual cables are enough to make the same complicated setup. Maybe later there may be 2x more virtual cables. But I know you have a huge project and it’s much more complicated than mine.
Honestly i don’t even need this, solved long ago. But if i had this routing possibility couple years ago, i wouldn’t have created many automations to move parameters of delay rev etc each song (even if that would have multiplied plugins in the project, but light plugins and song only so …)
anyway that is just an idea 
Ok, my two cents here. I get it, that you all get along. The answers in this forum point out, that there is nearly a workaround for everything. But I don’t use the software from a programmers or a knowing-all-hacks view. I use it as user and if I select an Output I expect that the routing goes to that Output. And in fact it does and works as ecpected, except that it is not saved. And here again comes the question, where do you want to go with VST Live … having a software with a hard learning curve or a software you can use as intuitive as possible. I‘m convinced you lose a lot of new users because of the „workaround situation“. There is a lot of help in this forum, but I think there would be a big chance that less help would be needed.
While you have some valid point, that is far reached. To get to that point, you chose a pretty specific route, maybe by intuition, though intuition would rather tell me to do it a more direct way that the app layout suggests. But point taken, we will check what we can do to avoid this situation.
I agree with this statement 100%.
Otherwise, they’ll create virtual audio, and then most likely end up with a situation where no one, not even the developers themselves, understands where the signal is coming from in the group song from this thread (Volume bump on part transition - #61 by sergeantt67), especially since there’s no signal sent from the stack in the mixer. This very much resembles a signal leak from the stack’s virtual audio channel…
Because I don’t see this in either Cubase or Ableton; such miracles are only possible in VST Live.
Well. Some features are “by design”. Sometimes “by design” is buggy. And sometimes “by design” wasn’t the best idea to get things done to start off.
All of these aspects can and should definitely be discussed here, complained about, ranted over, foot-stomping included.
But it would really help the team greatly if we managed to stay on topic .
Thanks for your attention
Kai
@musicullum Fair enough, maybe I did overstate that part. Wasn’t trying to make it sound like a mass exodus, just my gut feeling from browsing the forum a bit.
As for the route I took — you’re probably right that there’s a more direct way. Honestly, I just haven’t gotten the logic behind the routing/saving behavior, so I ended up figuring it out by trial and error rather than the intended way.
Appreciate you taking the core point seriously either way.
