I reworked my project and started to use the Global Stack Mixer Channel to use more than 4 Inserts. Works so far, except that the Out of the Global Stack Mixer Channel is always set to “PA” when I load the Project.
This is how it should look like (especially the Out of Channel 1 pointing to the Song Group “Vocals”:
But if I reload the Project the Out of the “Voice In”-Channel is always set to “PA”, which is the Main Out (and the first entry in the List - if that matters).
Song Groups are only active during the Song they belong to, so I would doubt that. Then the question is, why do you want to route a global instance to a Song specific one in the first place? You should use a global Group instead.
It was the least impact in changing my Project. I thought I could make my Song-specific adjustments here. Counter-question is why shouldn’t I? When I set the Out to Vocals everything works as it should so far - except that the Out is lost after reload.
That is not a Song Group, but a global Group (“Aux” Channel), though I may be wrong as the colors are very close.
Left to right: Layer, Stack, Song Channel (Bus, always present and specific to this Song), Song Group (user created, specific to this Song), (global) Group, Out.
However if (as?) you route your global Stack to a global Group, it should not change when you load it, but we could not reproduce that. You could send your project file (just the .vlprj file, no audio/midi etc files needed) so we can try to analyse it. Or, a step-by-step repro.
So, that @Kai_Schwirzke stays happy I push my issue that is not about Layers but Stacks and Channels (but still feels the same) in my original post. Did you (@musicullum) get my Project?
Thanks for your project. Unfortunately, we cannot fix this.
Yes. A Song Group only “lives” as long as its Song is active. If you output a global Stack (or other global source) to a “local” (Song) Group, it will loose its connection when the Song is deactivated, you don’t even need to save and load, switching to another Song and back will already leave the global Stack clueless, and it connects to the first global instance it can find (Group or Out channel).
We will check to see that for global Stacks and Layers, local channels will not be selectable. Remembering local connections for each global instance and each Song is not an option, it would make the project too complex and may cause other problems. The global Stack is supposed to be used with other global channels, sorry.
Actually that is not the case (on my side) … I have to set it once I loaded the Project. Then it works as it‘s ment to be … all the time, without any problems, regardless of switching randomly through the Songs.
But if there is nothing you can do, I will try another way (after my concert this weekend).
Thanks for checking
I admit, I lack how to do it the proper way:
Vox in → (6 global Effects for all Songs) → Volume, Pan, Sends, additional Effects per song → Vocal Group per Song → Master Group per Song → Main Out
Just create another output channel, call it “global stack X loop”, set routing to virtual audio out X.
Then set routing of global stack X to output on the loop to virtual audio out X.
then for each song, create a PART stack X with input from virtual audio IN X.
NOW YOU WILL HAVE A GLOBAL STACK WITH GLOBAL FX AND INSERTS (4 on stack plus 8 on mixer channel) that goes to a part stack with part related inserts/sends.
Each part of each son will have its own additional inserts/sends after the global channel.
Cheers, Ciro.
Edit: only limitation for now is that we have limited (8) virtual audio cables, that means you can redirect max 8 global stacks
That would be “one” direct way The other truly direct way is to copy/paste your “Global” stack wherever you want it to reside, apply specific adjustments and remove the global instance altogether. It usually doesn’t cost much.
Please take this with all my respect and as just a discussiom about this topic.
As STACKS don’t have “shared feature” (compared with LAYERS”) users might get lost with tiny changes that needs to done on hundreeds of songs afterwards maybe.
From this point of view, I find Ciro’s VMCABLE idea a more overview-able solution in long term
OFF
I had an another idea in my head, writing here but I have doubt if it worth any effort and maybe wont be a possible solution either:
SongVCA (like Song Group, but VCA) that could VCA channels within the song, but another song could VCA others or none, by resetting VCA-multiplyer$ at every songChanges.
Also that would only work if the SongVCA-channel could store all linked channelFaders (tick-box) by letting the channels not knowing about this at all
But that would bring in way too much coding-work and complexity also… so just anyone forget it plz
ON
… probably I find it one day.
The other truly direct way is to copy/paste your “Global” stack wherever you want it to reside, apply specific adjustments and remove the global instance altogether. It usually doesn’t cost much.