Posted: 15 Feb 2015, 21:45
So I have a discussion in the forum or question regarding the best way to manage or control sub-patch inlets and outlets.
In many cases I can control a specific Data In/Out and their position vertically determines the order on the parent.
The only problem is that Knobs, Faders, Text, etc... also will default to show themselves as nodes on the parent patch.
If I try to control via the Data In/Out it results in duplicate nodes.
With this.... the order becomes skewed, confusing, and hard to manage.
Thinking a little about this, I think it would be best to apply a control.
To manage the knobs and faders, and backward compatibility it might be a good idea to include an input/output Termination. If the termination is applied to a Knob or Fader, then the Knob or fader will not be displayed as a node on the parent patch.
With this termination, one could rely solely on using Data In/Out methods to create and organize their sub-patches.
-S
In many cases I can control a specific Data In/Out and their position vertically determines the order on the parent.
The only problem is that Knobs, Faders, Text, etc... also will default to show themselves as nodes on the parent patch.
If I try to control via the Data In/Out it results in duplicate nodes.
With this.... the order becomes skewed, confusing, and hard to manage.
Thinking a little about this, I think it would be best to apply a control.
To manage the knobs and faders, and backward compatibility it might be a good idea to include an input/output Termination. If the termination is applied to a Knob or Fader, then the Knob or fader will not be displayed as a node on the parent patch.
With this termination, one could rely solely on using Data In/Out methods to create and organize their sub-patches.
-S