Vegas 18 still not saving state of Lexicon plugins

JimHWiltshire wrote on 8/6/2020, 11:24 AM

This is starting to drive me slightly nuts. Is there any 'official' technical support for Vegas?

Vegas 17 wasn't restoring the last state of any of my Lexicon PCM native reverb plugins, nor allowing me to save presets to load again, meaning I have to literally take photos of the parameters and manually set up several instances each time I open a session! It also didn't appear to remember various window sizes.

Ok, so I upgrade to Vegas 18 in the hope of this issue being resolved, but the exact same problem exists. I've reinstalled the said plugins to no avail, and even trialled the LXP plugin to see if that would work (same issue). Kind of at a loss as to what to do, and I rely on this software and have done for a very long time. No other plugins present this issue thus far, so it could be a Lexicon issue (they didn't reply to my email last month), but how can I get in touch with the Vegas developer for advice? Only via this forum, or am I missing something? Close to packing this software in!

Comments

Musicvid wrote on 8/6/2020, 11:29 AM

You won't get much support for third party plugins, I'm afraid. Contact the plugin developer directly and see if they can get it working for you.

Musicvid wrote on 8/6/2020, 12:36 PM

Your issue is that you are unable to save presets using these plugins, is that correct? Are you talking about saving presets within the plugin itself, or within Vegas in order to use with these plugins? If it's the latter, you must give each Vegas custom preset a unique name, which has always been the case, and is well documented.

Vegas' developers may not have any personal experience with this particular plugin, and a forum search will tell you better whether it's a "known issue." Does Cakewalk actually say their Lexicon plugins will work the way you want with Vegas?

Introducing all this peripheral stuff as a second response serves to shift one's attention from the original question. Try to stick with it until we are sure it is not PEBCAC, ok? Then, work with the plugin's developer.

To be certain, Vegas maintains no control whatsoever over what third party plugins are said to work with its versions, past or present. And there is certainly no implied obligation to save their "state." There is no registry folder to do that. Do you also expect Cakewalk to work the way you want with Vegas' proprietary VST plugins? Best of luck.

JimHWiltshire wrote on 8/6/2020, 12:55 PM

Thanks a lot for trying to help. It's nothing really obvious as far as I can see (as a pro with 25 years of experience) and simply appears to be an issue with the Lexicon reverbs (with my present system, at least). I can neither save or restore presets from within the plugin, or simply save the state of the plugins within a Vegas session automatically, as it always has done in previous incarnations. I don't think it's unreasonable of me to speculate as to whether the developers of Vegas have encountered this before, or can shed any light on it. I'm not pinning the blame on anyone or anything, just putting it out there to see (and I have seen some mentions of it elsewhere online) in case anyone has a solution I'm overlooking. I'm contacting Lexicon to see if they've heard of it happening before.

Musicvid wrote on 8/6/2020, 1:34 PM

Have you tried saving the plugin parameters the way you want them in Cakewalk?

JimHWiltshire wrote on 8/6/2020, 4:17 PM

I use Cubase - but, yes, they work properly in Cubase. In all honesty, I haven't encountered an issue like this with any of my (many hundreds) of plugins since the days of Vegas/Sound Forge and Sonic Foundry/Sony in the 90s (I've been using these packages that long!) - so I really doubt it's anything obvious I'm missing here with regards to how to use and set up plug-ins, as an experienced user. And Lexicon Plug-ins are some of the best. There's a bug of some sort, I think (could be with the plug-in, vegas or anything, I know) but I'm just trying to determine where and with what, and I thought perhaps someone else here may have experienced this issue or may be able to replicate it if they use PCM Native Reverb in Vegas 17/18. For instance: there's a known issue with Altiverb and Vegas, which necessitates running Vegas as an administrator for it to work properly... so I wondered a similar issue may be occurring here with a similarly easy solution.