VST patch reset impossible

[fluffy_little_something]

I have noticed that behavior many times, and I don't know whether or not it is intentional, but in my view it is unfortunate:
When I make a custom patch by modifying an existing patch (for instance from the factory patch drop-down menu) in a synth or effect plugin, the instance does not forget my changes when I want them to be forgotten. So I can't reset the patch to the existing patch (oftentimes the init patch) anymore. I have to load a new instance.

Is that a DAW issue or a VST issue?

[MuTools]

Whether you can "revert" your changes to the loaded VST program depends on the VST. You have to check the VST's menus whether that functionality is there. You could also reload the relevant program using the Open FXP button at the top of the editor.

[pljones]

Yes, it's VST-specific, I think. Pretty much you always have to remember to save the FXB or FXP before you start playing with them if you want to get back to them easily.

[fluffy_little_something]

Yes, it's VST-specific, I think. Pretty much you always have to remember to save the FXB or FXP before you start playing with them if you want to get back to them easily.

Well, factory presets are just there without my saving them. I think it would make more sense if a factory preset were reset whenever I reload it from the patch list, no matter whether or not I have changed it the last time I loaded it. But somehow the modified factory preset seems to remain in the memory, unfortunately, instead of being deleted from the memory whenever I load any other patch (including the same factory preset).

Remaining in the memory only makes sense with those few plugins that have a compare feature, Waves stuff for instance.

[pljones]

It's the VST's memory. If you need to reload it, you need somewhere to reload it from, so you need to take a copy of the factory values if the VST does not give you a way to restore them itself.

[fluffy_little_something]

Interestingly, if I load one of my own patches and modify it, and then reload it again, it is reset and the modifications are lost.

[pljones]

Sorry, that's too vague. Could you explain in more detail, please?

[Michael L]

It would be good if you would say what the VST is, and all the steps you are following. It sounds like you may not be saving your patch properly according to the procedures for that VST (some are quite particular about names or file structure). You also might find it more helpful to discuss it with other users of that VST.

[fluffy_little_something]

There was nothing vague at all. I already have described exactly what I am doing.
It is not about my saving anything, as was obvious from my description.

I only use Sylenth1 and Toneboosters effects, all of which display that behavior. But I remember that behavior from other plugins in the past as well, which made me wonder if it is a DAW or a VST issue.

[pljones]

So you're not after anyone's help with anything, then? OK, good to hear you've got it sorted out.

[fluffy_little_something]

So you're not after anyone's help with anything, then? OK, good to hear you've got it sorted out.

I haven't sorted anything out, it simply continues to suck the way it is...

Basically, I was wondering whose fault it is, the DAW's or the plugins'...

[Michael L]

There is a third variable....

[fluffy_little_something]

There is a third variable....

Certainly not me
Checked Air's Hybrid 3 meanwhile, there modified factory presets are reset to their original status when reloaded