It would be great if plugin devs had the ability to feature integrated cross plugin routing for certain work tasks.
My use case is setting up complex side-chain sends with the key source coming from within a certain point in a channels insert chain - specifically, the ability to send a plugins delta as a key source (if the dev were to incorporate such a feature, which some have told me they would maybe if they could)
The work around is to duplicate a channel and use it as the key source.
The other development solution, is if Cubase gave us customization with exactly where our send starts in a channels topology.
A send that is customized this way would be highlighted a different colour.
Also, being able to have sends Pre-Insert could be useful in certain instances, instead of only Post-Insert/Pre-Fader or Post-Insert/Post-Fader
Although this second proposed solution still doesn’t accomplish being able to send a plugins Delta to somewhere else/another instance of the same plugins.
Thank you for mentioning our plug-in. Connector actually has an “App” mode that does not use the network at all, it’s all local in the app’s own memory.
I wouldn’t worry too much about that. Inter plugin communication has been done for years by e.g. Izotope or Sonible (or Blue cat) and whether they use local networking or some sorts of shared memory between threads, that is all being done by standard APIs of the operating system that are highly unlikely to “break”, because that would mean that nearly all other applications would stop working, too.
Each method has it’s potential drawbacks that a developer has to consider (e.g. if a DAW uses plugin sandboxing) but I would fully trust Blue Cat to know how to correctly implement it.