DSP Robotics Support

I understand the mechanism behind your method, Adam. Seems like This is quite similar to what I've done (although I didn't understand how you exactly saved the cc parameters. Have you built a giant string array connected to a "save text" primitive? you used the preset system to make it an integral part of preset like trog did?). My problem was routing out all these strings to the schematic's upper stage since many of my buttons and knobs were located in a way deeper stages (sometimes 5th or 6th stage). This method requires a decent schematic architecture pre-planing (separating graphics and locating them on upper stage) or the pain remains. With the additional preset manager, the bi-directional data transfer of the "P" link makes all the hard work for you with no special need to pre-plan the schematic's architecture.

Yes all the knobs send out their string via wireless to a master array combiner. If the knobs are in a deeper layerI just bring it out with direct link and do a wireless when I reach the layer where I can.

Don't you prefer the "P" link method that saves all this mess of pulling the strings out?

No. This is how Sylenth1, Spire, and lot of other synths do it. This information should not be in a preset but a global settings. So lets say you have a midi keyboard and you assign the cutoff to a midi knob. That should be set forever regardless of preset. Now if you store this as a preset and change presets it could change and you have to assign it again. Thats a bad way of doing it.

Well, as I wrote to trog, I'm not storing it as a preset, but as a text bank. That means that the settings stay for ever until you load a different text bank. The results: the additional preset manager acts exactly as an array builder connected to a "save text" primitive, but with bi-directional communication thanks to the "P" link...