If we use LGPL code inside our plugins we must link dynamically to avoid licensing issues, but reading from FreeAudio Clap plugins the developer used Qt framework for the UI but had to run it from a separate process which was neat since if the gui crashed the plugin would stay alive. But is this specifically for GUI libraries such as qt or do we have to create sub processes for each dll we use. Say if our plugin was a host hosting other plugins.
Code:
https://github.com/free-audio/clap-plugins1. has the advantage of being simple to deploy. 2. is more complex due to its inter-process nature. It has a few advantages: if the GUI crash, the audio engine does not the GUI can use any libraries, won't be subject to symbol or library clash etc...We abstracted the relation between the plugin and the GUI: AbstractGui and AbstractGuiListener which lets us transparently insert proxies to support the remote model.Statistics: Posted by Marvinh — Sun May 19, 2024 3:51 am