Updating Vital correctly, without breaking older projects?

Questions and Support
#1

Hello!

I was in a spree of finding new presets for Vital the past few days and I realized a lot of them are for newer versions. I’ve been stuck with 1.0.7 for some time and was a bit afraid to update, one of the main reasons being that I forgot the first account I used for it and I need to change it somehow, and the second reason being that something can go really wrong, especially with older projects.

I’ve heard people complain that newer versions are detected as another plugin, and when opening projects it will just display the midi information without the actual plugin opening.

So how did you guys manage to update it with as few problems as possible?

And also, is there an issue if I make a newer account that I can use for Vital?

Basically, how can I update Vital to the newest version and with a new email without breaking the plugin or older projects I used it on?

Thanks!

#2

to be on the safe side i would archive your old presets, label them for your old version of vital, and freeze/bounce your vital tracks. One thing that might be easy to forget is you also need to open each project, manually create any patches that are stored in your daw project file because those presets are stored in your project file, not in vital. I don’t know of a better way to handle versioning of software that isn’t backward compatible.

#3

Thanks! Yeah, I guess this would indeed be the safest bet. But to be honest, that’s gonna be incredibly tedious…