Chris Gilland
unread,Jul 5, 2024, 10:05:19 PM7/5/24Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to ptac...@googlegroups.com
Hey guys.
So, upon playing a little more, and doing some research, I figured out what happened, and why I didn't see Studio Rack any longer in my list of plugins inside ProTools.
This may prove helpful for those of you who used to use it.
It turns out, starting in Waves 15, they've done away with the dedicated Studio Rack plugin. Now, before you pannick and say, I have tons of tons of presets and chains I've configured through there, so great! Now what am I gonna do! You're not totally S O L.
What happened is, Waves has basically integrated Studio Rack now into the plugin called StudioVerse. You'll find it either under the venders in the plugin popup menu, or, if you're doing it by category, its under Effects, and is simply just called "StudioVerse".
You will definitely definitely need VOCR, as the plugin isn't exactly the most accessible otherwise with Voiceover. Using Aira over Teamviewer, an agent who happened to work some in the audio field as well on the side helped me figure this out.
Right below the line with VOCR that talks about search, recent, user, etcetera, when you first load the plugin, you'll see something that says "Full Reset". This is what you need with VOCR to click with the mouse, if you want to get to the Waves Shell preset manager menu. So instead of looking for the A default area like most waves plugins to get to that area, this one's a little different. It took me a bit to figure that out, but yeah. So if you have any custom xps presets that you used with Studio Rack inside a session in PT, they'll still work. Just load them up inside of StudioVerse instead using VOCR, and you'll be on your way. Just remember, "Full reset" is what you need to be clicking on. There is no "A Default", like in other Waves Plugins. Obviously, if you're still on Waves 14, you won't have this issue. This is only for those like myself who've updated to V15.
HTH someone and saves some future headaches.
Chris.