Skelm Posted October 18 Share Posted October 18 Hi, I bought a new PC as my previous PC did not support the Windows 11 hardware requirements. Everything appeared to be going well, until I noticed while testing that some envelopes were not automating the expected parameters. Volume and send envelopes seem unaffected, but many envelopes assigned to plugin parameters appear to have lost their assignments. The envelopes are still there but dropping down the edit filter doesn't bring up the associated parameter, so the envelopes cannot be brought into focus, or re-assigned and obviously the automation doesn't happen. This hasn't happened on every plugin but so far the Arturia Mini Filter and the Valhalla plugins have lost their assignments. This is quite an issue, as I tend to automate a lot, and there are dozens of tracks affected. Hopefully someone has a suggestion or workaround, I would appreciate it. Thanks. Link to comment Share on other sites More sharing options...
Skelm Posted October 18 Author Share Posted October 18 I am wondering if this may be a version issue. Is it possible to download an older version of the installer so I can test this? My previous PC was on version 2022-11. Thanks. Link to comment Share on other sites More sharing options...
Max Arwood Posted October 19 Share Posted October 19 I’m wondering do you have all the plugins installed and activated? Do they show up in the plugin manager? Link to comment Share on other sites More sharing options...
msmcleod Posted October 19 Share Posted October 19 18 hours ago, Skelm said: I am wondering if this may be a version issue. Is it possible to download an older version of the installer so I can test this? My previous PC was on version 2022-11. Thanks. I think it's more likely to be a plugin version issue than a Cakewalk version issue, especially if the plugin went through several upgrades from an earlier version on your previous machine. Link to comment Share on other sites More sharing options...
Skelm Posted October 19 Author Share Posted October 19 Thanks for the responses - after some hair-pulling, I found the issue. The VST2 - VST3 switch to "replace if possible on project load" was on, and the problem plugins had all loaded the VST3 version and subsequently lost their envelope assignments. Switching that off loaded the VST2 versions as before, and the automation assignments back to where they were. Ideally, losing these assignments should force the project to continue using the VST2 version, as there is no warning that the replacement is not like-for-like, and it is not immediately obvious that the automation is no longer working (in my case, anyway). 3 Link to comment Share on other sites More sharing options...
msmcleod Posted October 19 Share Posted October 19 2 minutes ago, Skelm said: Thanks for the responses - after some hair-pulling, I found the issue. The VST2 - VST3 switch to "replace if possible on project load" was on, and the problem plugins had all loaded the VST3 version and subsequently lost their envelope assignments. Switching that off loaded the VST2 versions as before, and the automation assignments back to where they were. Ideally, losing these assignments should force the project to continue using the VST2 version, as there is no warning that the replacement is not like-for-like, and it is not immediately obvious that the automation is no longer working (in my case, anyway). Glad you sorted the issue. What plugin manufacturers should be doing if possible, is ensuring their automation parameters match between VST2/VST3 - I guess this isn't the case for some of your plugins, which is likely the reason it didn't work. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now