Hello everyone!
I decided to share my experience on this example of a plugin from Mercurial AmpBox, maybe someone will find this experience useful…
The task was the following, to create a MIDI track and make this plugin control via the Program Change command. It didn’t work right away ((during the experiment VST 3 flatly refused to do this, as it turned out due to the limitations of this format (I found such a description on the Internet) it can only accept MIDI commands (CC) inside the host. I didn’t give up because I couldn’t find anything about this limitation about VST2, I deleted AmpBox for some reason VST Live doesn’t see both VST2 and VST3 at the same time.
I installed VST2 AmpBox and I present the result!
yes, here you can see that I used the loop midi program, in this case it is not needed, internal virtual midi ports of VST Live are enough.
but if you need to bring something out of the host and control something, then all this works)
Good luck to everyone, Sergey!
1 Like
The big question is if Ampbox VST3 supports
“ Program list “ object and preset change with CC** ?
no it can’t (CC) change the saved program only the same parameters that are available for automation, that is, these
but it is easier to implement through automation
and switching these programs with the vst3 command (CC) simply can’t do this, only Program Change can do it and only in vst2
I will refer to No Program Changes in VST3 - regrettable decision - #2 by Arne_Scheffler
based on this, that vst 3 can still support it, it’s just that the plugin manufacturers don’t implement it
ChatGPT generated me the missong code lines that should manufacturer use 
I wrote to Mercurial support to ask them to consider adding this to VST 3.
1 Like
Meanwhile ProgramList object recalled with MIDI CC is the new, preferred way
1 Like
Same with amplitube 5, I had to install vst2 version to use program changes via midi track and vmidi in VST Live
1 Like
Here is what the developers of mercuriall answered me today, I quote from their letter to me:
We have already discussed this problem with the developers and perhaps in the future we will be able to implement it for VST3.
Of course, if the mechanisms of the standards allow this to be done:)
Dear Sergey! Dear all!
I’m using the ampbox VST2 plugin in Cubase 14. I’m sending a MIDI automation track with program change values to it, but nothing happens. The plugin isn’t automating. Could you tell me what I’m doing wrong? Maybe you could create a short tutorial with screenshots on setting up ampbox automation for program change?
Thank you!
1 Like
Hi!
Right-click on the created MIDI track and use the drop-down menu to customize the track controls, Installation of controls
add an output
A new menu will appear on the track, and select Ampbox there.
Next, create a MIDI event and select which programs you want to switch.
And it should turn out like in the video.
Thank you, Sergey!
I’ll try to do it this way tonight one more time, but it seems that I’m deadly lucky. I did it many times definitely this way yesterday…
but you see the result works)))), and also delete VST 3, maybe you just pick it up and it definitely won’t work. I usually either delete it right away or leave it somewhere else, although it’s always easier to reinstall it if you need it.
We did everything as you suggested. We made sure the plugin was a VST2 and that there was no VST3 plugin on the computer. But the received event indicator in AmpBox (marked with an arrow on the screenshot) doesn’t turn orange. Is there another way to check MIDI routing inside Cubase?
Thank you!
I wrote in a private message
