Reply To: Auto Device mapping problems

I realised that newer version VSTs, just ’cause I either relocate the file in the VST device or just replace the existing file, may have altered innards that are not reimported into Podium

This is a major problem for me.
I don’t know if we speak about the same thing, but I have asked some years ago a “rescan mapping” or “rebuild mapping” of plugins or something like this.

In every host, when there is an update in a plugin that has changed the internal parameters names or order for example, the host says “some parameters could not be load”. But it loads the plugin and updates what exists.
The only risk is that some automations perhaps goes wrong or are linked to another parameter.
But it is your problem to correct it.

On the other hand, Podium simply ignores the changes, the old mapping remains, even if it doesn’t work anymore, and new parameters for example are not available.
The only way we have is to delete the plugin and reimport it. Of course, all the settings and automations are completely lost, and we have to insert it manually in all tracks were the previous version was.

I agree that in normal circumstancies it must not be a problem, and if the update is important editors generally give an independant plugin version.
It is a big problem for me because I have to modify my plugins very often, and when this occurs I lost everything…
Happily, I limit the use of plugins in Podium and do all the hard work in other hosts, but it is something that could be certainly improved.

Perhaps I am wrong and is there now a way for updating the parameters without having to delete the plugins ?