Comments

Musicvid wrote on 11/20/2020, 9:39 AM

Plugin support in Vegas depends on a number of things, including whether it was written to work in Vegas. Perhaps if you were to name your plugin and tell us what 'glitchy' means to you, someone here may have had some experience with it.

kyleknapp wrote on 11/22/2020, 2:31 PM

It's a reverb effect called EpicVerb, created by Variety of Sound. It uses the Steinberg VST standard.

When I first ran VMS, it automatically loaded a large assortment of VST plugins that were already installed on my computer, most of which were probably not written with Vegas in mind.

I've observed two glitches with EpicVerb:

  1. it intermittently creates an audio artifact at the beginning of playback, which sounds like a brief (a few milliseconds) burst of the effect taking from another part of the video. So when I render to a movie file, it starts with a brief but annoying echoey noise.
  2. in the effects window, the GUI of the effect sometimes disappears, leaving a blank white rectangle. The effect continues to function, but I can't adjust it. I have to close and restart VMS to get it back.
  3. Also, VMS17 continues to crash intermittently, but I don't know whether this is due to buggy plugins, a bug in VMS itself, or something else.

I tried replacing it with Vegas' "ExpressFX Reverb", but it just doesn't sound as good.
I've just now discovered another Vegas reverb plugin simply called "Reverb", which seems to have more controls, so I may give that a try.

Since VMS installed in C:\Progarm Files rather than C:\Progarm Files (x86), I assume it is a 64-bit program, and would expect it to support only 64-bit plugins. But if I learned it was capable of natively supporting 32-bit plugins, I would try installing the original 32-bit version of EpicVerb, rather than the jBridge-modded 64-bit version I've been using, hence my original question.