What problem(s) would this feature resolve?
When plugins are missing from the expected path of the project file, regardless if the plugin can be loaded from an alternate path, the plugin patch information saved in the project cannot be restored.
This issue primarily distrupts the resolution of projects being shared between systems/users or when revisiting older projects where plugin paths or versions no longer match.
The “save vst3 patch to project folder” feature is very helpful, however is still expects vst path to be the same as when saved.
How does this feature fit in Bitwig as a product?
The presets/patch library feature in Bitwig is a preferred way to manage and maintain portability in the production workflow. Without being able to adjust the plugin path or find, as with missing samples, it remains unreliable for maintainence of VST depended projects, with respects to project portability.
Is there already an alternative way to achieve this on Bitwig?
The workaround is to save patches/presets from with a respective plugins patch manager and handle the presets separately outside of Bitwig.
Could it be implemented using Bitwig components or APIs, without Bitwig team’s support?
I do not believe so