I noticed that the automation information are lost when exporting a bitwig project to the dawproject format when the plugin is missing from the library (I only tested this with vst3).
Steps to reproduce
Create a bitwig project with a vst3 plugin and add an automation on one of its parameter. Save the project
Uninstall the vst3 plugin.
Open the previous bitwig project. Notice the automation curve is still there. Export it to dawproject format.
Open the exported dawproject in bitwig. Notice the automation curve is gone.
Is this a limitation to how bitwig project and dawproject represent automation?
My best guess is that bitwig is unable to access the parameter id when the plugin is missing and thus is unable to export the automation data to dawproject because the dawproject file format requires the automation to point to the parameter id of the plugin.
I noticed that the automation information are lost when exporting a bitwig project to the dawproject format when the plugin is missing from the library (I only tested this with vst3).
Steps to reproduce
Is this a limitation to how bitwig project and dawproject represent automation? My best guess is that bitwig is unable to access the parameter id when the plugin is missing and thus is unable to export the automation data to dawproject because the dawproject file format requires the automation to point to the parameter id of the plugin.