Differences

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

--- ai:customising_modules [2018/10/14 17:47] – [Basic Patch Menu] icke_siegen
+++ ai:customising_modules [2018/12/18 11:25] (current) – external edit 127.0.0.1
@@ Line 10: / Line 10: @@
   * ''Insert Empty Patch'' adds an empty patch, represented by a small grey rectangle. Doubble-click it to open it, or to 'fly' down into it.
   * ''Insert Patch File'' opens a file explorer in order to navigate to another patchfile which can be inserted here
-  * ''Insert Patch IO'' (subpatches only) inserts the module [[ai:modules:patch_patch_io|]] which allows to route ports between patches.
+  * ''Insert Patch IO'' (subpatches only) inserts the module [[ai:modules:patch:patch_io]] which allows to route ports between patches.
   * ''Hide All Connections'' hides all already patched 'wires'. This is useful for patches with many connections. Even with the connections hidden, hovering the mouse over a port temporarily shows its connection(s).
   * ''Show All Connections'' makes all connections visible again.
@@ Line 23: / Line 23: @@
   * In order to select a group of modules/patches, draw a selection box around them (click in one corner, hold the mouse button, move diagonally for a reactangle, release mouse button)
   * In order to move the entire viewport of the patch window hold the spacebar pressed and drag the contents with the mouse, or - with nothing selected - repeatedly hit the arrow keys (up/down/left/right)
+  * ''Ctrl'' + ''A'' selects all items in this window
+  * ''Ctrl'' + ''D'' deselects all items
+  * ''Ctrl'' + ''G'' groups selected items into a subpatch, see [[#subpatches]] for details
 ==== Move ====
@@ Line 102: / Line 104: @@
 ===== Subpatches =====
-Patches can be nested - a patch can contain any number of modules and other patches, which in turn may contain other modules and patches, and so forth. (I think I already made patches with 4 or 5 layers of nested patches). In such situations you need a way to route signals (ports) and commands (controls/parameters) from one patch to another. Of course Ai offers a neat way for this: Patch IO.
+Patches can be nested - a patch can contain any number of modules and other patches, which in turn may contain other modules and patches, and so forth. (I think I already made patches with 4 or 5 layers of nested patches). In such situations you need a way to route signals (ports) and commands (controls/parameters) from one patch to another. Of course Ai offers a neat way for this: [[ai:modules:patch:patch_io|Patch IO]].
   * in the subpatch, insert ONE Patch IO module (each patch can contain only one such module). You can do this by right-click, ''Insert Module'', selecting it from the Patch section, or by right-click, ''Insert Patch IO''
   * if you need to patch one port to the parent patch simply start to patch this port and drop the other end onto the Patch IO module. The port will immediately appear on the rectangle representing this patch in the parent patch. From there, you may patch as usual.
@@ Line 108: / Line 110: @@
   * in order to make controls (faders, buttons, dropdown lists, text areas etc.) available on the surface of this patch/in the parent patch, right-click the control and select ''Add to Parent Panel'' whereupon the control will magically appear on the rectangle representing the patch in the parent patch.
+There is a quick way to group modules and patches into a subpatch: ''Ctrl'' + ''G'' does this for you, and even adds a Patch IO and wires it if needed. Thus, simply select the modules and patches you want to be moved into a subpatch, and hit ''Ctrl'' + ''G''.