This is quite hot topic and it seems we have lost the original post about this.
So, long story short: When we are rolling out new updates for plug-ins which may affect the plug-in backward compatibility, it is important to backup your project and make sure it will work with the new plug-in update.
We know, we know, it is a pain in the you know where, but it is something we can not do a thing about. The deal is: when we add new significant functions, we also have to add the parameters to work with it. These new parameters mess up the total recall data (until we create a new way for it), therefore making the plug-in non-backward compatible.
To ensure your project works after plug-in update, do these steps BEFORE running the update installer:
- Open your project with the old plug-in still in it.
- Let the total recall do its thing and send the data to your hardware.
- Store the song data in your hardware.
- Take a screenshot of your automation lanes.
- Save the project under a new name and close it!
- Run the update installer.
Once these steps are completed, you can then open the old or new project and see if the automation is still there. Also, total recall might not work as expected, so I recommend to load the patch data in your hardware and then sync the data in the plug-in UI. Save the new or old project and you are good to go again!
If you have any questions, please post them below or in the forums and I will do my best to help you out.