1000% (updated on both Mac and Win but tested on win only yet). Need to mention: The project I’ve sent you didn’t store the CommonSongGroup name for the 4diff songs, so first needed to set them back for my screen rec yest eve. (Therefore the version at you needs to set first as: GBL-STACK’s AudioOUT foreach songs == TestSongGroup” (that will be 4pcs of diff song contsined groups under the hood).
An output is the final destination for any signal, so that sounds wrong from a pro audio perspective 
Did you mean send Groups (Aux Channels) to Song Groups? Or be able to have Song specific sends (you can do that with automation though)?
I’ve explained what I want to do on multiple occasions, as other posters have also recognized. I want to have global channels for multiple vocalists that I process with multiple plugins. I then want to have a way to send those multiple channels at varying levels to a single stereo song group channel that I then output to separate stereo outputs of my Dante mixer and use those to return the effected signals on a separate fader. I create a song group in each song, instantiate the correct plugins for effects and route the vocal signals using the send from the mixer channels (not the green physical output channels). When I come back to that same song later, the send still appears active but no signal is sent until I redo the routing for the send. I had the issue come up when I tried to use consistent naming for the song groups (e.g., VocalFX1) or if I made the song group into a specific name for that song (e.g., VocalFXSong1).
That is the issue, I have yet to have time to test the latest build because of work and family commitments but I will today.
I’m frustrated by the responses nitpicking my errors in terminology (especially when this 40+ post thread explains the issue and ask multiple times over). Save your belittling comment masked as a joke for when you have a working product.
It was truly not my intention to be nitpicky at all, I’m really sorry if it came across like that. As you point out, these threads are very long, and there are really a lot of those, in addition to reports and a 600+ entry wishlist it is kinda tough to not only track all of those, but also try to fix things at the same time. After working through all of this thru the entire weekend, a Monday like yesterday may have led me to phrase in an offending way, and that wasn’t my intention at all. Quite on the contrary, we deeply respect your input and coopration.
Back to the issue, it looks like this is “just” about a bug that we most probably fixed already, let us know if it still doesn’t work out for you. But we’ll have another look at it anyway, there is another thread dealing with complexity of IEM setups like this.
To put it simple, he wants:
- global stack aux1 (send1) sent to multiple song groups of same name.
Global stack “vocals1” aux 1 sent to song 1 group “vocal FX”. Now for every other song make a song group named “vocal FX” with different iserts for each song. Every song that have a song group named “vocal fx” should receive the aux1 of global group.
At the moment it is not possible, at least for the times i tried. I succeded using virtual audio out onbthe global stck and virtual aidio in on each song stack. The song stack then routed to song group.
CIAO!
Oh, and by the way @h20fam , using my solutions, ifnyou have too much song stacks visiblenin mixer, after setting up everything as needed, you know you can hide mixer channels as you like, so you xan hide all the song stacks that just pass the signal to the song group right? Ciao!
Names of Song Groups have no meaning internally, because each and every channel has its own unique ID, and names are user related only.
There was a bug report that signals would be sent to multiple Song Group Channels because they had the same name, so there, it was considered a bug.
It is a tricky issue. In fact, Global Stacks should not offer Song Group Channels in the first place, they should be routed to (global) regular Group Channels, after all, they are global. But here, the wish is to use Song Groups for Song specific processing, which makes sense from a users point of view for “housekeeping” reasons, as you might as well create as many (global) Group Channels as required. That would clutter the mixer though, and as the “bug” to allow Song Groups as global Stack output is there already, we’ll add a function to route Global Stack output to Song Groups with the same name.
There must be a question box for this to ask if that is really what you want though, as it changes exiasting behaviour.
Exactly! That’s why asked if it is meant to work like this or not in January
Because although it’s a nonsense addess such song group that currently not being active, the app didn’t forbid to do, but got confused about…
But end of the day, can be very handy in specific situations.
That should be a good solution, maybe instead of a popup, an entry in preferences menu.
As per your proposed solution of multiple global group (and then automate return for each song) you only have 4 sends per stack, if you have 20 songs and want 20 different processing of the same global stack … you can’t. And you’ll have a ton of always active plugins (4 inserts for 4 groups you are at 16, but if you have 20 songs and 20 groups you’ll have hundreds of always acrive plugins… not good). Song group is loaded and unloaded accordingly, better optimization.
Ciao!
Ps: speaking about number of sends … pretty pleeeeaseee … add at least a 5th send … i need it 
1 Like
Exactly - there aren’t enough sends to do it on global groups and the automation isn’t user friendly enough to automate the plugins on every song (and I use at least 10+ different effects plugins based on the situation).
If you have different processing for every song, global stacks is not your best solution. In that case it is better to have an own stack in every song.
Nope! Absolutely not if you have also inserts IN the stack that you want to stay the same in the whole project. I tried it before going back to global stacks. As the numer of songs growth over 20 30 songs, having 6 input stacks per song, each one with same inserts replicated each songs, is a nightmare for dimension of the project, stability, ram usage, and silence in the stack as songs switches… AND if you want to adjust a parameter in one stack insert then you need to do it for each song as there isn’t such thing as Duplicate stacks …nighmare!
Most economical way is global stacks with fixed inserts processing, and send to global group automating parameters if you have same variable effects all songs, song groups as proposed if you have different inserts for variable processing for each song!
Ciao!!
But there is a duplicate stack
or did you mean “duplicate stack shared”? This will be the best solution.
Exactly, i mean shared 
