Audio glitches, VST plugins, with Vegas 15

JMacSTL wrote on 9/1/2017, 4:05 PM

Just downloaded the trial of Vegas 15 today. First thing I did is load up a project that had lots of Waves audio plugins in it. Tried zooming the timeline; guess what: GLITCHES. Tried moving the plugin window around on the desktop, and LOTS of glitches to the point where the audio just stopped playing. Changed audio driver to a non-ASIO and using an analog output....maybe a bit better here. Then I upped the track buffering and it got a little better (not as many glitches). So, did they address this issue, or not yet perhaps?

Here's a question: Since I've been running Vegas11-32bit (Waves 32bit plugins work great) and Vegas11-64 bit (Waves plugins don't work....still glitchy), I have both 32bit and 64bit versions of all my plugins installed on the same PC. So, how do I make sure that when I launch Vegas 15, it's only looking for the 64bit versions of my plugins? Unsure of how to identify this, other than re-scanning my VST folders and making sure to ONLY choose the 64bit folders.

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

Comments

JMacSTL wrote on 9/1/2017, 4:20 PM

here's an update: I tricked Vegas 15 into ignoring the 64bit Waves plugins by renaming the folder on the 64bit side, and then rescanning the VST folder on the x86 side. It found and loaded all the plugins for a project and there were no glitches. So this just points back to Waves 64 bit versions having the issue (altho I also use ProTools 11 on this same PC with the same 64bit Waves plugins with NO problems). That's the latest. i do have a workaround if I upgrade to 15 from 11. Still would need to buy a new video card for external monitor, as Vegas hasn't supported my AJA for the past three versions.

 

jmm in STL

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

NickHope wrote on 9/1/2017, 9:59 PM

Unfortunately there has been no development in VP15 to fix the VST issues. There was a bit of discussion in the News thread starting at this comment: https://www.vegascreativesoftware.info/us/forum/release-vegas-pro-15-inspiration-meets-productivity--108313/#ca667827

...So, how do I make sure that when I launch Vegas 15, it's only looking for the 64bit versions of my plugins?...

In Preferences > VST Effects, just have (for example) C:\Program Files\Vstplugins\ as your "Default VST search folder" and leave the 2 "Alternate VST search folder" fields empty. If you have any 32-bit VSTs that don't have 64-bit versions then you can put them in a subfolder of your 64-bit VSTs folder and Vegas will still find and load them. My such folder is called C:\Program Files\Vstplugins\32-bit-not-available-as-64-bit\ and contains iZotope Vinyl and Mastering and Repair Suite, which never got 64-bit versions etc..