To developers: possible BUG in Cakewalk!
VSTi track automation data is linked relative to plugin .dll including its installation path, instead of relative to the plugin .dll itself. Why?
I discovered this during my problem described in this thread about orphaned automation envelopes.
Problem NOT solved even though project is saved as Cakewalk Bundle .cwb file.
Cakewalk PLEASE solve this, otherwise it will not be possible to do collaboration work on project files on different computers, unless the project receiving comput
It is not linked to the plugin dll and certainly not the install path. However there are some caveats with VST2 plugins. see below.
Plugins are assigned a 128 bit UUID when scanned which is used for all operations including loading plugins as well as automation.
For VST2 plugins the UUID is derived from the manufacturer assigned plugin ID as well as the plugin name (because ID's are not guaranteed to be unique). This is the legacy method used only for VST2. VST3 plugins already have uniqu
