First I want to thank you for your patience and help in this issue. I am currently working with support but in case anyone reading the forum is curious later down the road, the issue is partially resolved.
The new registration seems to take, and persist between saves, but whenever an older project that used Kick 2 is loaded initially, the Kick 2 starts in evaluation mode. I can delete the plugin, add it back, and it starts as registered, and I need to re-select the preset I used. It then seems to operate normally until the next time I re-load the project.
A brand new project seems to work fine. I can start a new one, add Kick 2, select my preset, save, close, and re-open that new project, which all works normally, so the current state of the issue seems to only be affecting my projects which were made before the issue started.
As mentioned, support has been great so far once we got in contact and progress is being made, so I will post updates as things move along.
Thanks for the kind words and no worries, Iām glad if that could help and yes, itās nice for others members to keep the forumās topics up to date when you get something sorted out thanks to the support team, good community behavior ! Thanks
My take on this is that it might also come from the way Live handles projects saving and the data being written in Abletonās project files. Many times if you open a Live Project done with an older version of the DAW, it will ask you to convert it or warn you about compatibility issue. Another example is opening a previous project using older Liveās native plugins ( i.e : the older version of āUtilityā ), you will see an āUpgradeā button displayed on the plugin if you are using the new version.
Removing the older instance of the plugin and replacing it with the new one and saving again your Live Project will solve this most of the time, so IMO, itās a good habit to have with Ableton Projects across versioning anyway
