Someone reported that Bitwig and Reaper immediately call plugin_latency->get after host_latency->changed gets called from the plugin during activation
solution: allow plugin_latency->get to be called already during plugin->activate
I think it does not make sense if host_latency->changed is called before activate.
solution: require host_latency->changed to be called only during plugin->activate
open question: should it be mandatory for the plugin to call host_latency->changed during activate after setting up its latency internally? (How do existing hosts handle the case that plugins do not call host_latency->changed during activation? Maybe you can tell how Bitwig handles it, @abique?)
Not sure whether the term being-activated is optimal. If you have better suggestions, please feel free to change it or suggest something else.
abique
commented
1 month ago
proposal after some discussion on Dischord.
plugin_latency->getafterhost_latency->changedgets called from the plugin during activationplugin_latency->getto be called already duringplugin->activatehost_latency->changedis called beforeactivate.host_latency->changedto be called only duringplugin->activatehost_latency->changedduringactivateafter setting up its latency internally? (How do existing hosts handle the case that plugins do not callhost_latency->changedduring activation? Maybe you can tell how Bitwig handles it, @abique?)Not sure whether the term
being-activatedis optimal. If you have better suggestions, please feel free to change it or suggest something else.