The volume fader of a track with an assigned global layer does not affect the VSTi

1. Create one global layer.

2. Assign tracks from multiple songs to the global layer, and set different volume levels for each using the track’s faders.

3. The volume should change whenever you switch between songs; however, this change is sometimes reflected and sometimes not.

best regards.

on vst live pro 3.0.68

Can’t reproduce, 2 Songs each with one audio track, both tracks diferent levels, sent to global Stack. Tracks keep levels at all times. Maybe you assume the Stack Volume follows Song? It doesn’t, it’s global.

Would you have a step-by-step repro?

Apologies for the lack of information.
For example,suppose I create a “global part” and assign a single VSTi as a “global layer.”
I then set the output of MIDI tracks created via “create MIDI track” within various songs to this global layer.
If I then adjust the faders to send different volume levels for each song, the interface displays the different values, but it appears that the MIDI volume data is not actually being sent.

ah MIDI volume…will check.

I’m sorry.Thank you.
Whether using external MIDI or VSTi via a layer, the transmission of MIDI volume seems inconsistent—sometimes it’s sent, and sometimes it isn’t. Audio volume, by contrast, remains stable.

Are you sure not to be confused by looking at global, or local? If “Globals” is selected (see pic) you see the global Layers only.

Also, if you set both local and global Layers to the same MIDI output, the result of what is beeing sent to that output can be unpredictable. But why would you want to do that?

image

I am not confusing the two.
I set up various piano and pad sounds as a “global layer” and use them across my live performance setlist by switching between songs.

This works because I can simply adjust the volume levels to reuse the same sounds for different tracks.
Sounds that are specific to individual songs (such as lead sounds) or those that require specific keyboard zones are accessed via standard layers.

For example, for the first song, I recall an acoustic piano?configured within the “global layers” via the “tracks” section and enable the “monitor” function to play it.
At the same time, I use the “layer” setting to specify a unique sound to be played from a separate keyboard.
For the second song, I recall an electric piano and a pad?both configured in the “global layers” via the “tracks” section, and enable the “monitor” function for each to play them.
That is how I use the system.

If I were to load every sound using the “layer” setting, it would result in a waste of memory whenever I wanted to use the same sound from the same VSTi across different songs.

I want to save memory by using VSTis that are shared across multiple songs as “global layers”.

Sorry for the long message.

Interesting - try this:-
Add your Global layer
Copy the Global layer and paste it as a Shared layer into your song(s). Shared layers only have one instance of the VSTi in memory.
Adjust the layer volume in the particular song as needed, the volumes should now restore correctly.
Other benefits: you can send program changes per song if the VSTi supports it, also quick controls per song part and more.

I would also add that you don’t actually have to use a Global Layer. Any Layer can be shared across parts and songs.

So, the idea is to use a shared layer instead of the MIDI output destination for the MIDI track in [tracks].
I’ll give that a try.
Thank you.

As an additional note, I previously encountered an issue where MIDI volume output from a layer to an external MIDI sound source did not function correctly (sometimes it would be sent, other times not).

I wondered if there might be a bug causing MIDI volume to fail to output properly for the same reason.
I will try using a shared layer for the VSTi.
Thank you.

I send volume to my HydraSynth all the time with no problems.

One thing that caught me was that, at least on the HydraSynth, the MIDI volume resets to max on program change, so I have to set that every time.

If you’re feeding it from a MIDI track why not bounce it down to audio? Saves memory and CPU.

I use this strictly for real-time performance as a keyboard sound source during live shows.
It would be great if it were easier to distinguish between “shared layers” and standard layers at a glance.
I’ve been using the “tracks” feature because I find it intuitive much like how the VST instrument rack works in Cubase.

Shared layers have an “S” graphic next to the Layer name

Oh, I missed that! Thank you!

Instead of using “Global Part” I think I’ll try creating a song that has an “Instrument Rack” set up for the first track, and then sharing the sound source assigned to it by selecting it from the “shared” option in the MIDI output list of other songs.

Thanks for letting me know!

… we could finally fix this one. The fix has been added to the upcoming Pre-Release (3.0.69) which is coming today (Friday).

See you,
Michael.

I have confirmed that it is fixed. Thank you!