Unify Manual

Your complete reference to PlugInGuru's creative playground!

User Tools

Site Tools


combobox

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
combobox [2020/11/09 16:04] – [User interface basics] shanecombobox [2024/03/09 19:33] (current) – [User interface basics] shane
Line 27: Line 27:
  
 {{::combobox-1.png?600|}} {{::combobox-1.png?600|}}
- 
-Work in progress... TO BE CONTINUED... 
  
   * Right-click in background area to add new plug-in instance nodes   * Right-click in background area to add new plug-in instance nodes
 +    * A "quick select" dialog will appear, allowing you to select any type of plug-in from the Known Plug-Ins list.
 +    * Hold down ALT (Option on Mac) if you prefer the older cascading-menus method.
     * Unify assigns node-names automatically by adding "1", "2", "3", etc. to the plug-in name     * Unify assigns node-names automatically by adding "1", "2", "3", etc. to the plug-in name
   * Double-click in any plug-in node to open that plug-in's GUI in a separate window   * Double-click in any plug-in node to open that plug-in's GUI in a separate window
Line 42: Line 42:
     * You can also connect several outputs to one input; this is called a **merge**. Merging MIDI streams yields one combined MIDI stream. Merging two or more audio streams is basically the same as //mixing// them; the audio samples are simply summed.     * You can also connect several outputs to one input; this is called a **merge**. Merging MIDI streams yields one combined MIDI stream. Merging two or more audio streams is basically the same as //mixing// them; the audio samples are simply summed.
  
 +===== Using ComboBox vs. Layers =====
 +Unify's layer system provides another way to combine and connect multiple plug-ins, so what does //ComboBox// offer that Layers do not (or vice versa)?
 +  * The main **advantage** of //ComboBox// is that it allows you to connect groups of plug-ins in arbitrary ways, as opposed to the strict stereo-only "daisy chaining" allowed by Layers.
 +  * The main **drawback** of //ComboBox// is that, because //ComboBox// is itself a single plug-in, all plug-in instances inside a //ComboBox// are executed by only one CPU core at a time. Parallel Layers, in contrast, can run simultaneously using multiple CPU cores.
 +
 +===== ComboBox and Linked Parameters =====
 +//ComboBox// exposes all parameters of all embedded plug-in instances for linking to Unify's [[realtime-params|Macro Knobs]]. The link paths are constructed in a simple way, best illustrated with an example. Using the mono vocoder graph shown in the first image above, you could select, say, the //Hi Thru// parameter of the //mda Vocoder 1// plug-in like this:
 +
 +{{::combobox-2.png|}}
 +
 +The resulting parameter path would look like this:
  
-===== Headline =====+{{::combobox-3.png|}}
  
-===== Headline =====+**Note:** If you delete plug-in nodes from a //ComboBox// graph, any parameter links to that node will become invalid (they will display in red instead of green).
  
combobox.1604937848.txt.gz · Last modified: 2023/05/08 18:59 (external edit)