When loading a project where a global part VSTi has been routet to a Song Group, the routing needs to be re-assigned to work.
I want a global part VSTi, while being able to control e.g. volume on a per song basis - thus routing to a Song Group should do the trick. However, something seems to be wrong when routing a global part to a Song Group. The routing connection is non-functional on re-load.
You are assigning a global object to a local instance.
The local insance (aka Song Group) exists only while the Song it belongs to is active. Thus, the global Part looses its connection when the Song is un-selected.
What’s confusing is, that it visually displays what you expect, but that’s actually a bug.
When you assign the global channel output to another Song Group, as you do, it will keep that assignment until you choose Song 1 again and so on.
We will try to solve this, but it kinda contradicts the meanings of “global” and “local” (Song only related). But we understand that it is intuitive to proceed like so and try to map it.
Yes, I know it’s somewhat contradictive to assign a global layer to a local Song Group. However, I’ll explain why this can be very useful IMO.
Say I have a couple of VSTis that are the backbone of my setup - i.e. they must be available in every song. At the same time, I want to be able to make tweaks to the output of those VSTis on a per song basis. This could be e.g. volume, insert pocessing et cetera.
On top of this, I want to be able to make changes to the VSTi itself - while having these changes propagate to all songs. In case of a Piano, I might decide to use a different Piano VSTi entirely.
Routing a global layer to a Song Group allows me the flexibility of doing these actions, without having to change each song individually. The culprit is of course flexibility. Before diving head first into setting up all the songs for a show, I take a long and hard think about which parameters (e.g. volume, processing, sounds) may require tweaking on a global/local basis. I then setup my project to allow for these eventualities as far as possible.
In other words, I want to use VSTLive as part of the creative proces when playing music - in order to facilitate show changes or when the bandleader says “can we just try another piano sound? (for the show entire)”.
I think VSTLive has the potential to really shine in this kind of use case, and is definitely on this path. Even though I myself may post a bunch of feature requests from time to time (as I become more involved in using VL), I want to emphasize that so much is also done just right in VL.
@musicullum If all Global Layers & Stacks could output to a Virtual Audio channel then this could be used as an input to individual Songs either at track or mixer level. This would allow you to solve the bug that allows Globals to be assigned (unsuccessfully) to Song Groups.
You can create an audio output channel in mixer (green channel), and create an out in connections and assign virtual audio out 1+2. Then set the green channel to your virtual out 1+2
Then route the audio out from the global VSTi layer to you green channel virtual out 1+2.
Then for every song create a song stack and set vitual audio in 1+2 as input for the song stack. This way you have global vsti with per song audio channel (inserts and sends on the global layer are…
Well global and persistent, inserts and sends on song stacks are per song and retained correctly on a per song basis).