Use Case:
I am using VST Live for live performances with a music ensemble, incorporating playback tracks and an electric guitar with virtual emulations. For each song, I have a set of automations for the guitar plugin to switch between clean/lead/rhythm presets. To achieve this, I created a global stack, routed the guitar signal into it, and inserted the desired plugin. Everything worked fine up to this point. However, issues arose when I attempted to program MIDI-based automation for the guitar plugin using the Automation Track.
Issues Encountered:
Inconsistent MIDI Channel Button Visibility on Automation Tracks:
On the automation track, the button to select the MIDI channel would intermittently appear and disappear. I was unable to identify a consistent pattern or reproduce the steps leading to this behavior. Eventually, I simply memorized the previously selected MIDI channel and manually configured it in my plugin.
Automation Not Affecting Plugin Parameters:
After mapping the required CC controllers and drawing simple automation curves, the automations had no effect on the plugin. The mapped parameters (knobs) did not move as expected during playback.
Incorrect Controller Mapping List for Different Plugins:
I decided to switch from Bias FX 2 to STL Tonality Andy James. I added a new automation track and selected the second plugin as the target. However, in the mapping section for STL Tonality, the list of controllers displayed belonged to Bias FX instead of the newly selected plugin.
Persistent UI Glitch and Application Freeze:
While troubleshooting the issue by experimenting with different settings, the controller list either failed to open entirely (displaying only <nc>), opened with the wrong plugin’s controller list, or became stuck in an open state. Eventually, this caused VST Live to freeze completely.
Conclusion:
I hope these automation-related issues will be addressed in future updates. I truly appreciate VST Live for its lightweight design and potential, but the inability to reliably use plugin automations prevents me from using it for live performances. Until these issues are resolved, I will continue using Cubase with Arranger Track for managing setlists.
Thank you for the quick response and recommendation to update to the latest version. Indeed, some of the issues have been resolved. The list of available controllers now displays correctly for each insert, and the program no longer freezes when accessing the controller list.
However, I am still unable to automate my plugins. During playback, the plugin knobs do not move as expected. I double-checked my configuration against the instructions provided in this forum post and did not find any mistakes in my setup.
Additionally, I am still unable to select the desired MIDI channel. I am certain that I remember seeing the MIDI channel selector at some point, but I can no longer locate it anywhere.
Could you please provide further guidance on these remaining issues?
I think you are confusing automation tracks with midi tracks , different things .
Automation tracks can control quick controls exposed by the plug-in , but if you are trying to control the plug-in via midi assignment internal to the plug-in, you’ll have to use a midi track l, out to a virtual midi cable (vm out 1 for example), then set the plug-in to receive midi on vm in 1 … this way the midi from your track will be sent to va out 1 then vm in 1, then the plug-in.
I use midi track to send program changes to amplitude 5 to switch the presets that I saved inside the plug-in that way, meanwhile I control other plugins via automation track, for example enable disable inserts on stacks, set autotune parameters etc, every quick control that the plug-in exposes is available via automation tracks.
Okay. I do have some screenshots. Upon further investigation, it seems I was mistaken regarding the MIDI channel switching.
My apologies for the confusion. However, I must say that the current implementation is quite misleading. I find it unclear why in some cases the label appears as Channel N, while in others it shows N:<nc>. What exactly determines this behavior? If this is not related to MIDI channels, the naming convention should likely be reconsidered to avoid confusion.
Then, I add a similar automation track to Song 2, link it to the same guitar stack, but this time the parameter list for automation is completely empty.
I repeat the same process with another song in the tracklist, and the parameters reappear.
At this point, I’m starting to question whether I’m doing something wrong or if there’s an underlying issue. Is it me, or is the system itself inconsistent? (nervous laugh here.)
Additionally, even in cases where I manage to set up automation (for example, automating the gain knob on an amplifier), the plugin parameters do not change during playback.
Need to personally agree, some another expression / label, something like
“Param n.” would be better (something that explaint this is related to mapped parameter “n.”)
Tried with amplitube 5 , i can corrrectly automate parameters, need to assign it in plugin preferences (only 16 parameters can be exposed), maybe try with another kind of plugin, steinberg included plugins, to see if it’s a plugin specific problem … ?
