I have an issue using VST Live (1.4.0):
I set a setlist containing 10 songs, some of them having multiple parts and almost all of them having multiple layers. I use a MIDI controller (M-Audio Keystation 61).
I have all my layers transposed to -2. When I reach the last song (one single part), one of the layers sounds as if it was transposed to -4, but the indicator shows -2. If I click the panic button, it gets fixed, but every time I switch from other song to this last, the same layer sounds overtransposed again. Only this layer.
This layer uses KORG Triton VST, but I use this same plugin in many layers without having any problems, and this has happened to me using other VSTs.
Cannot reproduce this, but if you send us your .vlprj file (just that, no audio etc), we can examine it for problems.
Also you should know , in “Edit/Preferences/Layer”, there is a “Global Layer Transpose” feature which you may have missed. In some bands, guitar players tune a semitone down, and when you forget that, it comes in quite handy during soundcheck 
1 Like
AngelNegro2024-2.vlprj (503,5 KB)
Here is the file.
Yes, I transpose almost all my layers to -2 because the guitar and bass players from my band tune in D.
I am not using Global Transposition because I have a second keyboard that is a synth and I already have it transposed to -2. In some songs, instead of using its own synth sounds, I trigger sounds from the project. The layers for that keyboard are not transposed (transpose = 0).
Replaced the -2 Layer plug with Halion Sonic (which comes with VST Live), and no such issue. I can switch from any Song to there, and transpose is not only shown -2, but also sounds -2.
Can you confirm that?
However I also see that you have 2 Layers sending to the same plug (different instances though), the 2nd beeing a shared instance. Maybe the plug does not like it like that…who knows.
In cases like these, one can send to a Virtual MIDI Output (N) instead of the Instrument, and then check with the MIDI Monitor set to the same Virtual Input (N) to see what is (rather, would be) sent to the plugin.
1 Like
It seems that if I delete this layer and create a new one from zero (not duplicating because that is what I had tried before) using the same plugin I use, the problem does not happen anymore.
Thank you for the idea