Tweaking plugin presets overwrites preset - Vegas Pro 14 - Win7

thistof wrote on 1/29/2022, 2:19 PM

Like the title says, I'm starting with a preset on an audio effect, and it turns out that every tweak I do it overwrites the old preset. So if I don't like what I'm doing and I want to go back to the original preset to start tweaking over again from that point, well too bad because it's been overwritten with my tweaks. This happens when tweaking my own presets, or using the default presets that come with the plugins, and is true for the built in Vegas plugins, as well as third party VST plugins. This didn't used to be the case in older versions of Vegas, but I've noticed it in 14 for a long time, and I've finally gotten frustrated enough to ask. What can I do to prevent this strange behaviour which really should not be the default behaviour, and didn't used to be.

Comments

rraud wrote on 1/29/2022, 5:42 PM

Save the original plug-in chain you like as a preset so you can go back to It. Open the plug-in chooser and select 'Save as'. If you like Fx changes you make, you can update the chain by clicking the 'save' icon in the plug-in chooser, or 'save as' again using a new or appended name Saving a .veg file will save the plug-ins' changes but it will not update the named preset.
Automation envelopes however are saved in the .veg project file, not in the chain's preset You can also create an individual presets for specific plug-in to use it singularly or add to an existing chain

thistof wrote on 1/30/2022, 9:04 PM

Well, it doesn't get the old default presets back, nor does it solve the problem. I'll try to remember to do that every time I get a new plugin.

gary-rebholz wrote on 1/31/2022, 2:48 PM

@thistof, Nothing should have changed here since...forever. I can't find a way to repro what you're seeing. In fact, you shouldn't even be able to save changes to a built-in plug-in preset. I'm not saying you're not seeing what you see. Just that I can't see it. Can you provide a detailed step-by-step repro of the issue?

thistof wrote on 1/31/2022, 5:48 PM

I can't remember which plugins I've run into this problem in the past, I tried a few at random, and it seems to be the VST plugins that I'm having an issue with. I'll use bitspeek as an example, this is the one I was dealing with when I started this thread the other day.

I'll select the preset called "mice backup" which I don't care about. I tweak a couple parameters, but don't save it. Then I go to another preset, then back to the mice backup preset. The parameters are where I tweaked them, not where the original preset had them. The other day I started tweaking one of the default presets, and after a couple minutes, I noticed that it had even renamed itself to "default" giving me two presets called "default." I've had similar issues with other plugins as well. Now let's say I want to save "mice backup" as "robot voice" once I tweak it to sound how I like. If I rename it, it doesn't save the name change automatically, even though it somehow saved one of the previous entries as "default" when I hadn't even touched the name. Yet it still saves the tweaks.

So I want to save my new setting, and it gives me the options to save the entire bank as fxb or fxp (kind of annoying, but maybe that's the limitation of vst) and then if I want to load the entire bank, I can reload the entire bank. But the bottom line is, that merely tweaking a setting should not automatically overwrite the default fxb, leaving me no way to return to the original presets if I didn't happen to have backed them up

rraud wrote on 2/1/2022, 9:16 AM

but maybe that's the limitation of vst)

Maybe a VP/Win 7 issue. Otherwise VST presets do not overwrite themselves without user input. Do all your VST plug-ins overwrite user presets? As I stated, it is normal for the plug-in parameters to be changed along with the VEG project file, but the original saved chain or FX preset can be recalled .

Contact Vegas tech support

 

thistof wrote on 2/1/2022, 2:32 PM

Thanks rraud, yeah seems to be all my VST plugins, and doesn't seem to be per VEG project. I tweaked one in one project and it affected the same plugin in another project.

Thanks for the input guys, I did open a support ticket.