This plugin is supposed to support microtuning from Dorico and other VST3 plugins. Oh, how would it be wonderful if it could "stay in tune" with the VI and Synchron players…
Try this free subhoster (Kushview Element). I just tested it inside VePro7 and using a VST3 plug inside that; nd it seems to work. its free.
I have also tested BlueCatAudio Patchworks, which crashed the VST version but worked ok so far with AU version. When it crashed, it caused Cubase to crash too! That's bad, hope VSL is taking notes.
I also tested PlogueBidule, which causes VePro and Cubase to crash once, but worked once too. Not sure what happened there.
I also tested DDFM MetaPlugin, which also seemed to work.
The last three products listed above, are not free. Image-line MiniModular is the other free one, but it doesn't support VST3 hosting and hasn't been updated in like 5 years.
I do not know why some of these plugins seem to crash VePro so badly, and even cause the DAW to crash along with them.
VST3 in General
It will be an improvement when VePro can host VST3. Me personally I am avoiding using VST3 plugins as much as possible due to poorly designed midi implementaiton of VST3. In almost all cases, the VST2 version of a given plugin will work better. In fact I have removed all the VST3 versions of my plugins off the system to avoid them completely, with the exception of only one, Vienna Ensemble Pro.vst3. The reason is because that supports 768 midi channels into VePro. So that is definitely worth using on Cubase. Also some Steinberg plugins came with Cubase are only in VST3 format, so I'm stuck using them. Otherwise, its VST2 all the way for me.
That being said, Steinberg has changed the licensing rules on their SDK for VST plugins. New developers are now unable to legally distribute VST2 plugins unless they were grand-fathered into the old VST licensing with a signed agreement. Older developers mostly have that license agreement and can continue to distribute VST2 plugins, but newer developers do not have a legal option to develop and distribute VST2, they must use VST3, even with the midi limitaitons that Steinberg imposed into the new SDK and is very stubborn on the issue as well I might add.
In any case, for that reason, in the future we may see more plugins come out that are VST3 only, due to the licensing changes. Its a good idea for VePro to get with the times and support VST3 for that reason, but I also realize that VST3 hosting is a bit convoluted at this time due to some of the midi problems already mentioned.