<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://aumhaa.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Okyeron</id>
	<title>ModWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://aumhaa.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Okyeron"/>
	<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Special:Contributions/Okyeron"/>
	<updated>2026-04-20T11:52:30Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.31.1</generator>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Binary&amp;diff=710</id>
		<title>Binary</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Binary&amp;diff=710"/>
		<updated>2012-12-06T09:01:22Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Video Tutorial */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Video Tutorial ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=an0dz5PD7ho&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=1&amp;amp;feature=plcp  Binary Tutorial with Code and Ohm]&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:Binary_pick.png]]&lt;br /&gt;
&lt;br /&gt;
Binary for Monomodular.&lt;br /&gt;
&lt;br /&gt;
Binary is a variable speed programmable sequencer originally built for use with Livid&amp;#039;s Code.  It grew out of early experimentations with the Code and some lofty ideas.  You can expect some future changes.&lt;br /&gt;
&lt;br /&gt;
Its best to watch the video tutorial in order to figure out what&amp;#039;s going on, but here is a list of the basic controls:&lt;br /&gt;
&lt;br /&gt;
Code.&lt;br /&gt;
&lt;br /&gt;
Each dial contains a variable length/speed sequence.  Select a sequence by pressing the dial, and the white LED below it will light.&lt;br /&gt;
&lt;br /&gt;
The 8 steps nearest to the playhead (left) are shown on the bottom buttons.  Active steps are lit.  You can assign steps by pressing buttons.  You can scrub the playhead by pushing the selected dial and turning it.  You can change the speed of the sequence by turning the dial.  The current position of each sequence is always indicated by it&amp;#039;s dial&amp;#039;s LED strip.&lt;br /&gt;
&lt;br /&gt;
By pushing and holding a dial, then pushing another dial, you may lock the second sequence&amp;#039;s speed to the first&amp;#039;s.&lt;br /&gt;
&lt;br /&gt;
The active status of each sequence is indicated by the green light on the dial&amp;#039;s LED strip.  You can change its active status by pressing the top right button while the sequence is selected.&lt;br /&gt;
&lt;br /&gt;
Additionally, the second button on the right changes whether the selected sequence is quantized.  Quantize state is displayed by whether a selected sequence&amp;#039;s white LED is blinking (quantized) or solid (free).&lt;br /&gt;
&lt;br /&gt;
The third button on the right changes the sensitivity of the dials.&lt;br /&gt;
&lt;br /&gt;
The fourth button on the right converts the bottom row of dials to mirror the plugin GUI controls (also available via Live Device).&lt;br /&gt;
&lt;br /&gt;
Grid.&lt;br /&gt;
&lt;br /&gt;
The Grid has five modes, used for programming the sequences or playing them back.  Each sequence can be up to 64 steps in length, and each step can contain up to 8 simultaneous notes, can be turned on or off, and has independent velocity (but all notes played in that step share a common velocity).&lt;br /&gt;
&lt;br /&gt;
The Keys are the same for both Grid and Codec (Keys are shift-bottom row buttons on Codec):&lt;br /&gt;
&lt;br /&gt;
1 - Step Mode.  (turn steps on or off)&lt;br /&gt;
2 - Length Mode.  (1 - 64 steps)&lt;br /&gt;
3 - Note Mode.  (turn notes on or off)&lt;br /&gt;
4 - Velocity Mode.  (change velocity of each step)&lt;br /&gt;
5 - Active Mode. (turn activity on or off)&lt;br /&gt;
6 - Toggle Play Mode. (press and hold vs. toggle for Active Mode, and while &amp;#039;Play Mode&amp;#039; is on, pressing a dial is momentary active instead of selection;  also turns off ability to change speed by turning a the sequence&amp;#039;s dial)&lt;br /&gt;
7 - Hold to select sequence (selected lit on grid, flashing if locked)&lt;br /&gt;
8 - Toggle selected sequence&amp;#039;s quantize status.&lt;br /&gt;
&lt;br /&gt;
In addition, you may store and recall up to 32 presets by pressing ALT on the Grid.&lt;br /&gt;
&lt;br /&gt;
This plugin is very useful as a timing engine for other Mod plugs, and has been tailored for this purpose.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Binary&amp;diff=709</id>
		<title>Binary</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Binary&amp;diff=709"/>
		<updated>2012-12-06T08:59:13Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Video Tutorial ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=an0dz5PD7ho&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=1&amp;amp;feature=plcp b992 Binary Tutorial with Code and Ohm]&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:Binary_pick.png]]&lt;br /&gt;
&lt;br /&gt;
Binary for Monomodular.&lt;br /&gt;
&lt;br /&gt;
Binary is a variable speed programmable sequencer originally built for use with Livid&amp;#039;s Code.  It grew out of early experimentations with the Code and some lofty ideas.  You can expect some future changes.&lt;br /&gt;
&lt;br /&gt;
Its best to watch the video tutorial in order to figure out what&amp;#039;s going on, but here is a list of the basic controls:&lt;br /&gt;
&lt;br /&gt;
Code.&lt;br /&gt;
&lt;br /&gt;
Each dial contains a variable length/speed sequence.  Select a sequence by pressing the dial, and the white LED below it will light.&lt;br /&gt;
&lt;br /&gt;
The 8 steps nearest to the playhead (left) are shown on the bottom buttons.  Active steps are lit.  You can assign steps by pressing buttons.  You can scrub the playhead by pushing the selected dial and turning it.  You can change the speed of the sequence by turning the dial.  The current position of each sequence is always indicated by it&amp;#039;s dial&amp;#039;s LED strip.&lt;br /&gt;
&lt;br /&gt;
By pushing and holding a dial, then pushing another dial, you may lock the second sequence&amp;#039;s speed to the first&amp;#039;s.&lt;br /&gt;
&lt;br /&gt;
The active status of each sequence is indicated by the green light on the dial&amp;#039;s LED strip.  You can change its active status by pressing the top right button while the sequence is selected.&lt;br /&gt;
&lt;br /&gt;
Additionally, the second button on the right changes whether the selected sequence is quantized.  Quantize state is displayed by whether a selected sequence&amp;#039;s white LED is blinking (quantized) or solid (free).&lt;br /&gt;
&lt;br /&gt;
The third button on the right changes the sensitivity of the dials.&lt;br /&gt;
&lt;br /&gt;
The fourth button on the right converts the bottom row of dials to mirror the plugin GUI controls (also available via Live Device).&lt;br /&gt;
&lt;br /&gt;
Grid.&lt;br /&gt;
&lt;br /&gt;
The Grid has five modes, used for programming the sequences or playing them back.  Each sequence can be up to 64 steps in length, and each step can contain up to 8 simultaneous notes, can be turned on or off, and has independent velocity (but all notes played in that step share a common velocity).&lt;br /&gt;
&lt;br /&gt;
The Keys are the same for both Grid and Codec (Keys are shift-bottom row buttons on Codec):&lt;br /&gt;
&lt;br /&gt;
1 - Step Mode.  (turn steps on or off)&lt;br /&gt;
2 - Length Mode.  (1 - 64 steps)&lt;br /&gt;
3 - Note Mode.  (turn notes on or off)&lt;br /&gt;
4 - Velocity Mode.  (change velocity of each step)&lt;br /&gt;
5 - Active Mode. (turn activity on or off)&lt;br /&gt;
6 - Toggle Play Mode. (press and hold vs. toggle for Active Mode, and while &amp;#039;Play Mode&amp;#039; is on, pressing a dial is momentary active instead of selection;  also turns off ability to change speed by turning a the sequence&amp;#039;s dial)&lt;br /&gt;
7 - Hold to select sequence (selected lit on grid, flashing if locked)&lt;br /&gt;
8 - Toggle selected sequence&amp;#039;s quantize status.&lt;br /&gt;
&lt;br /&gt;
In addition, you may store and recall up to 32 presets by pressing ALT on the Grid.&lt;br /&gt;
&lt;br /&gt;
This plugin is very useful as a timing engine for other Mod plugs, and has been tailored for this purpose.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Binary&amp;diff=708</id>
		<title>Binary</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Binary&amp;diff=708"/>
		<updated>2012-12-06T08:59:01Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Video Tutorial ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=an0dz5PD7ho&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=1&amp;amp;feature=plcp b992 Binary Tutorial with Code and Ohm]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:Binary_pick.png]]&lt;br /&gt;
&lt;br /&gt;
Binary for Monomodular.&lt;br /&gt;
&lt;br /&gt;
Binary is a variable speed programmable sequencer originally built for use with Livid&amp;#039;s Code.  It grew out of early experimentations with the Code and some lofty ideas.  You can expect some future changes.&lt;br /&gt;
&lt;br /&gt;
Its best to watch the video tutorial in order to figure out what&amp;#039;s going on, but here is a list of the basic controls:&lt;br /&gt;
&lt;br /&gt;
Code.&lt;br /&gt;
&lt;br /&gt;
Each dial contains a variable length/speed sequence.  Select a sequence by pressing the dial, and the white LED below it will light.&lt;br /&gt;
&lt;br /&gt;
The 8 steps nearest to the playhead (left) are shown on the bottom buttons.  Active steps are lit.  You can assign steps by pressing buttons.  You can scrub the playhead by pushing the selected dial and turning it.  You can change the speed of the sequence by turning the dial.  The current position of each sequence is always indicated by it&amp;#039;s dial&amp;#039;s LED strip.&lt;br /&gt;
&lt;br /&gt;
By pushing and holding a dial, then pushing another dial, you may lock the second sequence&amp;#039;s speed to the first&amp;#039;s.&lt;br /&gt;
&lt;br /&gt;
The active status of each sequence is indicated by the green light on the dial&amp;#039;s LED strip.  You can change its active status by pressing the top right button while the sequence is selected.&lt;br /&gt;
&lt;br /&gt;
Additionally, the second button on the right changes whether the selected sequence is quantized.  Quantize state is displayed by whether a selected sequence&amp;#039;s white LED is blinking (quantized) or solid (free).&lt;br /&gt;
&lt;br /&gt;
The third button on the right changes the sensitivity of the dials.&lt;br /&gt;
&lt;br /&gt;
The fourth button on the right converts the bottom row of dials to mirror the plugin GUI controls (also available via Live Device).&lt;br /&gt;
&lt;br /&gt;
Grid.&lt;br /&gt;
&lt;br /&gt;
The Grid has five modes, used for programming the sequences or playing them back.  Each sequence can be up to 64 steps in length, and each step can contain up to 8 simultaneous notes, can be turned on or off, and has independent velocity (but all notes played in that step share a common velocity).&lt;br /&gt;
&lt;br /&gt;
The Keys are the same for both Grid and Codec (Keys are shift-bottom row buttons on Codec):&lt;br /&gt;
&lt;br /&gt;
1 - Step Mode.  (turn steps on or off)&lt;br /&gt;
2 - Length Mode.  (1 - 64 steps)&lt;br /&gt;
3 - Note Mode.  (turn notes on or off)&lt;br /&gt;
4 - Velocity Mode.  (change velocity of each step)&lt;br /&gt;
5 - Active Mode. (turn activity on or off)&lt;br /&gt;
6 - Toggle Play Mode. (press and hold vs. toggle for Active Mode, and while &amp;#039;Play Mode&amp;#039; is on, pressing a dial is momentary active instead of selection;  also turns off ability to change speed by turning a the sequence&amp;#039;s dial)&lt;br /&gt;
7 - Hold to select sequence (selected lit on grid, flashing if locked)&lt;br /&gt;
8 - Toggle selected sequence&amp;#039;s quantize status.&lt;br /&gt;
&lt;br /&gt;
In addition, you may store and recall up to 32 presets by pressing ALT on the Grid.&lt;br /&gt;
&lt;br /&gt;
This plugin is very useful as a timing engine for other Mod plugs, and has been tailored for this purpose.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Grainstorm&amp;diff=707</id>
		<title>Grainstorm</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Grainstorm&amp;diff=707"/>
		<updated>2012-12-06T08:55:52Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Grainstorm_pic.png]]&lt;br /&gt;
&lt;br /&gt;
This is a quick port of Stretta&amp;#039;s Grainstorm for monome and arc over to the [[How to use the Codec script|Codec script]]....you can pretty much do everything with a single controller.&lt;br /&gt;
&lt;br /&gt;
The first four encoders on the right take the place of the arc 4.  You can choose the focused voice by the row buttons on the far right.  The bottom column buttons allow storing and recalling of presets for the focused voice.  &lt;br /&gt;
&lt;br /&gt;
Keys 1-4 allow copying of the current Maxloop buffers over to each Grainstorm voice (depending upon which one is focused).  Key 5 allows for access to some miscellaneous controls at the bottom of the patch window that wouldn&amp;#039;t fit easily.&lt;br /&gt;
&lt;br /&gt;
This patch shows some of the capabilities of the Codec script off, as well as some possibilities of the new &amp;#039;hotline&amp;#039; functions built into the b993 mod script.  This is how it is able to connect to the loopmaster and send its buffer&amp;#039;s name, which loopmaster then forwards to the appropriate Maxloop patch with instructions to fill the buffer with the Maxloop&amp;#039;s current loop buffer.&lt;br /&gt;
&lt;br /&gt;
I made very few changes to the original patch besides the obvious UI restructuring.  I had to scale down all of the vectors for Arc, since there are 64 leds on it and only 14 on the code.   Otherwise, I mainly just removed things from view, even though they are still there in the patch (e.g. the vst~ instance for aux output).  I&amp;#039;ll probably come back to this later...I&amp;#039;ve barely played with it yet, so surely some changes are in order.&lt;br /&gt;
&lt;br /&gt;
Here&amp;#039;s the original page:&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:grainstorm monome Grainstorm patch]&lt;br /&gt;
&lt;br /&gt;
Many thanks, as usual, to Matthew Davidson for sharing his wonderful ideas with the world :)&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Xor&amp;diff=706</id>
		<title>Xor</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Xor&amp;diff=706"/>
		<updated>2012-12-06T08:54:00Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:xor_pic.png]]&lt;br /&gt;
&lt;br /&gt;
A quick port....pretty self explanatory if you check out the [http://docs.monome.org/doku.php?id=app:xor developer&amp;#039;s page].&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve changed very little except for the UI and some things necessary to recall values in m4l and maintain discreet send/receive channels so that you can run multiple instances.&lt;br /&gt;
&lt;br /&gt;
Keys 1 &amp;amp; 2 alternate between &amp;#039;value&amp;#039; and &amp;#039;link&amp;#039; modes.&lt;br /&gt;
&lt;br /&gt;
Original patch by tehn, who has gifted us with more more than just some wonderful hardware inventions.&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:xor  monome xor patch]&lt;br /&gt;
&lt;br /&gt;
[http://post.monome.org/comments.php?DiscussionID=9043 monome forum discussion thread]&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Xor&amp;diff=705</id>
		<title>Xor</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Xor&amp;diff=705"/>
		<updated>2012-12-06T08:52:40Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:xor_pic.png]]&lt;br /&gt;
&lt;br /&gt;
A quick port....pretty self explanatory if you check out the [http://docs.monome.org/doku.php?id=app:xor developer&amp;#039;s page].&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve changed very little except for the UI and some things necessary to recall values in m4l and maintain discreet send/receive channels so that you can run multiple instances.&lt;br /&gt;
&lt;br /&gt;
Keys 1 &amp;amp; 2 alternate between &amp;#039;value&amp;#039; and &amp;#039;link&amp;#039; modes.&lt;br /&gt;
&lt;br /&gt;
Original patch by tehn, who has gifted us with more more than just some wonderful hardware inventions.&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:xor  monome xor patch]&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Plinko&amp;diff=704</id>
		<title>Plinko</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Plinko&amp;diff=704"/>
		<updated>2012-12-06T08:50:58Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Video Tutorials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Video Tutorials ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=6CP7t_sfpBg&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=10&amp;amp;feature=plcp Very early Plinko demo/test]&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=o5RwIkh5hDw&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=9&amp;amp;feature=plcp Tutorial with Plinko and Launchpad].&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:plinko_pic.png]]&lt;br /&gt;
&lt;br /&gt;
Plinko is a generative plugin built to be freely editable in realtime.  See below for some attempts at explaining how it works  (its, uh....well, its rather complicated).&lt;br /&gt;
&lt;br /&gt;
Basically, each cell on the modGrid represents a &amp;#039;node&amp;#039;.  Each node represents the possibility of something happening.  Particles are generated at the beginning of each loop cycle (if &amp;#039;Loop&amp;#039; is turned on) from start-nodes on the grid.  A start node can be created by holding down a node button and pressing the first &amp;#039;&amp;#039;&amp;#039;KEY&amp;#039;&amp;#039;&amp;#039;.  &lt;br /&gt;
&lt;br /&gt;
When a particle is generated, it will begin travelling in a certain direction on the grid.  For every new node it enters, several possible outcomes could occur.&lt;br /&gt;
&lt;br /&gt;
[[File:Plinko flowchart.png]]&lt;br /&gt;
&lt;br /&gt;
There are four planes of possibility for every node.  Each plane is calculated in turn, starting with plane 1.  To view the assignments for each node&amp;#039;s plane, press one of the first four &amp;#039;&amp;#039;&amp;#039;KEY&amp;#039;&amp;#039;&amp;#039;s while nothing else is being held.&lt;br /&gt;
&lt;br /&gt;
The settings for a node will be displayed on the modGrid while holding down that node&amp;#039;s button. Depending on the orientation of the node selected, the screen may be reversed so that scale, note, and probability are on the right side of the grid instead of the left.&lt;br /&gt;
&lt;br /&gt;
[[File:Plinko_assignments.png]]|[[File:Plinko ex1.png]]&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:plinkonome monome Plinkonome docs]&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;KEY&amp;#039;&amp;#039;&amp;#039; Assignments==&lt;br /&gt;
&lt;br /&gt;
In addition to these basic functions, while holding down a node&amp;#039;s button and pressing one of the &amp;#039;&amp;#039;&amp;#039;KEY&amp;#039;&amp;#039;&amp;#039;s, the following changes can be made:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;KEY 1&amp;#039;&amp;#039;&amp;#039;:  This will enable/disable the node as a starting node (the color of the node will change while it is being held to indicate its status).&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;KEY 2&amp;#039;&amp;#039;&amp;#039;:  This will cause the node to become a &amp;#039;wormhole&amp;#039;.  While continuing to hold down the node button after pressing &amp;#039;&amp;#039;&amp;#039;KEY 2&amp;#039;&amp;#039;&amp;#039;, the next cell pressed on the modGrid will become the wormhole&amp;#039;s destination.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;KEY 3&amp;#039;&amp;#039;&amp;#039;:  This will copy the current plane&amp;#039;s settings to all the other planes of the node being held.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;KEY 4&amp;#039;&amp;#039;&amp;#039;:  This will clear the current plane&amp;#039;s settings, setting probability, scale, and note settings to 0, and removing any wormholes or directions.&lt;br /&gt;
&lt;br /&gt;
It is useful when programming on multiple planes to use the node+&amp;#039;&amp;#039;&amp;#039;KEY 4&amp;#039;&amp;#039;&amp;#039; combination to clear the current plane&amp;#039;s settings, and then the node+&amp;#039;&amp;#039;&amp;#039;KEY 3&amp;#039;&amp;#039;&amp;#039; combination to copy those cleared settings to all of the other planes of the current node.&lt;br /&gt;
&lt;br /&gt;
==Presets==&lt;br /&gt;
&lt;br /&gt;
While holding &amp;#039;&amp;#039;&amp;#039;ALT&amp;#039;&amp;#039;&amp;#039;, it is possible to store and recall preset nodal arrangements.  To store a preset, hold &amp;#039;&amp;#039;&amp;#039;ALT&amp;#039;&amp;#039;&amp;#039; and press one of the lower 4 rows of modGrid buttons.  Available slots for storage (i.e. those with no preset data stored in them) will be lit.  &lt;br /&gt;
&lt;br /&gt;
The user can recall one of the stored presets by holding &amp;#039;&amp;#039;&amp;#039;ALT&amp;#039;&amp;#039;&amp;#039; and selecting one of the top 4 rows of lit buttons.  &lt;br /&gt;
&lt;br /&gt;
As soon as a preset is stored by pressing one of the buttons on the bottom 4 rows, it will become  lighted and available for recall on the corresponding button from the top 4 rows.&lt;br /&gt;
&lt;br /&gt;
==Assignments==&lt;br /&gt;
&lt;br /&gt;
Pressing the &amp;quot;assign notes&amp;quot; button will expose a floating window which will allow user assignments of MIDI Notes to different grid positions in the main Plinko editor screen.  Each column represents one &amp;#039;octave&amp;#039; of the assignment matrix.  The assignments can be based on standard modal scales, or completely custom mappings.  &lt;br /&gt;
&lt;br /&gt;
Pressing the &amp;quot;Open Custom Assignment Editor&amp;quot; button will reveal the custom assignments grid.  These assignments correspond to the 64 possible combinations of the two assignment buttons on the editor.  Each column only applies to its corresponding column in the &amp;quot;assign notes&amp;quot; screen (so a column is only active if its corresponding column in the parent editor is assigned to &amp;quot;custom&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
In addition, there is now a new window available, the [[Script_Editor| &amp;quot;Script Editor&amp;quot;]] window.  Please see the corresponding section for more information about this:&lt;br /&gt;
&lt;br /&gt;
[[Script_Editor| The Script Editor Window]]&lt;br /&gt;
&lt;br /&gt;
== Original readme contained in early versions of this mod ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(This is the original text document that was included with the plugin when I first released it.  It is probably still somewhat helpful, and I think all these directions still apply to the current version)&lt;br /&gt;
&lt;br /&gt;
Plinko/Monodal beta 0.8&lt;br /&gt;
&lt;br /&gt;
The concept:  Plinko is a generative grid-based sequencer.  Points of potential (particles) are placed on the a, moving in a certain direction.  For every new grid-square they enter, there are five user-assignable outcomes that are possible, based on the result of a random number generated each turn. Each active node may alter a particles path or fire a note when the particle passes over it.  A user assignable scale may be assigned to each &amp;quot;octave&amp;quot;, or a cusomized midi map may be assigned (on a per octave basis).  Each octave may also be assigned to output to a generic plugin output (the monomod channel for the device), or to any specific nomeout.  In this way, Plinko can feed up to eight different instruments at once.&lt;br /&gt;
&lt;br /&gt;
Each square on the launchpad/grid represents a &amp;quot;node&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
A node is either active or passive depending upon whether it has been assigned &amp;quot;attributes&amp;quot;.&lt;br /&gt;
Each node is a potential &amp;quot;loopstart&amp;quot; point.&lt;br /&gt;
Each node has 4 &amp;quot;planes&amp;quot;.&lt;br /&gt;
Each plane has independent &amp;quot;direction&amp;quot;, &amp;quot;note&amp;quot;, &amp;quot;octave&amp;quot;, &amp;quot;probability&amp;quot;, and &amp;quot;wormhole&amp;quot; attributes.&lt;br /&gt;
&lt;br /&gt;
By holding down a grid key, one can assign multiple directions to a node by pressing the keys adjacent to the pressd node.  The far left or right columns, depending upon the area of the grid pressed (fi the node is on the right part of the grid, the columns will be on the left, and vice versa), represent (from left to right): octave, note, probability.&lt;br /&gt;
&lt;br /&gt;
The four monomod &amp;quot;mode&amp;quot; buttons have the following effects:&lt;br /&gt;
&lt;br /&gt;
When no node is pressed, they select which plane is active.&lt;br /&gt;
&lt;br /&gt;
When a node is pressed:&lt;br /&gt;
&lt;br /&gt;
1 - activates (or deactivates) the node as a loopstart point when in Loop mode.  Generates a particle from that node travelling east (when Loop is turned off)&lt;br /&gt;
2-  activates a wormhole.  While continuing to press the node key, select a grid square as the destination for the wormhole. (e.g. press node x1y1.  while holding x1y1, press mode 2.  CONITINUING  to hold the original node x1y1, press node x3y4).&lt;br /&gt;
3 - zeros a nodes attributes (only for the current plane).&lt;br /&gt;
4 - assigns the current planes nodal attributes to all other planes of a node.&lt;br /&gt;
&lt;br /&gt;
Each &amp;quot;turn&amp;quot; represents one beat triggered by monomod.&lt;br /&gt;
Any particles present in the grid will have their positions updated, and the node they reside in will determine an action based upon its attributes.&lt;br /&gt;
&lt;br /&gt;
Each plane represents a possibility of a node firing.  In its initial state, plane one has a 20% chance of happening, plane two 40%, etc.  When a particle strikes a node, a random number is generated (0-8).  If that number is less than plane 1&amp;#039;s probability, then whatever attributes are also assigned to that nodes plane will be used to determine what happens.  If the number is more than 1&amp;#039;s probability, then the same comparison will be done with plane 2&amp;#039;s probability.&lt;br /&gt;
&lt;br /&gt;
For instance:  a particle, traveling south, strikes a node.  (for this example, we will only consider the first two planes:  just as if plane 3 and 4 had their probability assigned to 0)&lt;br /&gt;
&lt;br /&gt;
The node has the following attirbutes:&lt;br /&gt;
&lt;br /&gt;
Plane1:  oct 0 note 0 prob 4 directions: north, south.&lt;br /&gt;
Plane2:  oct 1 note 4 prob 6 directions: east, west.&lt;br /&gt;
&lt;br /&gt;
The random number generated is a 7:  nothing happens and the particle continues to travel south on  the next turn.&lt;br /&gt;
The random number generated is a 6:  plane 2 is struck:  a note is played (note4,oct0), and the particle is split in two, traveling one east and one west on the next turn.&lt;br /&gt;
The random number generated is a 3:  plane 1 is struck:  no note is played (oct 0 note 0 == no note), but a new particle is created, so the old particle continues on southwards  at the beginning of the next turn, joined by a new particle traveling in the opposite direction.&lt;br /&gt;
&lt;br /&gt;
WTF?&lt;br /&gt;
&lt;br /&gt;
Press button x1y1 (keep holding it!).  Assign a direction (east).  Press Mode 1 to make it a loopstart point. Press.  Press x8y1 (to assign it a probability of 8:  this means it will asways happen). (now let go of x1y1)&lt;br /&gt;
Press button x5y1 (keep holding it!)  Assign a direction (west).  Press x8y1 (probability 8).  Now let go of x5y1.&lt;br /&gt;
Make sure loop is turn on.  Start playing in Live.  You should now have a particle bouncing back and forth between two red nodes.&lt;br /&gt;
&lt;br /&gt;
Nodes change color when they have direction or wormhole attributes, but not when they are only assigned notes.&lt;br /&gt;
The maximum number of particles may be limited in the GUI.  &lt;br /&gt;
Instead of generating a random number at each turn, you may assign that number in the GUI.  This way you can work on one plane of probability at a time.  Plane &amp;quot;9&amp;quot; in the GUI means random, this is the normal behavior.&lt;br /&gt;
The small white button in the bottom corner will open the note editor&lt;br /&gt;
Presets are stored via pattrstorage.  They can be directly written or read from .json files.  &lt;br /&gt;
&lt;br /&gt;
There are lots of little things that need to be done.  There will be a live-play mode very soon, where you can insert particles into the grid via MIDI in real time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Plinko&amp;diff=703</id>
		<title>Plinko</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Plinko&amp;diff=703"/>
		<updated>2012-12-06T08:49:15Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Video Tutorials ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=6CP7t_sfpBg&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=10&amp;amp;feature=plcp Very early on....]&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=o5RwIkh5hDw&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=9&amp;amp;feature=plcp Tutorial with Plinko and Launchpad].&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:plinko_pic.png]]&lt;br /&gt;
&lt;br /&gt;
Plinko is a generative plugin built to be freely editable in realtime.  See below for some attempts at explaining how it works  (its, uh....well, its rather complicated).&lt;br /&gt;
&lt;br /&gt;
Basically, each cell on the modGrid represents a &amp;#039;node&amp;#039;.  Each node represents the possibility of something happening.  Particles are generated at the beginning of each loop cycle (if &amp;#039;Loop&amp;#039; is turned on) from start-nodes on the grid.  A start node can be created by holding down a node button and pressing the first &amp;#039;&amp;#039;&amp;#039;KEY&amp;#039;&amp;#039;&amp;#039;.  &lt;br /&gt;
&lt;br /&gt;
When a particle is generated, it will begin travelling in a certain direction on the grid.  For every new node it enters, several possible outcomes could occur.&lt;br /&gt;
&lt;br /&gt;
[[File:Plinko flowchart.png]]&lt;br /&gt;
&lt;br /&gt;
There are four planes of possibility for every node.  Each plane is calculated in turn, starting with plane 1.  To view the assignments for each node&amp;#039;s plane, press one of the first four &amp;#039;&amp;#039;&amp;#039;KEY&amp;#039;&amp;#039;&amp;#039;s while nothing else is being held.&lt;br /&gt;
&lt;br /&gt;
The settings for a node will be displayed on the modGrid while holding down that node&amp;#039;s button. Depending on the orientation of the node selected, the screen may be reversed so that scale, note, and probability are on the right side of the grid instead of the left.&lt;br /&gt;
&lt;br /&gt;
[[File:Plinko_assignments.png]]|[[File:Plinko ex1.png]]&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:plinkonome monome Plinkonome docs]&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;KEY&amp;#039;&amp;#039;&amp;#039; Assignments==&lt;br /&gt;
&lt;br /&gt;
In addition to these basic functions, while holding down a node&amp;#039;s button and pressing one of the &amp;#039;&amp;#039;&amp;#039;KEY&amp;#039;&amp;#039;&amp;#039;s, the following changes can be made:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;KEY 1&amp;#039;&amp;#039;&amp;#039;:  This will enable/disable the node as a starting node (the color of the node will change while it is being held to indicate its status).&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;KEY 2&amp;#039;&amp;#039;&amp;#039;:  This will cause the node to become a &amp;#039;wormhole&amp;#039;.  While continuing to hold down the node button after pressing &amp;#039;&amp;#039;&amp;#039;KEY 2&amp;#039;&amp;#039;&amp;#039;, the next cell pressed on the modGrid will become the wormhole&amp;#039;s destination.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;KEY 3&amp;#039;&amp;#039;&amp;#039;:  This will copy the current plane&amp;#039;s settings to all the other planes of the node being held.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;KEY 4&amp;#039;&amp;#039;&amp;#039;:  This will clear the current plane&amp;#039;s settings, setting probability, scale, and note settings to 0, and removing any wormholes or directions.&lt;br /&gt;
&lt;br /&gt;
It is useful when programming on multiple planes to use the node+&amp;#039;&amp;#039;&amp;#039;KEY 4&amp;#039;&amp;#039;&amp;#039; combination to clear the current plane&amp;#039;s settings, and then the node+&amp;#039;&amp;#039;&amp;#039;KEY 3&amp;#039;&amp;#039;&amp;#039; combination to copy those cleared settings to all of the other planes of the current node.&lt;br /&gt;
&lt;br /&gt;
==Presets==&lt;br /&gt;
&lt;br /&gt;
While holding &amp;#039;&amp;#039;&amp;#039;ALT&amp;#039;&amp;#039;&amp;#039;, it is possible to store and recall preset nodal arrangements.  To store a preset, hold &amp;#039;&amp;#039;&amp;#039;ALT&amp;#039;&amp;#039;&amp;#039; and press one of the lower 4 rows of modGrid buttons.  Available slots for storage (i.e. those with no preset data stored in them) will be lit.  &lt;br /&gt;
&lt;br /&gt;
The user can recall one of the stored presets by holding &amp;#039;&amp;#039;&amp;#039;ALT&amp;#039;&amp;#039;&amp;#039; and selecting one of the top 4 rows of lit buttons.  &lt;br /&gt;
&lt;br /&gt;
As soon as a preset is stored by pressing one of the buttons on the bottom 4 rows, it will become  lighted and available for recall on the corresponding button from the top 4 rows.&lt;br /&gt;
&lt;br /&gt;
==Assignments==&lt;br /&gt;
&lt;br /&gt;
Pressing the &amp;quot;assign notes&amp;quot; button will expose a floating window which will allow user assignments of MIDI Notes to different grid positions in the main Plinko editor screen.  Each column represents one &amp;#039;octave&amp;#039; of the assignment matrix.  The assignments can be based on standard modal scales, or completely custom mappings.  &lt;br /&gt;
&lt;br /&gt;
Pressing the &amp;quot;Open Custom Assignment Editor&amp;quot; button will reveal the custom assignments grid.  These assignments correspond to the 64 possible combinations of the two assignment buttons on the editor.  Each column only applies to its corresponding column in the &amp;quot;assign notes&amp;quot; screen (so a column is only active if its corresponding column in the parent editor is assigned to &amp;quot;custom&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
In addition, there is now a new window available, the [[Script_Editor| &amp;quot;Script Editor&amp;quot;]] window.  Please see the corresponding section for more information about this:&lt;br /&gt;
&lt;br /&gt;
[[Script_Editor| The Script Editor Window]]&lt;br /&gt;
&lt;br /&gt;
== Original readme contained in early versions of this mod ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(This is the original text document that was included with the plugin when I first released it.  It is probably still somewhat helpful, and I think all these directions still apply to the current version)&lt;br /&gt;
&lt;br /&gt;
Plinko/Monodal beta 0.8&lt;br /&gt;
&lt;br /&gt;
The concept:  Plinko is a generative grid-based sequencer.  Points of potential (particles) are placed on the a, moving in a certain direction.  For every new grid-square they enter, there are five user-assignable outcomes that are possible, based on the result of a random number generated each turn. Each active node may alter a particles path or fire a note when the particle passes over it.  A user assignable scale may be assigned to each &amp;quot;octave&amp;quot;, or a cusomized midi map may be assigned (on a per octave basis).  Each octave may also be assigned to output to a generic plugin output (the monomod channel for the device), or to any specific nomeout.  In this way, Plinko can feed up to eight different instruments at once.&lt;br /&gt;
&lt;br /&gt;
Each square on the launchpad/grid represents a &amp;quot;node&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
A node is either active or passive depending upon whether it has been assigned &amp;quot;attributes&amp;quot;.&lt;br /&gt;
Each node is a potential &amp;quot;loopstart&amp;quot; point.&lt;br /&gt;
Each node has 4 &amp;quot;planes&amp;quot;.&lt;br /&gt;
Each plane has independent &amp;quot;direction&amp;quot;, &amp;quot;note&amp;quot;, &amp;quot;octave&amp;quot;, &amp;quot;probability&amp;quot;, and &amp;quot;wormhole&amp;quot; attributes.&lt;br /&gt;
&lt;br /&gt;
By holding down a grid key, one can assign multiple directions to a node by pressing the keys adjacent to the pressd node.  The far left or right columns, depending upon the area of the grid pressed (fi the node is on the right part of the grid, the columns will be on the left, and vice versa), represent (from left to right): octave, note, probability.&lt;br /&gt;
&lt;br /&gt;
The four monomod &amp;quot;mode&amp;quot; buttons have the following effects:&lt;br /&gt;
&lt;br /&gt;
When no node is pressed, they select which plane is active.&lt;br /&gt;
&lt;br /&gt;
When a node is pressed:&lt;br /&gt;
&lt;br /&gt;
1 - activates (or deactivates) the node as a loopstart point when in Loop mode.  Generates a particle from that node travelling east (when Loop is turned off)&lt;br /&gt;
2-  activates a wormhole.  While continuing to press the node key, select a grid square as the destination for the wormhole. (e.g. press node x1y1.  while holding x1y1, press mode 2.  CONITINUING  to hold the original node x1y1, press node x3y4).&lt;br /&gt;
3 - zeros a nodes attributes (only for the current plane).&lt;br /&gt;
4 - assigns the current planes nodal attributes to all other planes of a node.&lt;br /&gt;
&lt;br /&gt;
Each &amp;quot;turn&amp;quot; represents one beat triggered by monomod.&lt;br /&gt;
Any particles present in the grid will have their positions updated, and the node they reside in will determine an action based upon its attributes.&lt;br /&gt;
&lt;br /&gt;
Each plane represents a possibility of a node firing.  In its initial state, plane one has a 20% chance of happening, plane two 40%, etc.  When a particle strikes a node, a random number is generated (0-8).  If that number is less than plane 1&amp;#039;s probability, then whatever attributes are also assigned to that nodes plane will be used to determine what happens.  If the number is more than 1&amp;#039;s probability, then the same comparison will be done with plane 2&amp;#039;s probability.&lt;br /&gt;
&lt;br /&gt;
For instance:  a particle, traveling south, strikes a node.  (for this example, we will only consider the first two planes:  just as if plane 3 and 4 had their probability assigned to 0)&lt;br /&gt;
&lt;br /&gt;
The node has the following attirbutes:&lt;br /&gt;
&lt;br /&gt;
Plane1:  oct 0 note 0 prob 4 directions: north, south.&lt;br /&gt;
Plane2:  oct 1 note 4 prob 6 directions: east, west.&lt;br /&gt;
&lt;br /&gt;
The random number generated is a 7:  nothing happens and the particle continues to travel south on  the next turn.&lt;br /&gt;
The random number generated is a 6:  plane 2 is struck:  a note is played (note4,oct0), and the particle is split in two, traveling one east and one west on the next turn.&lt;br /&gt;
The random number generated is a 3:  plane 1 is struck:  no note is played (oct 0 note 0 == no note), but a new particle is created, so the old particle continues on southwards  at the beginning of the next turn, joined by a new particle traveling in the opposite direction.&lt;br /&gt;
&lt;br /&gt;
WTF?&lt;br /&gt;
&lt;br /&gt;
Press button x1y1 (keep holding it!).  Assign a direction (east).  Press Mode 1 to make it a loopstart point. Press.  Press x8y1 (to assign it a probability of 8:  this means it will asways happen). (now let go of x1y1)&lt;br /&gt;
Press button x5y1 (keep holding it!)  Assign a direction (west).  Press x8y1 (probability 8).  Now let go of x5y1.&lt;br /&gt;
Make sure loop is turn on.  Start playing in Live.  You should now have a particle bouncing back and forth between two red nodes.&lt;br /&gt;
&lt;br /&gt;
Nodes change color when they have direction or wormhole attributes, but not when they are only assigned notes.&lt;br /&gt;
The maximum number of particles may be limited in the GUI.  &lt;br /&gt;
Instead of generating a random number at each turn, you may assign that number in the GUI.  This way you can work on one plane of probability at a time.  Plane &amp;quot;9&amp;quot; in the GUI means random, this is the normal behavior.&lt;br /&gt;
The small white button in the bottom corner will open the note editor&lt;br /&gt;
Presets are stored via pattrstorage.  They can be directly written or read from .json files.  &lt;br /&gt;
&lt;br /&gt;
There are lots of little things that need to be done.  There will be a live-play mode very soon, where you can insert particles into the grid via MIDI in real time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Tr256&amp;diff=702</id>
		<title>Tr256</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Tr256&amp;diff=702"/>
		<updated>2012-12-06T08:45:03Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Video Tutorial==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=q4d6MriD6y4&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=5&amp;amp;feature=plcp Tutorial for TR256 with OhmRGB]&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:tr256_pic.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Original Patch Info==&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:tr-256 monome patch docs]&lt;br /&gt;
&lt;br /&gt;
TR256 for Monomodular b992.&lt;br /&gt;
&lt;br /&gt;
TR256 is one of Stretta&amp;#039;s patches I took a liking to when I first started working with monome patches.  I&amp;#039;ve changed it quite a bit since he released it.&lt;br /&gt;
&lt;br /&gt;
Mode buttons (Scene buttons on the Launcpad/APC/iPad):&lt;br /&gt;
1-4 sets velocity.  Its scaled between the low and high setting on the GUI.&lt;br /&gt;
5-7 sets the timing rate:  1/4 to 1/16. (shift 1-3 on APC)&lt;br /&gt;
8 turns on triplet.   (shift 4 on APC)&lt;br /&gt;
&lt;br /&gt;
Their are 16 programs.  &lt;br /&gt;
The top row selects which one to edit.&lt;br /&gt;
The second row selects which one is playing.&lt;br /&gt;
The third row is the running status and allows the user to change the beginning and length of the program.  If you hold down the end of the sequence and press a step to the right, it will change the starting point.&lt;br /&gt;
To copy from one program to another:&lt;br /&gt;
Press and hold the edit of the one you wish to copy, and then the  play of the destination program.&lt;br /&gt;
To clear:&lt;br /&gt;
Press and hold the edit of the program to clear, then press one of the velocity mode buttons (1-4).&lt;br /&gt;
To enter record mode:&lt;br /&gt;
Press both edit and play at the same time.&lt;br /&gt;
TR256 will record into the current pattern whatever is routed to it via MIDI that matches its output assignment.  The timing will be quantized to the current timing setting.&lt;br /&gt;
When restart is enabled, the loop will restart at the beginning of the beat after a timing change has occured.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=PressCafe&amp;diff=701</id>
		<title>PressCafe</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=PressCafe&amp;diff=701"/>
		<updated>2012-12-06T08:43:24Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Video Tutorial==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=H34J1Nehgvk&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=6&amp;amp;feature=plcp Tutorial for PressCafe with OhmRGB]&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:presscafe_pic.png]]&lt;br /&gt;
&lt;br /&gt;
==Original Docs==&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:press_cafe monome patch]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=PressCafe&amp;diff=700</id>
		<title>PressCafe</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=PressCafe&amp;diff=700"/>
		<updated>2012-12-06T08:42:40Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Video Tutorial==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=H34J1Nehgvk&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=6&amp;amp;feature=plcp Tutorial for PressCafe with OhmRGB]&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:presscafe_pic.png]]&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:press_cafe monome patch]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=PressCafe&amp;diff=699</id>
		<title>PressCafe</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=PressCafe&amp;diff=699"/>
		<updated>2012-12-06T08:42:23Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Video Tutorial==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=H34J1Nehgvk&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=6&amp;amp;feature=plcp Tutorial for PressCafe with OhmRGB]&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:presscafe_pic.png]]&lt;br /&gt;
&lt;br /&gt;
[[http://docs.monome.org/doku.php?id=app:press_cafe monome patch]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=PressCafe&amp;diff=698</id>
		<title>PressCafe</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=PressCafe&amp;diff=698"/>
		<updated>2012-12-06T08:40:52Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Video Tutorials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Video Tutorial==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=H34J1Nehgvk&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=6&amp;amp;feature=plcp Tutorial for PressCafe with OhmRGB]&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Overview&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[[File:presscafe_pic.png]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Boiingg&amp;diff=697</id>
		<title>Boiingg</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Boiingg&amp;diff=697"/>
		<updated>2012-12-06T08:40:09Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Video Tutorial==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=5aAfRYEQcJc&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=4&amp;amp;feature=plcp Tutorial for Boiingg with OhmRGB]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:boinngg_pic.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Choose grid type by pressing one of the first four key buttons (shift bottom row or bottom row while shift-locked).&lt;br /&gt;
&lt;br /&gt;
Choose timing with second four key buttons.&lt;br /&gt;
&lt;br /&gt;
Timing multiplier speeds up timing.&lt;br /&gt;
&lt;br /&gt;
Store and recall presets by holding down ALT button.&lt;br /&gt;
&lt;br /&gt;
== Original Docs ==&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:boiingg monome site]&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=696</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=696"/>
		<updated>2012-12-06T08:38:50Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
EndCoders for Everything b992.&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
==Video Tutorial==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=xSRQNTSYm24  Endcoders with LividCode]&lt;br /&gt;
&lt;br /&gt;
==Livid Code==&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [[How to use the Codec script|Codec]] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
==Other Controllers==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=694</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=694"/>
		<updated>2012-12-06T08:37:16Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
EndCoders for Everything b992.&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
== Video Tutorial ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=xSRQNTSYm24  Endcoders with LividCode]&lt;br /&gt;
&lt;br /&gt;
== Livid Code ==&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [[How to use the Codec script|Codec]] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
== Other Controllers ==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=693</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=693"/>
		<updated>2012-12-06T08:36:52Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
EndCoders for Everything b992.&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
== Video Tutorials ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=xSRQNTSYm24  Endcoders with LividCode]&lt;br /&gt;
&lt;br /&gt;
== Livid Code ==&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [[How to use the Codec script|Codec]] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
== Other Controllers ==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=692</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=692"/>
		<updated>2012-12-06T08:35:33Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Video Tutorials =&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=xSRQNTSYm24  Endcoders with LividCode]&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
EndCoders for Everything b992.&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
== Livid Code ==&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [[How to use the Codec script|Codec]] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
== Other Controllers ==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=689</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=689"/>
		<updated>2012-12-06T08:34:11Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Video Tutorials=&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=xSRQNTSYm24  Endcoders with LividCode]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
EndCoders for Everything b992.&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Livid Code&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [[How to use the Codec script|Codec]] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Other Controllers&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=688</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=688"/>
		<updated>2012-12-06T08:33:41Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=&amp;#039;&amp;#039;&amp;#039;Video Tutorials&amp;#039;&amp;#039;&amp;#039;=&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=xSRQNTSYm24  Endcoders with LividCode]&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Overview&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
EndCoders for Everything b992.&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Livid Code&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [[How to use the Codec script|Codec]] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Other Controllers&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Polygome&amp;diff=687</id>
		<title>Polygome</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Polygome&amp;diff=687"/>
		<updated>2012-12-06T08:33:01Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
==Video Tutorials==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=W1O8c8vLVMY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=3&amp;amp;feature=plcp  Tutorial for Polygome with OhmRGB]&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:Polygome_pic.png]]&lt;br /&gt;
&lt;br /&gt;
==Original Docs==&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:polygome monome patch]&lt;br /&gt;
&lt;br /&gt;
Polygome isn&amp;#039;t an easy concept...but I think its one of the best patches Stretta has made.&lt;br /&gt;
&lt;br /&gt;
This port behaves mostly the same as his, but lives in Live and remembers its states.  And you can run multiples.&lt;br /&gt;
&lt;br /&gt;
The right hand buttons (scene launch)  select which&lt;br /&gt;
mode the grid is in.&lt;br /&gt;
Mode 1 is play.  The key pressed is the root of the sequence that is selected.&lt;br /&gt;
Mode 2 is record.  You record the sequence by pressing up to 16 cells on the grid.&lt;br /&gt;
Mode 3 programs velocity for each step.&lt;br /&gt;
Mode 4 programs duration for each step.&lt;br /&gt;
The bottom row of Mode 4 allows for turning off or on each step.&lt;br /&gt;
&lt;br /&gt;
You can send MIDI to polygome and change the the scale that is assigned.&lt;br /&gt;
&lt;br /&gt;
The top right and left corner of the grid is the hold button.&lt;br /&gt;
&lt;br /&gt;
Try the gomeizer if you&amp;#039;re stumped...its instant gratification (after a wait of a few seconds to randomize everything)....&lt;br /&gt;
&lt;br /&gt;
Then off to google, to find out whats really going on ;)&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;IMPORTANT TIP: Live&amp;#039;s transport &amp;#039;&amp;#039;must&amp;#039;&amp;#039; be running in order for polygome to do &amp;#039;&amp;#039;anything&amp;#039;&amp;#039;.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Polygome&amp;diff=685</id>
		<title>Polygome</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Polygome&amp;diff=685"/>
		<updated>2012-12-06T08:28:58Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Video Tutorials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==&amp;#039;&amp;#039;&amp;#039;Video Tutorials&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=W1O8c8vLVMY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=3&amp;amp;feature=plcp  Tutorial for Polygome with OhmRGB]&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Overview&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[[File:Polygome_pic.png]]&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Original Docs&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:polygome monome patch]&lt;br /&gt;
&lt;br /&gt;
Polygome isn&amp;#039;t an easy concept...but I think its one of the best patches Stretta has made.&lt;br /&gt;
&lt;br /&gt;
This port behaves mostly the same as his, but lives in Live and remembers its states.  And you can run multiples.&lt;br /&gt;
&lt;br /&gt;
The right hand buttons (scene launch)  select which&lt;br /&gt;
mode the grid is in.&lt;br /&gt;
Mode 1 is play.  The key pressed is the root of the sequence that is selected.&lt;br /&gt;
Mode 2 is record.  You record the sequence by pressing up to 16 cells on the grid.&lt;br /&gt;
Mode 3 programs velocity for each step.&lt;br /&gt;
Mode 4 programs duration for each step.&lt;br /&gt;
The bottom row of Mode 4 allows for turning off or on each step.&lt;br /&gt;
&lt;br /&gt;
You can send MIDI to polygome and change the the scale that is assigned.&lt;br /&gt;
&lt;br /&gt;
The top right and left corner of the grid is the hold button.&lt;br /&gt;
&lt;br /&gt;
Try the gomeizer if you&amp;#039;re stumped...its instant gratification (after a wait of a few seconds to randomize everything)....&lt;br /&gt;
&lt;br /&gt;
Then off to google, to find out whats really going on ;)&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;IMPORTANT TIP: Live&amp;#039;s transport &amp;#039;&amp;#039;must&amp;#039;&amp;#039; be running in order for polygome to do &amp;#039;&amp;#039;anything&amp;#039;&amp;#039;.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Polygome&amp;diff=684</id>
		<title>Polygome</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Polygome&amp;diff=684"/>
		<updated>2012-12-06T08:27:21Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==&amp;#039;&amp;#039;&amp;#039;Video Tutorials&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=W1O8c8vLVMY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=3&amp;amp;feature=plcp  b99 Tutorial for Polygome with OhmRGB]&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Overview&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[[File:Polygome_pic.png]]&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Original Docs&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:polygome monome patch]&lt;br /&gt;
&lt;br /&gt;
Polygome isn&amp;#039;t an easy concept...but I think its one of the best patches Stretta has made.&lt;br /&gt;
&lt;br /&gt;
This port behaves mostly the same as his, but lives in Live and remembers its states.  And you can run multiples.&lt;br /&gt;
&lt;br /&gt;
The right hand buttons (scene launch)  select which&lt;br /&gt;
mode the grid is in.&lt;br /&gt;
Mode 1 is play.  The key pressed is the root of the sequence that is selected.&lt;br /&gt;
Mode 2 is record.  You record the sequence by pressing up to 16 cells on the grid.&lt;br /&gt;
Mode 3 programs velocity for each step.&lt;br /&gt;
Mode 4 programs duration for each step.&lt;br /&gt;
The bottom row of Mode 4 allows for turning off or on each step.&lt;br /&gt;
&lt;br /&gt;
You can send MIDI to polygome and change the the scale that is assigned.&lt;br /&gt;
&lt;br /&gt;
The top right and left corner of the grid is the hold button.&lt;br /&gt;
&lt;br /&gt;
Try the gomeizer if you&amp;#039;re stumped...its instant gratification (after a wait of a few seconds to randomize everything)....&lt;br /&gt;
&lt;br /&gt;
Then off to google, to find out whats really going on ;)&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;IMPORTANT TIP: Live&amp;#039;s transport &amp;#039;&amp;#039;must&amp;#039;&amp;#039; be running in order for polygome to do &amp;#039;&amp;#039;anything&amp;#039;&amp;#039;.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=683</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=683"/>
		<updated>2012-12-06T08:26:03Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Video Tutorials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==&amp;#039;&amp;#039;&amp;#039;Video Tutorials&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=xSRQNTSYm24  Endcoders with LividCode]&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Overview&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
EndCoders for Everything b992.&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Livid Code&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [[How to use the Codec script|Codec]] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Other Controllers&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=682</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=682"/>
		<updated>2012-12-06T08:25:17Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==&amp;#039;&amp;#039;&amp;#039;Video Tutorials&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=xSRQNTSYm24  Endcoders with Code]&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Overview&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
EndCoders for Everything b992.&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Livid Code&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [[How to use the Codec script|Codec]] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Other Controllers&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=681</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=681"/>
		<updated>2012-12-06T08:23:56Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==&amp;#039;&amp;#039;&amp;#039;Video Tutorials&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=xSRQNTSYm24  Endcoders with Code]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Overview&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
EndCoders for Everything b992.&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Livid Code&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [[How to use the Codec script|Codec]] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Other Controllers&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Polygome&amp;diff=680</id>
		<title>Polygome</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Polygome&amp;diff=680"/>
		<updated>2012-12-06T08:22:50Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==&amp;#039;&amp;#039;&amp;#039;Video Tutorials&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=W1O8c8vLVMY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=3&amp;amp;feature=plcp  b99 Tutorial for Polygome with OhmRGB]&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Overview&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[[File:Polygome_pic.png]]&lt;br /&gt;
&lt;br /&gt;
==&amp;#039;&amp;#039;&amp;#039;Original Docs&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&lt;br /&gt;
[http://docs.monome.org/doku.php?id=app:polygome monome patch]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Polygome isn&amp;#039;t an easy concept...but I think its one of the best patches Stretta has made.&lt;br /&gt;
&lt;br /&gt;
This port behaves mostly the same as his, but lives in Live and remembers its states.  And you can run multiples.&lt;br /&gt;
&lt;br /&gt;
The right hand buttons (scene launch)  select which&lt;br /&gt;
mode the grid is in.&lt;br /&gt;
Mode 1 is play.  The key pressed is the root of the sequence that is selected.&lt;br /&gt;
Mode 2 is record.  You record the sequence by pressing up to 16 cells on the grid.&lt;br /&gt;
Mode 3 programs velocity for each step.&lt;br /&gt;
Mode 4 programs duration for each step.&lt;br /&gt;
The bottom row of Mode 4 allows for turning off or on each step.&lt;br /&gt;
&lt;br /&gt;
You can send MIDI to polygome and change the the scale that is assigned.&lt;br /&gt;
&lt;br /&gt;
The top right and left corner of the grid is the hold button.&lt;br /&gt;
&lt;br /&gt;
Try the gomeizer if you&amp;#039;re stumped...its instant gratification (after a wait of a few seconds to randomize everything)....&lt;br /&gt;
&lt;br /&gt;
Then off to google, to find out whats really going on ;)&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;IMPORTANT TIP: Live&amp;#039;s transport &amp;#039;&amp;#039;must&amp;#039;&amp;#039; be running in order for polygome to do &amp;#039;&amp;#039;anything&amp;#039;&amp;#039;.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=679</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=679"/>
		<updated>2012-12-06T08:21:07Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;EndCoders for Everything b992.&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Video Tutorial:&amp;#039;&amp;#039;&amp;#039; [http://www.youtube.com/watch?v=xSRQNTSYm24 Endcoders]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Livid Code&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [[How to use the Codec script|Codec]] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Other Controllers&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=678</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=678"/>
		<updated>2012-12-06T08:20:45Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;EndCoders for Everything b992.&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Video Tutorial:&amp;#039;&amp;#039;&amp;#039; [http://www.youtube.com/watch?v=xSRQNTSYm24 Endcoders]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Livid Code&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [[How to use the Codec script|Codec]] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Other Controllers&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=677</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=677"/>
		<updated>2012-12-06T08:18:47Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;EndCoders for Everything b992.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Video Tutorial:&amp;#039;&amp;#039;&amp;#039; [http://www.youtube.com/watch?v=xSRQNTSYm24 Endcoders]&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [[How to use the Codec script|Codec]] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=676</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=676"/>
		<updated>2012-12-06T08:18:18Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;EndCoders for Everything b992.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Video Tutorial:&amp;#039;&amp;#039;&amp;#039; [http://www.youtube.com/watch?v=xSRQNTSYm24 Endcoders]&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the [How to use the Codec script|Codec] scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=675</id>
		<title>Endcoders</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Endcoders&amp;diff=675"/>
		<updated>2012-12-06T08:15:59Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:endcoders_pic.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Video Tutorial:&amp;#039;&amp;#039;&amp;#039; [http://www.youtube.com/watch?v=xSRQNTSYm24 Endcoders]&lt;br /&gt;
&lt;br /&gt;
EndCoders for Everything b992.&lt;br /&gt;
&lt;br /&gt;
OK, maybe not everything.  But a bunch of things.&lt;br /&gt;
&lt;br /&gt;
Basic idea:  You have 8 mappable knobs.  Each knob is capable of controlling 24 different parameters at once, each with its own breakpoint curve.  You can store eight banks of presets containing these breakpoint curves, and whether or not each curve is active or not.&lt;br /&gt;
&lt;br /&gt;
If you have a Livid Code, its pretty simple to get around (you&amp;#039;ll need Monomodular and the new Codec scripts):&lt;br /&gt;
&lt;br /&gt;
Press the top row of knobs to select which master knob you wish to edit (the LED below it should light up). All of its parameters are instantly brought up on the remaining rows of dials, along with the current values of those parameters.  If the green light is on, that means the dial is &amp;#039;active&amp;#039;, and linked to the breakpoint curve of its parent knob.  You can toggle the active status by pressing that knob.&lt;br /&gt;
&lt;br /&gt;
To choose what a parameter dial is linked to, simply select that parameter in Live (by clicking on it; it should show a darker area around it when its selected), and press the dial while holding down the third button from the top on the left side. If successfully linked, the LED below it will light up.&lt;br /&gt;
&lt;br /&gt;
You can now turn the top knob to any desired position, then turn the parameter to where you want it to be at the knobs position (either by turning the parameters dial, or by changing it in Live), and take a snapshot of that value on the parameters breakpoint curve by holding down the second row left button and pressing down on the dial (it is often useful to turn the parameter dial&amp;#039;s active status off while doing this stuff).&lt;br /&gt;
&lt;br /&gt;
You can capture all the parameter values at once by holding down the second row button and pushing the knob that belongs to that parameter group (the top row of knobs).  &lt;br /&gt;
&lt;br /&gt;
You can clear the breakpoint graph by holding down the top row button and pressing the parameter dial.&lt;br /&gt;
&lt;br /&gt;
You can clear ALL a knobs breakpoint graphs by holding down the top row button and pressing the knob.&lt;br /&gt;
&lt;br /&gt;
You can change the dial speed by toggling the fourth row button.  It will be lit while fast is on.&lt;br /&gt;
&lt;br /&gt;
You can open up the editor for a knob by holding down the third row button and pressing one of the top knobs corresponding.&lt;br /&gt;
&lt;br /&gt;
You can store presets by holding shift and pressing one of the bottom column buttons, and recall them by pressing the same buttons without shift held.&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve tried to make the plugin as versatile as possible for those without a Livid Code. You can still do all the important stuff, but you&amp;#039;ll have to go about it differently.  The currently selected knob is available in the GUI, and the small buttons on the top right of each graph allow selection of  the parameter for the graph (left one) and change of  the graphs active state for each preset (right one).&lt;br /&gt;
&lt;br /&gt;
You can only have one breakpoint active per Live parameter, but of course you can have different combinations by storing the active state in different presets.   If you select a parameter that is already chosen and active on a new graph, the old one will automatically be deactivated when you select the new one.&lt;br /&gt;
&lt;br /&gt;
Of course, you can also just use the entire thing without the breakpoints (by deactivating everything) to store parameters in banks that you can get to easily by pressing the top row of buttons.&lt;br /&gt;
&lt;br /&gt;
[[Category:Mods]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Hex&amp;diff=674</id>
		<title>Hex</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Hex&amp;diff=674"/>
		<updated>2012-12-06T08:13:03Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:Hex pic a.png]]&lt;br /&gt;
&lt;br /&gt;
Hex contains sixteen sequences, or parts, that can be edited and manipulated in real time in various ways from the controller.  When linked to a properly configured DrumRack, the controller&amp;#039;s encoders control parameters belonging to each of it&amp;#039;s chains.  When in PolyMode, the part can be transmitted directly to an instrument and send a pitched sequence.  Each of the sequences contains sixteen different presets, which can be chosen and stored directly from the controller.  Loop begin and end points can also be set using the controller.  All of the sequences speed settings can be set changed independently in either quantized or unquantized amounts.  Sequence timing can be synchronized between different parts in an easy fashion.  Different behavior definitions can be made for each step of each sequence directly from the controller.  Part-mute and preset changes can be recorded directly into the currently playing MIDI clip on the same track that the mod is present, even while playing back previously recorded automation data in the same clip.  &lt;br /&gt;
&lt;br /&gt;
Hex combines most of the ergonomics of the Livid Stepp:r with the versatility and speed of the &amp;quot;binary&amp;quot; mod I wrote for the Code last year.  It is still a work in progress, and some features are still being fleshed out (among which are polyphonic step mode, solo mode, and trigger mode).  While borrowing heavily from both of its predecessors, it yet promises a lot of unrealized potential under the hood.  A great deal of the underpinnings of &amp;quot;binary&amp;quot; have yet to be implemented.&lt;br /&gt;
&lt;br /&gt;
Hex is currently built for the CNTRL:R, but it&amp;#039;s functionality can be accessed from any controller by using Live&amp;#039;s MIDI Mapping capabilities.  It will include support for other grid-based controllers that are compatible with Monomodular with future releases.  The idea here is to eventually replace the functionality of Stepp:r, Polygome, TR256, and Binary with a single patch that is accessible from multiple controllers at once, while improving the speed, efficiency, and capabilities of the originals.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Video Demos&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=BkyNa4tz1y4 Hex Basics]&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=V6TOLEEDQfU Hex Details]&lt;br /&gt;
&lt;br /&gt;
=The User Interface=&lt;br /&gt;
&lt;br /&gt;
The currently selected sequence data is displayed in the center pane.  To change what data is being viewed, select a new new view mode.  The default view shows the active state of each step in the currently selected sequence.  Active state can be changed via the controller, but other types of data can currently only be changed from the UI (duration, velocity, rulebends, pitch).  This will change when Ohm/Block integration is finished (but probably won&amp;#039;t matter to you unless you own a CNTRL:R and another grid-based controller).&lt;br /&gt;
&lt;br /&gt;
Three main areas of control are delineated in the patch UI, and are controllable in different ways with their corresponding controls on the CNTRL:R.  &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;The Grid&amp;#039;&amp;#039;&amp;#039; -  this describes the 4x4 RGB buttons in the center of the CNTRL:R.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;The Keys&amp;#039;&amp;#039;&amp;#039; -  this describes the 16x2 RGB buttons on the bottom of the CNTRL:R.  They are broken into two sections, the &amp;#039;&amp;#039;&amp;#039;Top Row&amp;#039;&amp;#039;&amp;#039; and the &amp;#039;&amp;#039;&amp;#039;Bottom Row&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;The Encoders&amp;#039;&amp;#039;&amp;#039; -  this describes the top endless rotary encoders and their corresponding buttons.&lt;br /&gt;
&lt;br /&gt;
[[File:Hex pic b.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Each area can be assigned different functionality based on the two assignment menus on the UI.  You can select a way to work from the UI itself, or you can use the &amp;quot;Mode&amp;quot; button on the bottom row of encoders to step through the available modes.&lt;br /&gt;
&lt;br /&gt;
==The Grid==&lt;br /&gt;
&lt;br /&gt;
===select===&lt;br /&gt;
In its default position, the grid is in &amp;quot;select&amp;quot; mode.  Each of the buttons corresponds to a sequence.  You can select which sequence you are currently editing by pressing one of the sixteen buttons.  The UI and the CTNRL:R will automatically update to reflect the data contained in your selection.  If an appropriate instrument is configured, the encoders will control and reflect the current value of its parameters.  &lt;br /&gt;
&lt;br /&gt;
===add===&lt;br /&gt;
[[File:Hex pic add.png]]&lt;br /&gt;
&lt;br /&gt;
In &amp;quot;add&amp;quot; mode, pressing one of the grid buttons will add a note event to its corresponding sequence at its current time position.  It will also play the note if the transport is running.  It will always select the new sequence.&lt;br /&gt;
&lt;br /&gt;
===freewheel===&lt;br /&gt;
[[File:Hex pic freewheel.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;This mode is currently broken for the sake of getting the release out, but will be back soon!&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
In &amp;quot;freewheel&amp;quot; mode, the grid operates in the same manner as &amp;quot;select&amp;quot; mode.  However, the encoders rings reflect the current position and data for each of the grids highlighted 8 sequences, and the encoders themselves control the unquantized speed of each of the sequences. &lt;br /&gt;
&lt;br /&gt;
The green LED of each encoder ring indicates whether or not a sequence is currently quantized.  &lt;br /&gt;
&lt;br /&gt;
A quantized sequence will become unquantized if it&amp;#039;s corresponding speed dial is turned, or if it is synced to another unquantized sequence (see &amp;quot;wheel syncing&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
An unquantized sequence can become quantized if it is selected and one of the speed buttons are pressed.  It will lock to the nearest quantization value, depending on which direction you&amp;#039;ve nudged it.   It can also become quantized if it is synced to another quantized sequence (see &amp;quot;wheel syncing&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
The encoder&amp;#039;s will automatically be updated to reflect the currently selected sequences region any time the sequence you&amp;#039;ve chosen is outside the bounds of the last one you&amp;#039;d selected.  The encoder&amp;#039;s assignments will always be reflected by the highlighted (magenta) area of the Grid.&lt;br /&gt;
&lt;br /&gt;
===mute, preset, global===&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;mute&amp;quot;, &amp;quot;preset&amp;quot;, and &amp;quot;global&amp;quot; modes correspond to the key modes of the same name.  They are provided for convenience when creating sequences and editing.  They are NOT available via &amp;quot;quick-select&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
===quick-select===&lt;br /&gt;
&lt;br /&gt;
Quick-select allows an alternate method of stepping through different modes and functionalities in the patch.  Any time you hold down a Grid button while selecting a part, several things change: &lt;br /&gt;
&lt;br /&gt;
1) An alternate assignment of the upper keys appears, and will remain until the button is released.  The default mode entered in quick-select is &amp;quot;single preset&amp;quot;, but it can be changed in the settings menu to any of the available key modes.&lt;br /&gt;
&lt;br /&gt;
2) Pressing the mode button (one of the encoder buttons) will step through the available Grid modes instead of the key modes.  Caveat:  pressing the mode button while in &amp;quot;add&amp;quot; mode will ALWAYS cause the Grid to return to &amp;quot;select&amp;quot; mode.&lt;br /&gt;
&lt;br /&gt;
3) Pressing the button corresponding to another part will synchronize the timing of that part to the current timing of the chosen sequence (see &amp;quot;wheel syncing&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
4) Alternate encoder-button functionality is available:&lt;br /&gt;
&lt;br /&gt;
---Speed buttons change notetype, &lt;br /&gt;
---Repeat button steps through direction.&lt;br /&gt;
---Rotate buttons change the active sequence view.&lt;br /&gt;
&lt;br /&gt;
==The Keys==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Lower Keys&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
The lower keys always represent whether or not a current step is active.  The active state of a step can be toggled off/on with its corresponding button.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Upper Keys&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
===mute===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic a.png]]&lt;br /&gt;
&lt;br /&gt;
In it&amp;#039;s default mode, the upper keys control the mute state of each part.  Mute data can be recorded into a playing or recording clip (see &amp;quot;Automation&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===length===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic loop.png]]&lt;br /&gt;
&lt;br /&gt;
The length of a sequence can be changed on the fly by pressing one of the buttons corresponding to the position in the timeline where you wish the part loop.  By holding down the loops end-point and selecting a button at an earlier position, you can also change the loops start point.&lt;br /&gt;
&lt;br /&gt;
===behavior===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic behaviors.png]]&lt;br /&gt;
&lt;br /&gt;
The behavior assigned to each step can be changed.  Any current assignments are also reflected for the selected sequence.  See &amp;quot;Behaviors&amp;quot;, below.&lt;br /&gt;
&lt;br /&gt;
===single preset===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic single.png]]&lt;br /&gt;
&lt;br /&gt;
The currently selected part&amp;#039;s preset can be chosen by pressing one of the buttons.  Each time you change to a new preset, the currently selected preset is stored (however, this behavior is defeated when the &amp;quot;Lock&amp;quot; feature is enabled.  This can speed things up considerably, see the section about &amp;quot;Lock&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===global preset===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic global.png]]&lt;br /&gt;
&lt;br /&gt;
In global mode, selecting a preset recalls the corresponding preset for EVERY part.  It&amp;#039;s important to understand that (currently) when changing global presets, only the currently selected part&amp;#039;s preset data is stored.  (I&amp;#039;ve tried it the other way, it&amp;#039;s just too darned slow)&lt;br /&gt;
&lt;br /&gt;
===poly record===&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_polyrec.png]]&lt;br /&gt;
&lt;br /&gt;
Poly record mode allows the user to record a sequence of notes via the keys top keys.  The notes will only be played back at their recorded pitch if the selected voice is set to a channel other than &amp;quot;Plug&amp;quot;.  Unfortunately, this limits use of this feature to OSX only....however, I have a solution for Windows user&amp;#039;s coming soon ;)&lt;br /&gt;
&lt;br /&gt;
===poly play===&lt;br /&gt;
&lt;br /&gt;
[[File:hex_polyplay.png]]&lt;br /&gt;
&lt;br /&gt;
Poly play mode allows the user to play back the current sequence immediatedly, ala Polygome.  Each of the top keys represent a base note, and pressing it will start the sequence playing independent of the current time position, with its root based on the note pressed, and locked to the current mode setting.  It&amp;#039;s also important to recognize that the Poly Offset parameter is useful here, since otherwise the sequence base note will be C-2.&lt;br /&gt;
&lt;br /&gt;
==The Encoders==&lt;br /&gt;
&lt;br /&gt;
Hex is capable of latching to the controls of multiple different instruments in your Live set.  I&amp;#039;ve done my best to make it capable of being both a Drum-based beat programmer as well as a semi-capable, freewheeling note sequencer for use with other instruments.  Because of this, things get a little tricky here.&lt;br /&gt;
&lt;br /&gt;
When you open hex for the first time, it should be in its default mode, or &amp;quot;Plug&amp;quot; mode.  This means that its output is sent to the m4l plugins output.  You can either place a DrumRack after it or send the tracks output to another track containing a DrumRack that you want hex to play.  If hex does not automatically detect the DrumRack you wish it&amp;#039;s encoders to control, it will look something like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_detect_instrument.png]]&lt;br /&gt;
&lt;br /&gt;
Don&amp;#039;t worry, all  is not lost.  Just press the button that says &amp;quot;Detect Instrument&amp;quot;.  A little window will be floated on your screen, that looks like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_detect_float.png]]&lt;br /&gt;
&lt;br /&gt;
Select the DrumRack you wish to control (the &amp;quot;Blue Hand&amp;quot; should appear on it, and it should be hilighted), and then press the button in the float.  The CNTRL:R&amp;#039;s encoder rings should immediately update to reflect the currently selected part&amp;#039;s parameters.&lt;br /&gt;
&lt;br /&gt;
Your GUI should look something like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_encoders.png]]&lt;br /&gt;
&lt;br /&gt;
If you&amp;#039;re not happy with the parameters that hex uses, just group the instrument and assign the macros to the parameters that you wish to control.  Hex will happily lock to them instead.&lt;br /&gt;
&lt;br /&gt;
When you&amp;#039;re ready to go further and explore some new madness, turn the &amp;quot;Channel&amp;quot; encoder to something besides &amp;quot;Plug&amp;quot;.  In addition to the plugin&amp;#039;s output, hex can transmit your part to one of sixteen MIDI channels.  Hex stores a different device for each MIDI channel.  In this way, you can quickly assign a single note sequence that is outputting to your DrumRack to an instrument in a completely different place in your set, and it will start playing whatever multi-note pattern you&amp;#039;ve recorded in that track.&lt;br /&gt;
&lt;br /&gt;
You can change the channel that the part is assigned to by turning the channel encoder:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_channel.png]]&lt;br /&gt;
&lt;br /&gt;
There are a few caveats here.  As mentioned earlier, this only currently works on OSX.  You&amp;#039;ll need to create an IAC loop passthrough by doing the following:&lt;br /&gt;
&lt;br /&gt;
1.  Create an IAC Bus in OSX&amp;quot;s &amp;quot;Audio MIDI Setup&amp;quot;.  &lt;br /&gt;
&lt;br /&gt;
2.  Make sure the IAC Bus&amp;#039;s port is set for &amp;quot;Track&amp;quot; (both input and output) in Live&amp;#039;s MIDI Preferences.&lt;br /&gt;
&lt;br /&gt;
2.  Open hex&amp;#039;s Settings and assign that IAC Bus as the &amp;quot;Poly Output Port&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
3.  Assign the instrument you want to control to Hex in the same manner you did with the DrumRack.  You&amp;#039;ll need to do this once for each of the sixteen channels, but the settings will be stored with your project unless you delete the controlled instrument at some point.  &lt;br /&gt;
&lt;br /&gt;
4.  Set the MIDI input port of the destination instrument&amp;#039;s track to the IAC Bus you&amp;#039;ve created, and set its Channel input to the channel you assigned the instrument to in hex.&lt;br /&gt;
&lt;br /&gt;
Once you have assigned an instrument to one of hex&amp;#039;s individual channels, the display should look like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_encoders2.png]]&lt;br /&gt;
&lt;br /&gt;
Notice that there are some differences.  Hex only controls 4 parameters of the target instrument (on the top 4 encoders).  On the second row of encoders, PolyOffset and Mode have replaced the &amp;quot;Plug&amp;quot;s parameter assignments.  &lt;br /&gt;
&lt;br /&gt;
PolyOffset is the base note of your sequence. &lt;br /&gt;
&lt;br /&gt;
Mode is the scale mode which the sequence will use.&lt;br /&gt;
&lt;br /&gt;
For perhaps a better explanation of how this works, see the video:&lt;br /&gt;
&lt;br /&gt;
[[Placeholder]]&lt;br /&gt;
&lt;br /&gt;
==Other Controls==&lt;br /&gt;
&lt;br /&gt;
The modVolume dial controls the master output of the entire patch.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Mode&amp;quot; button steps through all available Key modes, making it easy to work in a different way.&lt;br /&gt;
&lt;br /&gt;
==Wheel Syncing==&lt;br /&gt;
&lt;br /&gt;
It is easy to synchronize the speed of two different parts.  Select the part to which you want to synchronize, and while holding down its button, press the button corresponding to the sequence you wish to change.&lt;br /&gt;
&lt;br /&gt;
==Automation==&lt;br /&gt;
&lt;br /&gt;
Hex allows recording of automation directly to a clip that is playing or recording on the track it&amp;#039;s on.  To enable this, either create a MIDI clip on its track and start playing it, or start recording a new clip on its track.  Then, press the REC button on its UI.  Any &amp;quot;mute&amp;quot; or &amp;quot;single preset&amp;quot; changes that you make will be recorded in the clip as you make them.&lt;br /&gt;
&lt;br /&gt;
In order to play back this data, just play the clip and make sure that PLAY is turned on in the UI.  You can have both PLAY and REC enabled at the same time in order to overdub new changes (however, this will not currently erase older data).  &lt;br /&gt;
&lt;br /&gt;
Hex uses note-based automation.  It&amp;#039;s important to understand a little about this:  any note event arriving at the mod&amp;#039;s input can be interpreted as automation data.  Hex reserves note numbers above 113 for use with automation.  As long as &amp;quot;Play&amp;quot; is not enabled, nothing dire will happen.  However, be sure not to send unintentional notes to Hex when it&amp;#039;s in play mode, or some wacky things will probably happen.  Any notes below its automation range will just be passed through to hex&amp;#039;s output.&lt;br /&gt;
&lt;br /&gt;
===Behaviors===&lt;br /&gt;
&lt;br /&gt;
In order to create more variability in a sequence&amp;#039;s sound, you can assign behaviors to each step of a sequence.  This allows changing how a step acts over the space of 8 bars of 16 beats.  &lt;br /&gt;
&lt;br /&gt;
There are seven user definable behaviors.  They can be assigned in the advanced settings.  Each behavior has 8 steps.  Each step corresponds to one cycle of a loops sequence.  &lt;br /&gt;
&lt;br /&gt;
By default, each behavior is filled with one type of action.  This can be changed by clicking on the Behavior grid in the settings menu.  The available actions are:&lt;br /&gt;
&lt;br /&gt;
1)  No Action.  When no action is chosen, nothing will be played on the assigned cycle even if a step is active in the sequence the behavior is assigned to.&lt;br /&gt;
&lt;br /&gt;
2) Trigger.  When trigger is chosen, if a step is active on the assigned cycle, a note will be played in the sequence the behavior is assigned to.&lt;br /&gt;
&lt;br /&gt;
3) Random.  When random is chosen, the step may or may not trigger a note based on chance.  In addition, the corresponding &amp;#039;rulebend&amp;#039; for the step determines the how likely the note will trigger.&lt;br /&gt;
&lt;br /&gt;
4) Sympathy.  If another rulebend in the current step of any other sequence is equal to the currently selected sequence step&amp;#039;s rulebend, the note will play.&lt;br /&gt;
&lt;br /&gt;
5) Dominate.  If active, the note will play.  In addition, it will mute any other notes played by other sequences unless those sequences are also set to dominate.  The length of dominance is determined by the corresponding step&amp;#039;s rulebend value.&lt;br /&gt;
&lt;br /&gt;
6) Delay.  If active, the note will play, but a delay will occur before it is triggered corresponding to that steps rulebend value.&lt;br /&gt;
&lt;br /&gt;
7) Repeat.  If active, the note will play, and will be repeated.  The interval and number of repeats is determined by the rulebend value.&lt;br /&gt;
&lt;br /&gt;
8) Plink.  This will start a particle in any Plinko mod that is currently in the set.  The rulebend determines the direction of the particle.  The particle will appear in the square corresponding to the part(x-coordinate) and the step(y-coordinate).&lt;br /&gt;
&lt;br /&gt;
===Advanced Settings===&lt;br /&gt;
&lt;br /&gt;
[[File:Hex pic settings.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Select + Hold Temporarily Reveals:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Changing this setting allows cusomization of what mode Quick-view snaps to.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Timing Changes Happen:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
If set to &amp;quot;immediately&amp;quot;, quantized changes will happen when they are made.  Otherwise, timing changes will not be triggered until the beginning of the part&amp;#039;s next loop.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Global Chain Offset&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
This one&amp;#039;s important.  And a little tricky.  All you need to know:  set this value to the lowest note in your DrumRack, and don&amp;#039;t allow any gaps in the your Rack.  You can always insert an empty InstrumentRack in blank spaces, but there can&amp;#039;t be any gaps or the parameter controls will not lock to the correct chain when you select a new sequence. &lt;br /&gt;
&lt;br /&gt;
Because there is no way to determine the note-assignment of a DrumRack&amp;#039;s chain, it is necessary to order your DrumRack with no gaps.  It&amp;#039;s not important which note it starts on, but if you start at a note higher than 0 (C-2), you&amp;#039;ll need to compensate for chain detection by changing this setting.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Transpose Steps&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
You can change the number of steps that are changed when using the &amp;quot;-1st&amp;quot; and &amp;quot;+1st&amp;quot; encoder buttons by changing this value.  &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Capture Currently Selected Instrument&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If you wish to use Hex with an instrument or DrumRack that is not immediately adjacent to it, you can select the instrument you wish to control in Live and then press this button.  Hex will detect the new instrument, and should store it&amp;#039;s id for your concurrent sessions.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;MIDI Remote Assignment&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
You can use Live&amp;#039;s MIDI Learn functionality to assign any controller to the CNTRL:R&amp;#039;s controls.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Initialize Preset&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Clear the currently selected preset&amp;#039;s data.  This clears all sequences in the currently selected preset slot, not just the selected sequence.&lt;br /&gt;
&lt;br /&gt;
In order to clear all presets in all sequences, make sure the &amp;quot;Global&amp;quot; button is active in the Randomize section below, then press the Initialize Preset button.  It&amp;#039;ll take a few seconds.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Behaviors&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Assign new actions for each type of behavior by clicking the squares on the grid.  Each step will cycle through all available actions.&lt;br /&gt;
&lt;br /&gt;
You can use the Randomize button in the top right corner to shake things up a bit.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Randomize&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Randomize individual data types for the current global preset.  You can randomize all data types in the current preset by pressing the &amp;quot;All&amp;quot; button.&lt;br /&gt;
&lt;br /&gt;
If &amp;quot;Global&amp;quot; is active, any randomization or initialization changes will affect all global presets (that means every single preset in every single sequence).  Be carefull....it takes a little while.&lt;br /&gt;
&lt;br /&gt;
=Known Issues and Bugs=&lt;br /&gt;
&lt;br /&gt;
Read and Write (via pattrstorage) are currently broken.  I&amp;#039;m looking into this.&lt;br /&gt;
&lt;br /&gt;
Freewheel is currently not functioning correctly.  This was working in the prototypes (as it works in &amp;quot;binary&amp;quot;, as well), but due to some last minute bugs that cropped up I had to disable some of this mode&amp;#039;s functionality in order to promote better timing for the rest of the patch.  It will be back to normal in an update, hopefully soon.&lt;br /&gt;
&lt;br /&gt;
In addition, freewheel encoder rings are not getting updated properly when changing presets or initializing the patch.  You will have to manually select a part before its encoder ring display correctly updates.&lt;br /&gt;
&lt;br /&gt;
In Freewheel mode, the bottom encoder rings do not currently light to display the value being controlled.&lt;br /&gt;
&lt;br /&gt;
Automation rec/play currently only supports the mutes and single preset changes.  This will probably see more additions later if it proves to be truly useful.&lt;br /&gt;
&lt;br /&gt;
=Technology=&lt;br /&gt;
&lt;br /&gt;
Here are the header comments from the core js file, which might give a little more food for your curiousity:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;This script is the result of collaboration with Peter Nyboer @ Livid Instruments and represents a great deal of effort to gain some speed and stability from the original Steppr without sacrificing too much readability.  The majority of the functionality for the entire patch can be modified in this js or the accompanying poly~ object, &amp;quot;steppr_wheel&amp;quot;, without ever opening the actual containing patch in the m4l editor (this is crucial for speeding up the development process).  Because of this, the functionality of the patch can be radically altered merely by modifying the poly~ or adding some lines of code in to this js.  As an example, the poly~ used as the base for this patch is only a slightly modified version of the &amp;quot;binary&amp;quot; mod (from Monomodular), and the majority of processes in this script are maintained between both versions.&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Although the original ideas came from the Stepp:rs, this patch is in fact a complete recoding of those ideas.&lt;br /&gt;
&lt;br /&gt;
More to come shortly....&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Hex&amp;diff=673</id>
		<title>Hex</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Hex&amp;diff=673"/>
		<updated>2012-12-06T08:12:46Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:Hex pic a.png]]&lt;br /&gt;
&lt;br /&gt;
Hex contains sixteen sequences, or parts, that can be edited and manipulated in real time in various ways from the controller.  When linked to a properly configured DrumRack, the controller&amp;#039;s encoders control parameters belonging to each of it&amp;#039;s chains.  When in PolyMode, the part can be transmitted directly to an instrument and send a pitched sequence.  Each of the sequences contains sixteen different presets, which can be chosen and stored directly from the controller.  Loop begin and end points can also be set using the controller.  All of the sequences speed settings can be set changed independently in either quantized or unquantized amounts.  Sequence timing can be synchronized between different parts in an easy fashion.  Different behavior definitions can be made for each step of each sequence directly from the controller.  Part-mute and preset changes can be recorded directly into the currently playing MIDI clip on the same track that the mod is present, even while playing back previously recorded automation data in the same clip.  &lt;br /&gt;
&lt;br /&gt;
Hex combines most of the ergonomics of the Livid Stepp:r with the versatility and speed of the &amp;quot;binary&amp;quot; mod I wrote for the Code last year.  It is still a work in progress, and some features are still being fleshed out (among which are polyphonic step mode, solo mode, and trigger mode).  While borrowing heavily from both of its predecessors, it yet promises a lot of unrealized potential under the hood.  A great deal of the underpinnings of &amp;quot;binary&amp;quot; have yet to be implemented.&lt;br /&gt;
&lt;br /&gt;
Hex is currently built for the CNTRL:R, but it&amp;#039;s functionality can be accessed from any controller by using Live&amp;#039;s MIDI Mapping capabilities.  It will include support for other grid-based controllers that are compatible with Monomodular with future releases.  The idea here is to eventually replace the functionality of Stepp:r, Polygome, TR256, and Binary with a single patch that is accessible from multiple controllers at once, while improving the speed, efficiency, and capabilities of the originals.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Video Demos&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
[http://www.youtube.com/watch?v=BkyNa4tz1y4 Hex Basics]&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=V6TOLEEDQfU Hex Details]&lt;br /&gt;
&lt;br /&gt;
=The User Interface=&lt;br /&gt;
&lt;br /&gt;
The currently selected sequence data is displayed in the center pane.  To change what data is being viewed, select a new new view mode.  The default view shows the active state of each step in the currently selected sequence.  Active state can be changed via the controller, but other types of data can currently only be changed from the UI (duration, velocity, rulebends, pitch).  This will change when Ohm/Block integration is finished (but probably won&amp;#039;t matter to you unless you own a CNTRL:R and another grid-based controller).&lt;br /&gt;
&lt;br /&gt;
Three main areas of control are delineated in the patch UI, and are controllable in different ways with their corresponding controls on the CNTRL:R.  &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;The Grid&amp;#039;&amp;#039;&amp;#039; -  this describes the 4x4 RGB buttons in the center of the CNTRL:R.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;The Keys&amp;#039;&amp;#039;&amp;#039; -  this describes the 16x2 RGB buttons on the bottom of the CNTRL:R.  They are broken into two sections, the &amp;#039;&amp;#039;&amp;#039;Top Row&amp;#039;&amp;#039;&amp;#039; and the &amp;#039;&amp;#039;&amp;#039;Bottom Row&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;The Encoders&amp;#039;&amp;#039;&amp;#039; -  this describes the top endless rotary encoders and their corresponding buttons.&lt;br /&gt;
&lt;br /&gt;
[[File:Hex pic b.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Each area can be assigned different functionality based on the two assignment menus on the UI.  You can select a way to work from the UI itself, or you can use the &amp;quot;Mode&amp;quot; button on the bottom row of encoders to step through the available modes.&lt;br /&gt;
&lt;br /&gt;
==The Grid==&lt;br /&gt;
&lt;br /&gt;
===select===&lt;br /&gt;
In its default position, the grid is in &amp;quot;select&amp;quot; mode.  Each of the buttons corresponds to a sequence.  You can select which sequence you are currently editing by pressing one of the sixteen buttons.  The UI and the CTNRL:R will automatically update to reflect the data contained in your selection.  If an appropriate instrument is configured, the encoders will control and reflect the current value of its parameters.  &lt;br /&gt;
&lt;br /&gt;
===add===&lt;br /&gt;
[[File:Hex pic add.png]]&lt;br /&gt;
&lt;br /&gt;
In &amp;quot;add&amp;quot; mode, pressing one of the grid buttons will add a note event to its corresponding sequence at its current time position.  It will also play the note if the transport is running.  It will always select the new sequence.&lt;br /&gt;
&lt;br /&gt;
===freewheel===&lt;br /&gt;
[[File:Hex pic freewheel.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;This mode is currently broken for the sake of getting the release out, but will be back soon!&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
In &amp;quot;freewheel&amp;quot; mode, the grid operates in the same manner as &amp;quot;select&amp;quot; mode.  However, the encoders rings reflect the current position and data for each of the grids highlighted 8 sequences, and the encoders themselves control the unquantized speed of each of the sequences. &lt;br /&gt;
&lt;br /&gt;
The green LED of each encoder ring indicates whether or not a sequence is currently quantized.  &lt;br /&gt;
&lt;br /&gt;
A quantized sequence will become unquantized if it&amp;#039;s corresponding speed dial is turned, or if it is synced to another unquantized sequence (see &amp;quot;wheel syncing&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
An unquantized sequence can become quantized if it is selected and one of the speed buttons are pressed.  It will lock to the nearest quantization value, depending on which direction you&amp;#039;ve nudged it.   It can also become quantized if it is synced to another quantized sequence (see &amp;quot;wheel syncing&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
The encoder&amp;#039;s will automatically be updated to reflect the currently selected sequences region any time the sequence you&amp;#039;ve chosen is outside the bounds of the last one you&amp;#039;d selected.  The encoder&amp;#039;s assignments will always be reflected by the highlighted (magenta) area of the Grid.&lt;br /&gt;
&lt;br /&gt;
===mute, preset, global===&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;mute&amp;quot;, &amp;quot;preset&amp;quot;, and &amp;quot;global&amp;quot; modes correspond to the key modes of the same name.  They are provided for convenience when creating sequences and editing.  They are NOT available via &amp;quot;quick-select&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
===quick-select===&lt;br /&gt;
&lt;br /&gt;
Quick-select allows an alternate method of stepping through different modes and functionalities in the patch.  Any time you hold down a Grid button while selecting a part, several things change: &lt;br /&gt;
&lt;br /&gt;
1) An alternate assignment of the upper keys appears, and will remain until the button is released.  The default mode entered in quick-select is &amp;quot;single preset&amp;quot;, but it can be changed in the settings menu to any of the available key modes.&lt;br /&gt;
&lt;br /&gt;
2) Pressing the mode button (one of the encoder buttons) will step through the available Grid modes instead of the key modes.  Caveat:  pressing the mode button while in &amp;quot;add&amp;quot; mode will ALWAYS cause the Grid to return to &amp;quot;select&amp;quot; mode.&lt;br /&gt;
&lt;br /&gt;
3) Pressing the button corresponding to another part will synchronize the timing of that part to the current timing of the chosen sequence (see &amp;quot;wheel syncing&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
4) Alternate encoder-button functionality is available:&lt;br /&gt;
&lt;br /&gt;
---Speed buttons change notetype, &lt;br /&gt;
---Repeat button steps through direction.&lt;br /&gt;
---Rotate buttons change the active sequence view.&lt;br /&gt;
&lt;br /&gt;
==The Keys==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Lower Keys&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
The lower keys always represent whether or not a current step is active.  The active state of a step can be toggled off/on with its corresponding button.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Upper Keys&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
===mute===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic a.png]]&lt;br /&gt;
&lt;br /&gt;
In it&amp;#039;s default mode, the upper keys control the mute state of each part.  Mute data can be recorded into a playing or recording clip (see &amp;quot;Automation&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===length===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic loop.png]]&lt;br /&gt;
&lt;br /&gt;
The length of a sequence can be changed on the fly by pressing one of the buttons corresponding to the position in the timeline where you wish the part loop.  By holding down the loops end-point and selecting a button at an earlier position, you can also change the loops start point.&lt;br /&gt;
&lt;br /&gt;
===behavior===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic behaviors.png]]&lt;br /&gt;
&lt;br /&gt;
The behavior assigned to each step can be changed.  Any current assignments are also reflected for the selected sequence.  See &amp;quot;Behaviors&amp;quot;, below.&lt;br /&gt;
&lt;br /&gt;
===single preset===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic single.png]]&lt;br /&gt;
&lt;br /&gt;
The currently selected part&amp;#039;s preset can be chosen by pressing one of the buttons.  Each time you change to a new preset, the currently selected preset is stored (however, this behavior is defeated when the &amp;quot;Lock&amp;quot; feature is enabled.  This can speed things up considerably, see the section about &amp;quot;Lock&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===global preset===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic global.png]]&lt;br /&gt;
&lt;br /&gt;
In global mode, selecting a preset recalls the corresponding preset for EVERY part.  It&amp;#039;s important to understand that (currently) when changing global presets, only the currently selected part&amp;#039;s preset data is stored.  (I&amp;#039;ve tried it the other way, it&amp;#039;s just too darned slow)&lt;br /&gt;
&lt;br /&gt;
===poly record===&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_polyrec.png]]&lt;br /&gt;
&lt;br /&gt;
Poly record mode allows the user to record a sequence of notes via the keys top keys.  The notes will only be played back at their recorded pitch if the selected voice is set to a channel other than &amp;quot;Plug&amp;quot;.  Unfortunately, this limits use of this feature to OSX only....however, I have a solution for Windows user&amp;#039;s coming soon ;)&lt;br /&gt;
&lt;br /&gt;
===poly play===&lt;br /&gt;
&lt;br /&gt;
[[File:hex_polyplay.png]]&lt;br /&gt;
&lt;br /&gt;
Poly play mode allows the user to play back the current sequence immediatedly, ala Polygome.  Each of the top keys represent a base note, and pressing it will start the sequence playing independent of the current time position, with its root based on the note pressed, and locked to the current mode setting.  It&amp;#039;s also important to recognize that the Poly Offset parameter is useful here, since otherwise the sequence base note will be C-2.&lt;br /&gt;
&lt;br /&gt;
==The Encoders==&lt;br /&gt;
&lt;br /&gt;
Hex is capable of latching to the controls of multiple different instruments in your Live set.  I&amp;#039;ve done my best to make it capable of being both a Drum-based beat programmer as well as a semi-capable, freewheeling note sequencer for use with other instruments.  Because of this, things get a little tricky here.&lt;br /&gt;
&lt;br /&gt;
When you open hex for the first time, it should be in its default mode, or &amp;quot;Plug&amp;quot; mode.  This means that its output is sent to the m4l plugins output.  You can either place a DrumRack after it or send the tracks output to another track containing a DrumRack that you want hex to play.  If hex does not automatically detect the DrumRack you wish it&amp;#039;s encoders to control, it will look something like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_detect_instrument.png]]&lt;br /&gt;
&lt;br /&gt;
Don&amp;#039;t worry, all  is not lost.  Just press the button that says &amp;quot;Detect Instrument&amp;quot;.  A little window will be floated on your screen, that looks like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_detect_float.png]]&lt;br /&gt;
&lt;br /&gt;
Select the DrumRack you wish to control (the &amp;quot;Blue Hand&amp;quot; should appear on it, and it should be hilighted), and then press the button in the float.  The CNTRL:R&amp;#039;s encoder rings should immediately update to reflect the currently selected part&amp;#039;s parameters.&lt;br /&gt;
&lt;br /&gt;
Your GUI should look something like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_encoders.png]]&lt;br /&gt;
&lt;br /&gt;
If you&amp;#039;re not happy with the parameters that hex uses, just group the instrument and assign the macros to the parameters that you wish to control.  Hex will happily lock to them instead.&lt;br /&gt;
&lt;br /&gt;
When you&amp;#039;re ready to go further and explore some new madness, turn the &amp;quot;Channel&amp;quot; encoder to something besides &amp;quot;Plug&amp;quot;.  In addition to the plugin&amp;#039;s output, hex can transmit your part to one of sixteen MIDI channels.  Hex stores a different device for each MIDI channel.  In this way, you can quickly assign a single note sequence that is outputting to your DrumRack to an instrument in a completely different place in your set, and it will start playing whatever multi-note pattern you&amp;#039;ve recorded in that track.&lt;br /&gt;
&lt;br /&gt;
You can change the channel that the part is assigned to by turning the channel encoder:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_channel.png]]&lt;br /&gt;
&lt;br /&gt;
There are a few caveats here.  As mentioned earlier, this only currently works on OSX.  You&amp;#039;ll need to create an IAC loop passthrough by doing the following:&lt;br /&gt;
&lt;br /&gt;
1.  Create an IAC Bus in OSX&amp;quot;s &amp;quot;Audio MIDI Setup&amp;quot;.  &lt;br /&gt;
&lt;br /&gt;
2.  Make sure the IAC Bus&amp;#039;s port is set for &amp;quot;Track&amp;quot; (both input and output) in Live&amp;#039;s MIDI Preferences.&lt;br /&gt;
&lt;br /&gt;
2.  Open hex&amp;#039;s Settings and assign that IAC Bus as the &amp;quot;Poly Output Port&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
3.  Assign the instrument you want to control to Hex in the same manner you did with the DrumRack.  You&amp;#039;ll need to do this once for each of the sixteen channels, but the settings will be stored with your project unless you delete the controlled instrument at some point.  &lt;br /&gt;
&lt;br /&gt;
4.  Set the MIDI input port of the destination instrument&amp;#039;s track to the IAC Bus you&amp;#039;ve created, and set its Channel input to the channel you assigned the instrument to in hex.&lt;br /&gt;
&lt;br /&gt;
Once you have assigned an instrument to one of hex&amp;#039;s individual channels, the display should look like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_encoders2.png]]&lt;br /&gt;
&lt;br /&gt;
Notice that there are some differences.  Hex only controls 4 parameters of the target instrument (on the top 4 encoders).  On the second row of encoders, PolyOffset and Mode have replaced the &amp;quot;Plug&amp;quot;s parameter assignments.  &lt;br /&gt;
&lt;br /&gt;
PolyOffset is the base note of your sequence. &lt;br /&gt;
&lt;br /&gt;
Mode is the scale mode which the sequence will use.&lt;br /&gt;
&lt;br /&gt;
For perhaps a better explanation of how this works, see the video:&lt;br /&gt;
&lt;br /&gt;
[[Placeholder]]&lt;br /&gt;
&lt;br /&gt;
==Other Controls==&lt;br /&gt;
&lt;br /&gt;
The modVolume dial controls the master output of the entire patch.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Mode&amp;quot; button steps through all available Key modes, making it easy to work in a different way.&lt;br /&gt;
&lt;br /&gt;
==Wheel Syncing==&lt;br /&gt;
&lt;br /&gt;
It is easy to synchronize the speed of two different parts.  Select the part to which you want to synchronize, and while holding down its button, press the button corresponding to the sequence you wish to change.&lt;br /&gt;
&lt;br /&gt;
==Automation==&lt;br /&gt;
&lt;br /&gt;
Hex allows recording of automation directly to a clip that is playing or recording on the track it&amp;#039;s on.  To enable this, either create a MIDI clip on its track and start playing it, or start recording a new clip on its track.  Then, press the REC button on its UI.  Any &amp;quot;mute&amp;quot; or &amp;quot;single preset&amp;quot; changes that you make will be recorded in the clip as you make them.&lt;br /&gt;
&lt;br /&gt;
In order to play back this data, just play the clip and make sure that PLAY is turned on in the UI.  You can have both PLAY and REC enabled at the same time in order to overdub new changes (however, this will not currently erase older data).  &lt;br /&gt;
&lt;br /&gt;
Hex uses note-based automation.  It&amp;#039;s important to understand a little about this:  any note event arriving at the mod&amp;#039;s input can be interpreted as automation data.  Hex reserves note numbers above 113 for use with automation.  As long as &amp;quot;Play&amp;quot; is not enabled, nothing dire will happen.  However, be sure not to send unintentional notes to Hex when it&amp;#039;s in play mode, or some wacky things will probably happen.  Any notes below its automation range will just be passed through to hex&amp;#039;s output.&lt;br /&gt;
&lt;br /&gt;
===Behaviors===&lt;br /&gt;
&lt;br /&gt;
In order to create more variability in a sequence&amp;#039;s sound, you can assign behaviors to each step of a sequence.  This allows changing how a step acts over the space of 8 bars of 16 beats.  &lt;br /&gt;
&lt;br /&gt;
There are seven user definable behaviors.  They can be assigned in the advanced settings.  Each behavior has 8 steps.  Each step corresponds to one cycle of a loops sequence.  &lt;br /&gt;
&lt;br /&gt;
By default, each behavior is filled with one type of action.  This can be changed by clicking on the Behavior grid in the settings menu.  The available actions are:&lt;br /&gt;
&lt;br /&gt;
1)  No Action.  When no action is chosen, nothing will be played on the assigned cycle even if a step is active in the sequence the behavior is assigned to.&lt;br /&gt;
&lt;br /&gt;
2) Trigger.  When trigger is chosen, if a step is active on the assigned cycle, a note will be played in the sequence the behavior is assigned to.&lt;br /&gt;
&lt;br /&gt;
3) Random.  When random is chosen, the step may or may not trigger a note based on chance.  In addition, the corresponding &amp;#039;rulebend&amp;#039; for the step determines the how likely the note will trigger.&lt;br /&gt;
&lt;br /&gt;
4) Sympathy.  If another rulebend in the current step of any other sequence is equal to the currently selected sequence step&amp;#039;s rulebend, the note will play.&lt;br /&gt;
&lt;br /&gt;
5) Dominate.  If active, the note will play.  In addition, it will mute any other notes played by other sequences unless those sequences are also set to dominate.  The length of dominance is determined by the corresponding step&amp;#039;s rulebend value.&lt;br /&gt;
&lt;br /&gt;
6) Delay.  If active, the note will play, but a delay will occur before it is triggered corresponding to that steps rulebend value.&lt;br /&gt;
&lt;br /&gt;
7) Repeat.  If active, the note will play, and will be repeated.  The interval and number of repeats is determined by the rulebend value.&lt;br /&gt;
&lt;br /&gt;
8) Plink.  This will start a particle in any Plinko mod that is currently in the set.  The rulebend determines the direction of the particle.  The particle will appear in the square corresponding to the part(x-coordinate) and the step(y-coordinate).&lt;br /&gt;
&lt;br /&gt;
===Advanced Settings===&lt;br /&gt;
&lt;br /&gt;
[[File:Hex pic settings.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Select + Hold Temporarily Reveals:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Changing this setting allows cusomization of what mode Quick-view snaps to.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Timing Changes Happen:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
If set to &amp;quot;immediately&amp;quot;, quantized changes will happen when they are made.  Otherwise, timing changes will not be triggered until the beginning of the part&amp;#039;s next loop.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Global Chain Offset&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
This one&amp;#039;s important.  And a little tricky.  All you need to know:  set this value to the lowest note in your DrumRack, and don&amp;#039;t allow any gaps in the your Rack.  You can always insert an empty InstrumentRack in blank spaces, but there can&amp;#039;t be any gaps or the parameter controls will not lock to the correct chain when you select a new sequence. &lt;br /&gt;
&lt;br /&gt;
Because there is no way to determine the note-assignment of a DrumRack&amp;#039;s chain, it is necessary to order your DrumRack with no gaps.  It&amp;#039;s not important which note it starts on, but if you start at a note higher than 0 (C-2), you&amp;#039;ll need to compensate for chain detection by changing this setting.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Transpose Steps&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
You can change the number of steps that are changed when using the &amp;quot;-1st&amp;quot; and &amp;quot;+1st&amp;quot; encoder buttons by changing this value.  &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Capture Currently Selected Instrument&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If you wish to use Hex with an instrument or DrumRack that is not immediately adjacent to it, you can select the instrument you wish to control in Live and then press this button.  Hex will detect the new instrument, and should store it&amp;#039;s id for your concurrent sessions.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;MIDI Remote Assignment&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
You can use Live&amp;#039;s MIDI Learn functionality to assign any controller to the CNTRL:R&amp;#039;s controls.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Initialize Preset&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Clear the currently selected preset&amp;#039;s data.  This clears all sequences in the currently selected preset slot, not just the selected sequence.&lt;br /&gt;
&lt;br /&gt;
In order to clear all presets in all sequences, make sure the &amp;quot;Global&amp;quot; button is active in the Randomize section below, then press the Initialize Preset button.  It&amp;#039;ll take a few seconds.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Behaviors&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Assign new actions for each type of behavior by clicking the squares on the grid.  Each step will cycle through all available actions.&lt;br /&gt;
&lt;br /&gt;
You can use the Randomize button in the top right corner to shake things up a bit.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Randomize&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Randomize individual data types for the current global preset.  You can randomize all data types in the current preset by pressing the &amp;quot;All&amp;quot; button.&lt;br /&gt;
&lt;br /&gt;
If &amp;quot;Global&amp;quot; is active, any randomization or initialization changes will affect all global presets (that means every single preset in every single sequence).  Be carefull....it takes a little while.&lt;br /&gt;
&lt;br /&gt;
=Known Issues and Bugs=&lt;br /&gt;
&lt;br /&gt;
Read and Write (via pattrstorage) are currently broken.  I&amp;#039;m looking into this.&lt;br /&gt;
&lt;br /&gt;
Freewheel is currently not functioning correctly.  This was working in the prototypes (as it works in &amp;quot;binary&amp;quot;, as well), but due to some last minute bugs that cropped up I had to disable some of this mode&amp;#039;s functionality in order to promote better timing for the rest of the patch.  It will be back to normal in an update, hopefully soon.&lt;br /&gt;
&lt;br /&gt;
In addition, freewheel encoder rings are not getting updated properly when changing presets or initializing the patch.  You will have to manually select a part before its encoder ring display correctly updates.&lt;br /&gt;
&lt;br /&gt;
In Freewheel mode, the bottom encoder rings do not currently light to display the value being controlled.&lt;br /&gt;
&lt;br /&gt;
Automation rec/play currently only supports the mutes and single preset changes.  This will probably see more additions later if it proves to be truly useful.&lt;br /&gt;
&lt;br /&gt;
=Technology=&lt;br /&gt;
&lt;br /&gt;
Here are the header comments from the core js file, which might give a little more food for your curiousity:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;This script is the result of collaboration with Peter Nyboer @ Livid Instruments and represents a great deal of effort to gain some speed and stability from the original Steppr without sacrificing too much readability.  The majority of the functionality for the entire patch can be modified in this js or the accompanying poly~ object, &amp;quot;steppr_wheel&amp;quot;, without ever opening the actual containing patch in the m4l editor (this is crucial for speeding up the development process).  Because of this, the functionality of the patch can be radically altered merely by modifying the poly~ or adding some lines of code in to this js.  As an example, the poly~ used as the base for this patch is only a slightly modified version of the &amp;quot;binary&amp;quot; mod (from Monomodular), and the majority of processes in this script are maintained between both versions.&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Although the original ideas came from the Stepp:rs, this patch is in fact a complete recoding of those ideas.&lt;br /&gt;
&lt;br /&gt;
More to come shortly....&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Hex&amp;diff=672</id>
		<title>Hex</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Hex&amp;diff=672"/>
		<updated>2012-12-06T08:11:17Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Overview==&lt;br /&gt;
&lt;br /&gt;
[[File:Hex pic a.png]]&lt;br /&gt;
&lt;br /&gt;
Hex contains sixteen sequences, or parts, that can be edited and manipulated in real time in various ways from the controller.  When linked to a properly configured DrumRack, the controller&amp;#039;s encoders control parameters belonging to each of it&amp;#039;s chains.  When in PolyMode, the part can be transmitted directly to an instrument and send a pitched sequence.  Each of the sequences contains sixteen different presets, which can be chosen and stored directly from the controller.  Loop begin and end points can also be set using the controller.  All of the sequences speed settings can be set changed independently in either quantized or unquantized amounts.  Sequence timing can be synchronized between different parts in an easy fashion.  Different behavior definitions can be made for each step of each sequence directly from the controller.  Part-mute and preset changes can be recorded directly into the currently playing MIDI clip on the same track that the mod is present, even while playing back previously recorded automation data in the same clip.  &lt;br /&gt;
&lt;br /&gt;
Hex combines most of the ergonomics of the Livid Stepp:r with the versatility and speed of the &amp;quot;binary&amp;quot; mod I wrote for the Code last year.  It is still a work in progress, and some features are still being fleshed out (among which are polyphonic step mode, solo mode, and trigger mode).  While borrowing heavily from both of its predecessors, it yet promises a lot of unrealized potential under the hood.  A great deal of the underpinnings of &amp;quot;binary&amp;quot; have yet to be implemented.&lt;br /&gt;
&lt;br /&gt;
Hex is currently built for the CNTRL:R, but it&amp;#039;s functionality can be accessed from any controller by using Live&amp;#039;s MIDI Mapping capabilities.  It will include support for other grid-based controllers that are compatible with Monomodular with future releases.  The idea here is to eventually replace the functionality of Stepp:r, Polygome, TR256, and Binary with a single patch that is accessible from multiple controllers at once, while improving the speed, efficiency, and capabilities of the originals.&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=BkyNa4tz1y4 Hex Basics Video Demo]&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=V6TOLEEDQfU Hex Details Video Demo]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=The User Interface=&lt;br /&gt;
&lt;br /&gt;
The currently selected sequence data is displayed in the center pane.  To change what data is being viewed, select a new new view mode.  The default view shows the active state of each step in the currently selected sequence.  Active state can be changed via the controller, but other types of data can currently only be changed from the UI (duration, velocity, rulebends, pitch).  This will change when Ohm/Block integration is finished (but probably won&amp;#039;t matter to you unless you own a CNTRL:R and another grid-based controller).&lt;br /&gt;
&lt;br /&gt;
Three main areas of control are delineated in the patch UI, and are controllable in different ways with their corresponding controls on the CNTRL:R.  &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;The Grid&amp;#039;&amp;#039;&amp;#039; -  this describes the 4x4 RGB buttons in the center of the CNTRL:R.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;The Keys&amp;#039;&amp;#039;&amp;#039; -  this describes the 16x2 RGB buttons on the bottom of the CNTRL:R.  They are broken into two sections, the &amp;#039;&amp;#039;&amp;#039;Top Row&amp;#039;&amp;#039;&amp;#039; and the &amp;#039;&amp;#039;&amp;#039;Bottom Row&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;The Encoders&amp;#039;&amp;#039;&amp;#039; -  this describes the top endless rotary encoders and their corresponding buttons.&lt;br /&gt;
&lt;br /&gt;
[[File:Hex pic b.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Each area can be assigned different functionality based on the two assignment menus on the UI.  You can select a way to work from the UI itself, or you can use the &amp;quot;Mode&amp;quot; button on the bottom row of encoders to step through the available modes.&lt;br /&gt;
&lt;br /&gt;
==The Grid==&lt;br /&gt;
&lt;br /&gt;
===select===&lt;br /&gt;
In its default position, the grid is in &amp;quot;select&amp;quot; mode.  Each of the buttons corresponds to a sequence.  You can select which sequence you are currently editing by pressing one of the sixteen buttons.  The UI and the CTNRL:R will automatically update to reflect the data contained in your selection.  If an appropriate instrument is configured, the encoders will control and reflect the current value of its parameters.  &lt;br /&gt;
&lt;br /&gt;
===add===&lt;br /&gt;
[[File:Hex pic add.png]]&lt;br /&gt;
&lt;br /&gt;
In &amp;quot;add&amp;quot; mode, pressing one of the grid buttons will add a note event to its corresponding sequence at its current time position.  It will also play the note if the transport is running.  It will always select the new sequence.&lt;br /&gt;
&lt;br /&gt;
===freewheel===&lt;br /&gt;
[[File:Hex pic freewheel.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;This mode is currently broken for the sake of getting the release out, but will be back soon!&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
In &amp;quot;freewheel&amp;quot; mode, the grid operates in the same manner as &amp;quot;select&amp;quot; mode.  However, the encoders rings reflect the current position and data for each of the grids highlighted 8 sequences, and the encoders themselves control the unquantized speed of each of the sequences. &lt;br /&gt;
&lt;br /&gt;
The green LED of each encoder ring indicates whether or not a sequence is currently quantized.  &lt;br /&gt;
&lt;br /&gt;
A quantized sequence will become unquantized if it&amp;#039;s corresponding speed dial is turned, or if it is synced to another unquantized sequence (see &amp;quot;wheel syncing&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
An unquantized sequence can become quantized if it is selected and one of the speed buttons are pressed.  It will lock to the nearest quantization value, depending on which direction you&amp;#039;ve nudged it.   It can also become quantized if it is synced to another quantized sequence (see &amp;quot;wheel syncing&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
The encoder&amp;#039;s will automatically be updated to reflect the currently selected sequences region any time the sequence you&amp;#039;ve chosen is outside the bounds of the last one you&amp;#039;d selected.  The encoder&amp;#039;s assignments will always be reflected by the highlighted (magenta) area of the Grid.&lt;br /&gt;
&lt;br /&gt;
===mute, preset, global===&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;mute&amp;quot;, &amp;quot;preset&amp;quot;, and &amp;quot;global&amp;quot; modes correspond to the key modes of the same name.  They are provided for convenience when creating sequences and editing.  They are NOT available via &amp;quot;quick-select&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
===quick-select===&lt;br /&gt;
&lt;br /&gt;
Quick-select allows an alternate method of stepping through different modes and functionalities in the patch.  Any time you hold down a Grid button while selecting a part, several things change: &lt;br /&gt;
&lt;br /&gt;
1) An alternate assignment of the upper keys appears, and will remain until the button is released.  The default mode entered in quick-select is &amp;quot;single preset&amp;quot;, but it can be changed in the settings menu to any of the available key modes.&lt;br /&gt;
&lt;br /&gt;
2) Pressing the mode button (one of the encoder buttons) will step through the available Grid modes instead of the key modes.  Caveat:  pressing the mode button while in &amp;quot;add&amp;quot; mode will ALWAYS cause the Grid to return to &amp;quot;select&amp;quot; mode.&lt;br /&gt;
&lt;br /&gt;
3) Pressing the button corresponding to another part will synchronize the timing of that part to the current timing of the chosen sequence (see &amp;quot;wheel syncing&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
4) Alternate encoder-button functionality is available:&lt;br /&gt;
&lt;br /&gt;
---Speed buttons change notetype, &lt;br /&gt;
---Repeat button steps through direction.&lt;br /&gt;
---Rotate buttons change the active sequence view.&lt;br /&gt;
&lt;br /&gt;
==The Keys==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Lower Keys&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
The lower keys always represent whether or not a current step is active.  The active state of a step can be toggled off/on with its corresponding button.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Upper Keys&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
===mute===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic a.png]]&lt;br /&gt;
&lt;br /&gt;
In it&amp;#039;s default mode, the upper keys control the mute state of each part.  Mute data can be recorded into a playing or recording clip (see &amp;quot;Automation&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===length===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic loop.png]]&lt;br /&gt;
&lt;br /&gt;
The length of a sequence can be changed on the fly by pressing one of the buttons corresponding to the position in the timeline where you wish the part loop.  By holding down the loops end-point and selecting a button at an earlier position, you can also change the loops start point.&lt;br /&gt;
&lt;br /&gt;
===behavior===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic behaviors.png]]&lt;br /&gt;
&lt;br /&gt;
The behavior assigned to each step can be changed.  Any current assignments are also reflected for the selected sequence.  See &amp;quot;Behaviors&amp;quot;, below.&lt;br /&gt;
&lt;br /&gt;
===single preset===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic single.png]]&lt;br /&gt;
&lt;br /&gt;
The currently selected part&amp;#039;s preset can be chosen by pressing one of the buttons.  Each time you change to a new preset, the currently selected preset is stored (however, this behavior is defeated when the &amp;quot;Lock&amp;quot; feature is enabled.  This can speed things up considerably, see the section about &amp;quot;Lock&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===global preset===&lt;br /&gt;
&lt;br /&gt;
[[File:hex pic global.png]]&lt;br /&gt;
&lt;br /&gt;
In global mode, selecting a preset recalls the corresponding preset for EVERY part.  It&amp;#039;s important to understand that (currently) when changing global presets, only the currently selected part&amp;#039;s preset data is stored.  (I&amp;#039;ve tried it the other way, it&amp;#039;s just too darned slow)&lt;br /&gt;
&lt;br /&gt;
===poly record===&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_polyrec.png]]&lt;br /&gt;
&lt;br /&gt;
Poly record mode allows the user to record a sequence of notes via the keys top keys.  The notes will only be played back at their recorded pitch if the selected voice is set to a channel other than &amp;quot;Plug&amp;quot;.  Unfortunately, this limits use of this feature to OSX only....however, I have a solution for Windows user&amp;#039;s coming soon ;)&lt;br /&gt;
&lt;br /&gt;
===poly play===&lt;br /&gt;
&lt;br /&gt;
[[File:hex_polyplay.png]]&lt;br /&gt;
&lt;br /&gt;
Poly play mode allows the user to play back the current sequence immediatedly, ala Polygome.  Each of the top keys represent a base note, and pressing it will start the sequence playing independent of the current time position, with its root based on the note pressed, and locked to the current mode setting.  It&amp;#039;s also important to recognize that the Poly Offset parameter is useful here, since otherwise the sequence base note will be C-2.&lt;br /&gt;
&lt;br /&gt;
==The Encoders==&lt;br /&gt;
&lt;br /&gt;
Hex is capable of latching to the controls of multiple different instruments in your Live set.  I&amp;#039;ve done my best to make it capable of being both a Drum-based beat programmer as well as a semi-capable, freewheeling note sequencer for use with other instruments.  Because of this, things get a little tricky here.&lt;br /&gt;
&lt;br /&gt;
When you open hex for the first time, it should be in its default mode, or &amp;quot;Plug&amp;quot; mode.  This means that its output is sent to the m4l plugins output.  You can either place a DrumRack after it or send the tracks output to another track containing a DrumRack that you want hex to play.  If hex does not automatically detect the DrumRack you wish it&amp;#039;s encoders to control, it will look something like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_detect_instrument.png]]&lt;br /&gt;
&lt;br /&gt;
Don&amp;#039;t worry, all  is not lost.  Just press the button that says &amp;quot;Detect Instrument&amp;quot;.  A little window will be floated on your screen, that looks like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_detect_float.png]]&lt;br /&gt;
&lt;br /&gt;
Select the DrumRack you wish to control (the &amp;quot;Blue Hand&amp;quot; should appear on it, and it should be hilighted), and then press the button in the float.  The CNTRL:R&amp;#039;s encoder rings should immediately update to reflect the currently selected part&amp;#039;s parameters.&lt;br /&gt;
&lt;br /&gt;
Your GUI should look something like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_encoders.png]]&lt;br /&gt;
&lt;br /&gt;
If you&amp;#039;re not happy with the parameters that hex uses, just group the instrument and assign the macros to the parameters that you wish to control.  Hex will happily lock to them instead.&lt;br /&gt;
&lt;br /&gt;
When you&amp;#039;re ready to go further and explore some new madness, turn the &amp;quot;Channel&amp;quot; encoder to something besides &amp;quot;Plug&amp;quot;.  In addition to the plugin&amp;#039;s output, hex can transmit your part to one of sixteen MIDI channels.  Hex stores a different device for each MIDI channel.  In this way, you can quickly assign a single note sequence that is outputting to your DrumRack to an instrument in a completely different place in your set, and it will start playing whatever multi-note pattern you&amp;#039;ve recorded in that track.&lt;br /&gt;
&lt;br /&gt;
You can change the channel that the part is assigned to by turning the channel encoder:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_channel.png]]&lt;br /&gt;
&lt;br /&gt;
There are a few caveats here.  As mentioned earlier, this only currently works on OSX.  You&amp;#039;ll need to create an IAC loop passthrough by doing the following:&lt;br /&gt;
&lt;br /&gt;
1.  Create an IAC Bus in OSX&amp;quot;s &amp;quot;Audio MIDI Setup&amp;quot;.  &lt;br /&gt;
&lt;br /&gt;
2.  Make sure the IAC Bus&amp;#039;s port is set for &amp;quot;Track&amp;quot; (both input and output) in Live&amp;#039;s MIDI Preferences.&lt;br /&gt;
&lt;br /&gt;
2.  Open hex&amp;#039;s Settings and assign that IAC Bus as the &amp;quot;Poly Output Port&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
3.  Assign the instrument you want to control to Hex in the same manner you did with the DrumRack.  You&amp;#039;ll need to do this once for each of the sixteen channels, but the settings will be stored with your project unless you delete the controlled instrument at some point.  &lt;br /&gt;
&lt;br /&gt;
4.  Set the MIDI input port of the destination instrument&amp;#039;s track to the IAC Bus you&amp;#039;ve created, and set its Channel input to the channel you assigned the instrument to in hex.&lt;br /&gt;
&lt;br /&gt;
Once you have assigned an instrument to one of hex&amp;#039;s individual channels, the display should look like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Hex_encoders2.png]]&lt;br /&gt;
&lt;br /&gt;
Notice that there are some differences.  Hex only controls 4 parameters of the target instrument (on the top 4 encoders).  On the second row of encoders, PolyOffset and Mode have replaced the &amp;quot;Plug&amp;quot;s parameter assignments.  &lt;br /&gt;
&lt;br /&gt;
PolyOffset is the base note of your sequence. &lt;br /&gt;
&lt;br /&gt;
Mode is the scale mode which the sequence will use.&lt;br /&gt;
&lt;br /&gt;
For perhaps a better explanation of how this works, see the video:&lt;br /&gt;
&lt;br /&gt;
[[Placeholder]]&lt;br /&gt;
&lt;br /&gt;
==Other Controls==&lt;br /&gt;
&lt;br /&gt;
The modVolume dial controls the master output of the entire patch.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Mode&amp;quot; button steps through all available Key modes, making it easy to work in a different way.&lt;br /&gt;
&lt;br /&gt;
==Wheel Syncing==&lt;br /&gt;
&lt;br /&gt;
It is easy to synchronize the speed of two different parts.  Select the part to which you want to synchronize, and while holding down its button, press the button corresponding to the sequence you wish to change.&lt;br /&gt;
&lt;br /&gt;
==Automation==&lt;br /&gt;
&lt;br /&gt;
Hex allows recording of automation directly to a clip that is playing or recording on the track it&amp;#039;s on.  To enable this, either create a MIDI clip on its track and start playing it, or start recording a new clip on its track.  Then, press the REC button on its UI.  Any &amp;quot;mute&amp;quot; or &amp;quot;single preset&amp;quot; changes that you make will be recorded in the clip as you make them.&lt;br /&gt;
&lt;br /&gt;
In order to play back this data, just play the clip and make sure that PLAY is turned on in the UI.  You can have both PLAY and REC enabled at the same time in order to overdub new changes (however, this will not currently erase older data).  &lt;br /&gt;
&lt;br /&gt;
Hex uses note-based automation.  It&amp;#039;s important to understand a little about this:  any note event arriving at the mod&amp;#039;s input can be interpreted as automation data.  Hex reserves note numbers above 113 for use with automation.  As long as &amp;quot;Play&amp;quot; is not enabled, nothing dire will happen.  However, be sure not to send unintentional notes to Hex when it&amp;#039;s in play mode, or some wacky things will probably happen.  Any notes below its automation range will just be passed through to hex&amp;#039;s output.&lt;br /&gt;
&lt;br /&gt;
===Behaviors===&lt;br /&gt;
&lt;br /&gt;
In order to create more variability in a sequence&amp;#039;s sound, you can assign behaviors to each step of a sequence.  This allows changing how a step acts over the space of 8 bars of 16 beats.  &lt;br /&gt;
&lt;br /&gt;
There are seven user definable behaviors.  They can be assigned in the advanced settings.  Each behavior has 8 steps.  Each step corresponds to one cycle of a loops sequence.  &lt;br /&gt;
&lt;br /&gt;
By default, each behavior is filled with one type of action.  This can be changed by clicking on the Behavior grid in the settings menu.  The available actions are:&lt;br /&gt;
&lt;br /&gt;
1)  No Action.  When no action is chosen, nothing will be played on the assigned cycle even if a step is active in the sequence the behavior is assigned to.&lt;br /&gt;
&lt;br /&gt;
2) Trigger.  When trigger is chosen, if a step is active on the assigned cycle, a note will be played in the sequence the behavior is assigned to.&lt;br /&gt;
&lt;br /&gt;
3) Random.  When random is chosen, the step may or may not trigger a note based on chance.  In addition, the corresponding &amp;#039;rulebend&amp;#039; for the step determines the how likely the note will trigger.&lt;br /&gt;
&lt;br /&gt;
4) Sympathy.  If another rulebend in the current step of any other sequence is equal to the currently selected sequence step&amp;#039;s rulebend, the note will play.&lt;br /&gt;
&lt;br /&gt;
5) Dominate.  If active, the note will play.  In addition, it will mute any other notes played by other sequences unless those sequences are also set to dominate.  The length of dominance is determined by the corresponding step&amp;#039;s rulebend value.&lt;br /&gt;
&lt;br /&gt;
6) Delay.  If active, the note will play, but a delay will occur before it is triggered corresponding to that steps rulebend value.&lt;br /&gt;
&lt;br /&gt;
7) Repeat.  If active, the note will play, and will be repeated.  The interval and number of repeats is determined by the rulebend value.&lt;br /&gt;
&lt;br /&gt;
8) Plink.  This will start a particle in any Plinko mod that is currently in the set.  The rulebend determines the direction of the particle.  The particle will appear in the square corresponding to the part(x-coordinate) and the step(y-coordinate).&lt;br /&gt;
&lt;br /&gt;
===Advanced Settings===&lt;br /&gt;
&lt;br /&gt;
[[File:Hex pic settings.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Select + Hold Temporarily Reveals:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Changing this setting allows cusomization of what mode Quick-view snaps to.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Timing Changes Happen:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
If set to &amp;quot;immediately&amp;quot;, quantized changes will happen when they are made.  Otherwise, timing changes will not be triggered until the beginning of the part&amp;#039;s next loop.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Global Chain Offset&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
This one&amp;#039;s important.  And a little tricky.  All you need to know:  set this value to the lowest note in your DrumRack, and don&amp;#039;t allow any gaps in the your Rack.  You can always insert an empty InstrumentRack in blank spaces, but there can&amp;#039;t be any gaps or the parameter controls will not lock to the correct chain when you select a new sequence. &lt;br /&gt;
&lt;br /&gt;
Because there is no way to determine the note-assignment of a DrumRack&amp;#039;s chain, it is necessary to order your DrumRack with no gaps.  It&amp;#039;s not important which note it starts on, but if you start at a note higher than 0 (C-2), you&amp;#039;ll need to compensate for chain detection by changing this setting.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Transpose Steps&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
You can change the number of steps that are changed when using the &amp;quot;-1st&amp;quot; and &amp;quot;+1st&amp;quot; encoder buttons by changing this value.  &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Capture Currently Selected Instrument&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If you wish to use Hex with an instrument or DrumRack that is not immediately adjacent to it, you can select the instrument you wish to control in Live and then press this button.  Hex will detect the new instrument, and should store it&amp;#039;s id for your concurrent sessions.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;MIDI Remote Assignment&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
You can use Live&amp;#039;s MIDI Learn functionality to assign any controller to the CNTRL:R&amp;#039;s controls.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Initialize Preset&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Clear the currently selected preset&amp;#039;s data.  This clears all sequences in the currently selected preset slot, not just the selected sequence.&lt;br /&gt;
&lt;br /&gt;
In order to clear all presets in all sequences, make sure the &amp;quot;Global&amp;quot; button is active in the Randomize section below, then press the Initialize Preset button.  It&amp;#039;ll take a few seconds.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Behaviors&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Assign new actions for each type of behavior by clicking the squares on the grid.  Each step will cycle through all available actions.&lt;br /&gt;
&lt;br /&gt;
You can use the Randomize button in the top right corner to shake things up a bit.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Randomize&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Randomize individual data types for the current global preset.  You can randomize all data types in the current preset by pressing the &amp;quot;All&amp;quot; button.&lt;br /&gt;
&lt;br /&gt;
If &amp;quot;Global&amp;quot; is active, any randomization or initialization changes will affect all global presets (that means every single preset in every single sequence).  Be carefull....it takes a little while.&lt;br /&gt;
&lt;br /&gt;
=Known Issues and Bugs=&lt;br /&gt;
&lt;br /&gt;
Read and Write (via pattrstorage) are currently broken.  I&amp;#039;m looking into this.&lt;br /&gt;
&lt;br /&gt;
Freewheel is currently not functioning correctly.  This was working in the prototypes (as it works in &amp;quot;binary&amp;quot;, as well), but due to some last minute bugs that cropped up I had to disable some of this mode&amp;#039;s functionality in order to promote better timing for the rest of the patch.  It will be back to normal in an update, hopefully soon.&lt;br /&gt;
&lt;br /&gt;
In addition, freewheel encoder rings are not getting updated properly when changing presets or initializing the patch.  You will have to manually select a part before its encoder ring display correctly updates.&lt;br /&gt;
&lt;br /&gt;
In Freewheel mode, the bottom encoder rings do not currently light to display the value being controlled.&lt;br /&gt;
&lt;br /&gt;
Automation rec/play currently only supports the mutes and single preset changes.  This will probably see more additions later if it proves to be truly useful.&lt;br /&gt;
&lt;br /&gt;
=Technology=&lt;br /&gt;
&lt;br /&gt;
Here are the header comments from the core js file, which might give a little more food for your curiousity:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;This script is the result of collaboration with Peter Nyboer @ Livid Instruments and represents a great deal of effort to gain some speed and stability from the original Steppr without sacrificing too much readability.  The majority of the functionality for the entire patch can be modified in this js or the accompanying poly~ object, &amp;quot;steppr_wheel&amp;quot;, without ever opening the actual containing patch in the m4l editor (this is crucial for speeding up the development process).  Because of this, the functionality of the patch can be radically altered merely by modifying the poly~ or adding some lines of code in to this js.  As an example, the poly~ used as the base for this patch is only a slightly modified version of the &amp;quot;binary&amp;quot; mod (from Monomodular), and the majority of processes in this script are maintained between both versions.&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Although the original ideas came from the Stepp:rs, this patch is in fact a complete recoding of those ideas.&lt;br /&gt;
&lt;br /&gt;
More to come shortly....&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Manual_Installation&amp;diff=671</id>
		<title>Manual Installation</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Manual_Installation&amp;diff=671"/>
		<updated>2012-11-28T20:55:51Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Control Surface Scripts */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back in the old days, we had to put all this stuff where it went on our own.  &lt;br /&gt;
&lt;br /&gt;
If you would like to remove files from old installations or manually install the Installation Package, here is some help to keep you in line.&lt;br /&gt;
&lt;br /&gt;
== Mods ==&lt;br /&gt;
&lt;br /&gt;
All of the m4l patches that accompany the static build of Monomodular (i.e. the frozen version) should be placed in Live&amp;#039;s Presets Library under MIDI Effects/.  It is easiest to do this from the desktop:  Take the folder labeled Monomodular_bxxx and drag it on top of the Max MIDI Effect folder in Live&amp;#039;s browser, then drop it there.  All the patches inside it should be copied into your library.&lt;br /&gt;
&lt;br /&gt;
The default paths for Live&amp;#039;s Library are:&lt;br /&gt;
&lt;br /&gt;
MacOS = ~/Library/Preferences/Live 8.x.x/Library/Presets/MIDI Effects/Max MIDI Effect&lt;br /&gt;
&lt;br /&gt;
&amp;lt;= Windows XP =\Documents and Settings\USER\Documents\Ableton\Library\Presets\MIDI Effects\Max MIDI Effect&lt;br /&gt;
&lt;br /&gt;
Windows 7+ = \users\username\documents\ableton\Library\Presets\MIDI Effects\Max MIDI Effect&lt;br /&gt;
&lt;br /&gt;
== Python Scripts ==&lt;br /&gt;
 &lt;br /&gt;
All of the control surface scripts should be placed inside the &amp;quot;MIDI Remote Scripts&amp;quot; folder. &lt;br /&gt;
&lt;br /&gt;
This folder resides inside the Live.app bundle on OSX (ctrl-click the Live app, then select &amp;#039;Show Package Contents&amp;#039; in order to navigate to the right place.  Once inside, the path is: /Contents/App-Resources/MIDI Remote Scripts/).  &lt;br /&gt;
&lt;br /&gt;
On Windows, this process is a little simpler.  The default file paths for the Remote Scripts folder are detailed on the [[Installation]] page.&lt;br /&gt;
&lt;br /&gt;
Make sure NOT to move the entire &amp;#039;Python Scripts&amp;#039; folder from the Installation Package.  You must move only the folders inside it to the new location, or they will not be recognized correctly by Live when you restart it.&lt;br /&gt;
&lt;br /&gt;
MacOS:  Live.app = ~/Applications/Live 8.x.x/Live.app/Resources\MIDI Remote Scripts&lt;br /&gt;
&lt;br /&gt;
Windows:   Live Folder =\Program Files\Ableton\Live 8.2.2\Resources\MIDI Remote Scripts&lt;br /&gt;
&lt;br /&gt;
== Java ==&lt;br /&gt;
&lt;br /&gt;
There are a couple of files required by Boinng, Plinko, and Aumboids that must be place inside the Cycling &amp;#039;74 folder.  The default location for the Max installation is detailed on the [[Installation]] page.  Once in that location, you will need to navigate to /Cycling &amp;#039;74/java/classes/, and there place the files from the Java folder from the Monomodular Installation Package.&lt;br /&gt;
&lt;br /&gt;
MacOS = ~/Applications/Max 5/java/classes&lt;br /&gt;
&lt;br /&gt;
Windows = \Program Files\Cycling &amp;#039;74\Max 5.x\java\classes&lt;br /&gt;
&lt;br /&gt;
== aumhaa_blocks ==&lt;br /&gt;
&lt;br /&gt;
These are support files needed by the patches.  Depending on how you received the package (direct download or SVN), it&amp;#039;s contents will be different.&lt;br /&gt;
&lt;br /&gt;
When downloading via SVN, this folder will contain additional resources for opening the unfrozen patch versions that are included in Live&amp;#039;s library installation.  &lt;br /&gt;
&lt;br /&gt;
These files can be placed anywhere as long as you add the location to your search path in Max&amp;#039;s file preferences.  However, its easiest to just place them inside the &amp;quot;patches&amp;quot; folder in your Max installation, since it is already part of the search path.&lt;br /&gt;
&lt;br /&gt;
If are getting errors in Max&amp;#039;s status window, or there is no &amp;quot;wood block&amp;quot; display on the top right of your patches, these files aren&amp;#039;t in the right place.  There are graphics files inside the aumhaa_blocks folder that I&amp;#039;m unable to compile with the patches, and this behavior indicates that Max can&amp;#039;t find them in their current location.  Make sure they are inside Max&amp;#039;s search path.&lt;br /&gt;
&lt;br /&gt;
MacOS = ~/Applications/Max 5/patches&lt;br /&gt;
&lt;br /&gt;
Windows = \Program Files\Cycling &amp;#039;74\Max 5.x\patches&lt;br /&gt;
&lt;br /&gt;
== Monomodular ==&lt;br /&gt;
&lt;br /&gt;
This folder contains several files useful to those using an iPad with TouchOSC or Lemur.  If you don&amp;#039;t have one, then you won&amp;#039;t need them.  Otherwise, you&amp;#039;ll need to put them on your iOS device in order to use the AumPad or Aum256 Python scripts.&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Manual_Installation&amp;diff=670</id>
		<title>Manual Installation</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Manual_Installation&amp;diff=670"/>
		<updated>2012-11-28T20:55:04Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Python Scripts */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back in the old days, we had to put all this stuff where it went on our own.  &lt;br /&gt;
&lt;br /&gt;
If you would like to remove files from old installations or manually install the Installation Package, here is some help to keep you in line.&lt;br /&gt;
&lt;br /&gt;
== Mods ==&lt;br /&gt;
&lt;br /&gt;
All of the m4l patches that accompany the static build of Monomodular (i.e. the frozen version) should be placed in Live&amp;#039;s Presets Library under MIDI Effects/.  It is easiest to do this from the desktop:  Take the folder labeled Monomodular_bxxx and drag it on top of the Max MIDI Effect folder in Live&amp;#039;s browser, then drop it there.  All the patches inside it should be copied into your library.&lt;br /&gt;
&lt;br /&gt;
The default paths for Live&amp;#039;s Library are:&lt;br /&gt;
&lt;br /&gt;
MacOS = ~/Library/Preferences/Live 8.x.x/Library/Presets/MIDI Effects/Max MIDI Effect&lt;br /&gt;
&lt;br /&gt;
&amp;lt;= Windows XP =\Documents and Settings\USER\Documents\Ableton\Library\Presets\MIDI Effects\Max MIDI Effect&lt;br /&gt;
&lt;br /&gt;
Windows 7+ = \users\username\documents\ableton\Library\Presets\MIDI Effects\Max MIDI Effect&lt;br /&gt;
&lt;br /&gt;
== Control Surface Scripts ==&lt;br /&gt;
 &lt;br /&gt;
All of the Python control surface scripts should be placed inside the &amp;quot;MIDI Remote Scripts&amp;quot; folder. &lt;br /&gt;
&lt;br /&gt;
This folder resides inside the Live.app bundle on OSX (ctrl-click the Live app, then select &amp;#039;Show Package Contents&amp;#039; in order to navigate to the right place.  Once inside, the path is: /Contents/App-Resources/MIDI Remote Scripts/).  &lt;br /&gt;
&lt;br /&gt;
On Windows, this process is a little simpler.  The default file paths for the Remote Scripts folder are detailed on the [[Installation]] page.&lt;br /&gt;
&lt;br /&gt;
Make sure NOT to move the entire &amp;#039;Python Scripts&amp;#039; folder from the Installation Package.  You must move only the folders inside it to the new location, or they will not be recognized correctly by Live when you restart it.&lt;br /&gt;
&lt;br /&gt;
MacOS:  Live.app = ~/Applications/Live 8.x.x/Live.app/Resources\MIDI Remote Scripts&lt;br /&gt;
&lt;br /&gt;
Windows:   Live Folder =\Program Files\Ableton\Live 8.2.2\Resources\MIDI Remote Scripts&lt;br /&gt;
&lt;br /&gt;
== Java ==&lt;br /&gt;
&lt;br /&gt;
There are a couple of files required by Boinng, Plinko, and Aumboids that must be place inside the Cycling &amp;#039;74 folder.  The default location for the Max installation is detailed on the [[Installation]] page.  Once in that location, you will need to navigate to /Cycling &amp;#039;74/java/classes/, and there place the files from the Java folder from the Monomodular Installation Package.&lt;br /&gt;
&lt;br /&gt;
MacOS = ~/Applications/Max 5/java/classes&lt;br /&gt;
&lt;br /&gt;
Windows = \Program Files\Cycling &amp;#039;74\Max 5.x\java\classes&lt;br /&gt;
&lt;br /&gt;
== aumhaa_blocks ==&lt;br /&gt;
&lt;br /&gt;
These are support files needed by the patches.  Depending on how you received the package (direct download or SVN), it&amp;#039;s contents will be different.&lt;br /&gt;
&lt;br /&gt;
When downloading via SVN, this folder will contain additional resources for opening the unfrozen patch versions that are included in Live&amp;#039;s library installation.  &lt;br /&gt;
&lt;br /&gt;
These files can be placed anywhere as long as you add the location to your search path in Max&amp;#039;s file preferences.  However, its easiest to just place them inside the &amp;quot;patches&amp;quot; folder in your Max installation, since it is already part of the search path.&lt;br /&gt;
&lt;br /&gt;
If are getting errors in Max&amp;#039;s status window, or there is no &amp;quot;wood block&amp;quot; display on the top right of your patches, these files aren&amp;#039;t in the right place.  There are graphics files inside the aumhaa_blocks folder that I&amp;#039;m unable to compile with the patches, and this behavior indicates that Max can&amp;#039;t find them in their current location.  Make sure they are inside Max&amp;#039;s search path.&lt;br /&gt;
&lt;br /&gt;
MacOS = ~/Applications/Max 5/patches&lt;br /&gt;
&lt;br /&gt;
Windows = \Program Files\Cycling &amp;#039;74\Max 5.x\patches&lt;br /&gt;
&lt;br /&gt;
== Monomodular ==&lt;br /&gt;
&lt;br /&gt;
This folder contains several files useful to those using an iPad with TouchOSC or Lemur.  If you don&amp;#039;t have one, then you won&amp;#039;t need them.  Otherwise, you&amp;#039;ll need to put them on your iOS device in order to use the AumPad or Aum256 Python scripts.&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=How_to_use_the_Ohm64_script&amp;diff=669</id>
		<title>How to use the Ohm64 script</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=How_to_use_the_Ohm64_script&amp;diff=669"/>
		<updated>2012-11-28T20:53:54Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Some Video Tutorials ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=9ypoR7JH1cY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=8&amp;amp;feature=plcp  Earliest tutorial with old help patcher and little commentary]&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=00mlz1DpUTY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=7&amp;amp;feature=plcp b99 Release tutorial]&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
&lt;br /&gt;
The only component that is strictly necessary to get the Remote Script working in Ableton is the MonOhm Script itself.  It goes in the Live Application Bundle, in the &amp;quot;Remote Scripts&amp;quot; folder. &lt;br /&gt;
&lt;br /&gt;
If you&amp;#039;re using the Monomodular installer (see:  [[Installation]]), this should take care of itself. If you&amp;#039;re installing just the MonOhm script  (see:  [[Manual_Installation]]), here&amp;#039;s where it goes:&lt;br /&gt;
&lt;br /&gt;
*Macintosh – Right click on the Ableton Live application icon and select &amp;quot;show package contents&amp;quot;. Put the MonOhm folder in Contents/App-Resources/MIDI Remote Scripts&lt;br /&gt;
*Windows - put the MonOhm folder in C:\Program Files\Ableton\Live 8.x.x\Resources\MIDI Remote Scripts&lt;br /&gt;
&lt;br /&gt;
In order to use the Monomodular portion of the script, it is necessary to have Max5.18 installed, and the client plugins that are contained in the suite. Monomodular&amp;#039;s functionality in a seperate place (see:  [[How_Monomodular_Works]]).&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
The Ohm64 script (aka &amp;quot;MonOhm&amp;quot;) consists of three independent mixers.  Two of them control four channels at a time, the third mixer uses all 8 faders to control 8 channels.&lt;br /&gt;
&lt;br /&gt;
Each mixer is independent, and remembers the last tracks that were assigned to it.  When the Ohm64 is first connected to Live, it will automatically be in split mixer mode.  If there are more than four tracks in the project, the mixer will be assigned to the first 8 tracks, otherwise both sides of the mixer will be assigned to whatever tracks are present. &lt;br /&gt;
&lt;br /&gt;
Since there are several different &amp;quot;shift modes&amp;quot; available within the script, the most important concept to grasp about this scheme is that there are two shift buttons:  one left, and one right.  They are on either side of the crossfader.  By holding down the shift button, you gain access to a bunch of different alternative functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Pete @Livid says this script melts peoples&amp;#039; brains.  Really, its not all that complicated.  I tried to fit as much functionality as I could into what was available on the controller, and I can understand why that&amp;#039;s intimidating.  But its very hard to get lost unless you insist on pressing more than one button at a time without knowing what the combination is going to do.  Make this thine performance mantra:  &amp;#039;I shall not press two buttons at once until I understand....&amp;#039;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Note: If you have Max4Live, I highly recommend using a copy of the LCD patch; in addition to letting you know at all times what it is that you are controlling, it will also tell you precisely what the values of your parameters are (in plainspeak, not MIDIeze). &amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== The Grid ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_assign_main.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rows 1-5:  Fire Session Clips&lt;br /&gt;
&lt;br /&gt;
Row 6:  Mute&lt;br /&gt;
&lt;br /&gt;
Row 7:  Solo&lt;br /&gt;
&lt;br /&gt;
Row 8:  Arm&lt;br /&gt;
&lt;br /&gt;
Exception:  When in Right Mixer Mode 4, The right side of the Grid is mapped to DrumRacks (Pad Translation;  see below**).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Shifted Grid ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments with Right Shift button pressed:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_shift_l.png]] &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments with Right Shift button pressed:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_shift_r.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rows 1-5(except for column 8):  Session Zoom Navigation&lt;br /&gt;
&lt;br /&gt;
Row 6:  Record, Overdub, Loop, Stop All Clips, Zero All Sends 1-4&lt;br /&gt;
&lt;br /&gt;
Row 7: Crossfader Assignment&lt;br /&gt;
&lt;br /&gt;
Row 8: Stop Clip&lt;br /&gt;
&lt;br /&gt;
Column 8 (Rows 1-5):  Fire Scene&lt;br /&gt;
&lt;br /&gt;
By holding down one of the shifts and pressing one of the channel select buttons on the same side of the controller, you can enter a different &amp;quot;Shift Mode&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Modes ==&lt;br /&gt;
&lt;br /&gt;
=== For the Left Mixer, Modes 1-4 ===&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Faders are always mapped to Track Volume (or MIDI Velocity...see below****).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm_func1_l.png‎|180px|thumb|left]] &lt;br /&gt;
|Left Mode 1:  Left Dials(top 8) control selected Device, Left Dials (bottom 4) control Selected Track&amp;#039;s Sends.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_l_func2.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 2:  Left Dials control Sends 1-3 for the corresponding Fader&amp;#039;s Track.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func3_l.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 3:  Left Dials (top 8) control Track Filter for corresponding Fader, Left Dials (bottom 4) control Pan for corresponding Fader.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func4_l.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 4:  Left Dials are remapped to channel 2 so that they are User Mappable with Live.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For the Right Mixer, Modes 1-4 ===&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm func1 2 3 r.png|180px|thumb|left]]&lt;br /&gt;
|Right Mode 1:  Faders control Track Volume, Mixer offset at Track 5, Right Dials control Returns 1-4.&lt;br /&gt;
&lt;br /&gt;
Right Mode 2:  Faders control Track Volume, Mixer offset at Track 9, Right Dials control Returns 1-4.&lt;br /&gt;
&lt;br /&gt;
Right Mode 3:  Faders control Track Volume, Mixer offset at Track 13, Right Dials control Returns 1-4. &lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func4_r.png|180px|thumb|left]]&lt;br /&gt;
|Right Mode 4:  Faders control Return Volume, Right Dials control Return Pan&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Buttons below the Faders select Track in all modes (except when shift is being held...see below*).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Functions ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Function Buttons (top right) have the following functions (top left to bottom right):&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm function assign.png|200px|thumb|left]] &lt;br /&gt;
|Session Nav up, Play, Stop, Session Nav down,  Session Nav left, Session Nav right.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Function Buttons (top right) have the following Shifted functions (top left to bottom right):&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm function assign shift.png|200px|thumb|left]] &lt;br /&gt;
|Device Bank up, Device ON/OFF, Device Lock, Device Bank down, Device Nav left, Device Nav right.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WHILE LEFT SHIFT IS PRESSED, FADER 8 CONTROLS MASTER VOLUME.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WHILE LEFT SHIFT IS PRESSED, RIGHT DIAL 4 CONTROLS PREHEAR.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
(Master/Prehear functionality can be defeated in the MonOhm_Map.py file....it has fubarred me several times when things are lagging, so its not necessarily recommended for performance situations)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== modMode ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm modGrid.png]]&lt;br /&gt;
&lt;br /&gt;
The Livid button (aka &amp;quot;Gary the Welder&amp;quot;) switches the grid to Monomodular Mode (aka &amp;quot;modMode&amp;quot;).  Most of the controls remain the same, but the grid is now used for controlling Monomodular patches. &lt;br /&gt;
&lt;br /&gt;
When in modMode, the Function buttons (unShifted) control the following(top left to bottom right):&lt;br /&gt;
&lt;br /&gt;
Grid Nav up, Lock (the bottom row of the grid remains &amp;#039;Shifted&amp;#039;), Alt (access to Preset management in enabled patches...see below*****), Grid Nav down, Grid Nav right, Grid Nav left.&lt;br /&gt;
&lt;br /&gt;
When in modMode, the Function buttons (Shifted) control the following(top left to bottom right).&lt;br /&gt;
&lt;br /&gt;
Device Bank up, Play, Stop, Device Bank down, Device Nav left, Device Nav right.&lt;br /&gt;
&lt;br /&gt;
Track selection and Mode navigation is identical in Monomodular Mode as in normal Session Mode.&lt;br /&gt;
&lt;br /&gt;
By pressing either of the shift buttons, Zoom mode is invoked.  In Zoom mode, the center lit square of buttons indicates the current selected quadrant.  By pressing an area of that square, the grid changes assignment to the corresponding area.  &lt;br /&gt;
&lt;br /&gt;
In Zoom mode, the top row of buttons selects the current Monomodular plugin.  The second row of buttons selects the channel that plugin transmits on (this is only useful when the plugins &amp;#039;nomeout&amp;#039; is enabled...see below*****).  The bottom row of buttons transmits &amp;#039;Key&amp;#039; data (these buttons have special functionality specific to each Monomodular client...see the documenation with the client to find out what they do).&lt;br /&gt;
&lt;br /&gt;
For further info on modMode, see the section on [[How_Monomodular_Works]].&lt;br /&gt;
&lt;br /&gt;
== Linked Mixer Mode ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_linked_mixer.png]]&lt;br /&gt;
&lt;br /&gt;
By holding one shift button and pressing the other, it is possible to link both mixers so they behave like a single one. In linked mode, all mode changes correspond to the descriptions of the Left Mixer, and the right dials remain locked to the Returns.  It is still possible to access the Master/Prehear levels by pressing Right Shift.  The linked mixer&amp;#039;s position (i.e. track assignment) will be recalled independently from the other two mixers, thus allowing easy navigation between 16 tracks by the press of two buttons.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Footnotes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt; Channel Select buttons (buttons below the Faders) operate differently depending upon which Shift button is pressed.  While the left-side Shift is pressed, or when the Mixer is LINKED, the left 4 buttons select a new &amp;#039;Shift Mode&amp;#039;, while the right 4 buttons select a preset Device 5-8 (see below***).  When the right-side Shift is pressed, this behavior is reversed(i.e. preset Devices 1-4 on left, Mode on right).  &lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;**&amp;lt;/nowiki&amp;gt; Pad Translation works by reassigning the Channel/Identifier of each button.  In order to use it with Drum Racks, you must enable &amp;#039;Track Input&amp;#039; for the Ohm64&amp;#039;s MIDI Control Input, and assign that input as the source for the DrumRack&amp;#039;s input.  By default, Pad Translation transmits on MIDI Channel 10, but you can reassign this in the MonOhm_Map.py file to your liking.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;***&amp;lt;/nowiki&amp;gt; preset Device selection allows the user to select a predefined device instantly for editing with the Device knobs.  In order for this functionality to work, the Device must be renamed so that its first two characters are p1 thru p8.  Once named properly, the device may be selected by holding down a shift button and pressing one of the Channel Select buttons on the opposite side of the Ohm64 (e.g.  a device named &amp;#039;p1 Dub Delay&amp;#039; can be selected by holding down the right shift button and pressing the channel select underneath the 1st left side fader).&lt;br /&gt;
&lt;br /&gt;
[[File:Preset_example.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;****&amp;lt;/nowiki&amp;gt; when a Velocity plugin is inserted on a MIDI Track as the first plugin, any Fader currently controlling that Track will lock to its &amp;#039;Out Hi&amp;#039; parameter.  This allows the user to control the Volume of a MIDI only track.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*****&amp;lt;/nowiki&amp;gt; the Key buttons have specific functionality for each Monomodular client.  Generally, the first four control some aspect of the plugins operation, while the second four control the timing of the plugin.  However, see the individual helpfile contained in the client to find out exactly what they do for each one.  The Key buttons may be &amp;#039;Locked&amp;#039;, so that they are always accessible, by pressing the &amp;#039;Lock&amp;#039; button (the top-center Function button when in Monomodular Mode).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
phewww....I think that&amp;#039;s about it.&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Installation&amp;diff=668</id>
		<title>Installation</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Installation&amp;diff=668"/>
		<updated>2012-11-28T20:49:26Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* MacOS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Before installing Monomodular, make sure you have the most current versions of MaxMSP and Ableton Live installed on your computer.  You will also need a license to use MaxforLive (although it is possible to use everything here in Demo Mode).&lt;br /&gt;
&lt;br /&gt;
You may have navigated here from the installer itself, and you&amp;#039;re wondering what its all about.&lt;br /&gt;
&lt;br /&gt;
To install all the Monomodular software, just follow the instructions printed in the console window of the Installer patch.  &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;MAKE SURE LIVE&amp;#039;S AUDIO ENGINE IS TURNED ON BEFORE LOADING THE INSTALLER&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
There are four fields that need to be correct in order for the installation to proceed.  They display the file paths to the locations that the files will be copied on your system.  If they are correct, the field will be white.  If the path couldn&amp;#039;t automatically be found, it will say so in red, and you can locate it manually by either clicking on the text or dropping the file/folder onto the box on the left of the text.  The default paths for the files:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;IF YOU ARE USING WINDOWS 7, SEE BELOW FOR SPECIAL INSTRUCTIONS.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
==Installation Package (all platforms):==&lt;br /&gt;
&lt;br /&gt;
This is the data that the installer will copy to your computer.  If you downloaded the bundle, it should have been autodetected if you launched the installer from inside that bundles folder.  If not, you can either drag the folder from its location to the box on the left side of the text indicating the path, or you can click on the path and choose it from a file browser.&lt;br /&gt;
&lt;br /&gt;
If you are installing from SVN (not available with b993 yet), you must press the &amp;quot;Subversion&amp;quot; button on the right side of the interface, and you will be given a choice of a temp folder where the installer will download the package from its subversion repository.  You can delete this folder manually after the installation is complete, or leave it in place until the next time you update Monomodular with the installer (however, its path is not stored....it will need to be reselected the next time you run the installer).&lt;br /&gt;
&lt;br /&gt;
These are the default locations that the installer is looking for.  Under most circumstances, this is where things will be:&lt;br /&gt;
&lt;br /&gt;
Here&amp;#039;s a video from astarte describing the installation. He&amp;#039;s using a Launchpad with Monomodular in the video:&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=70sBh41X3qw&amp;amp;feature=plcp Astarte&amp;#039;s video]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====MacOS====&lt;br /&gt;
&lt;br /&gt;
Live.app   &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;           = ~/Applications/Live 8.x.x/Live.app&lt;br /&gt;
&lt;br /&gt;
or  &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;                     ~/Applications/Ableton Live 8.app  (version 8.3.x and greater)&lt;br /&gt;
  &lt;br /&gt;
MaxMSP Folder  &amp;amp;nbsp; = ~/Applications/Max 5&lt;br /&gt;
&lt;br /&gt;
Live Library    &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;    = ~/Library/Preferences/Live 8.x.x/Library&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====Windows (pre win7)====&lt;br /&gt;
&lt;br /&gt;
Live Folder        = \Program Files\Ableton\Live 8.x.x&lt;br /&gt;
&lt;br /&gt;
MaxMSP Folder = \Program Files\Cycling &amp;#039;74\Max 5.x&lt;br /&gt;
&lt;br /&gt;
Live Library       =\Documents and Settings\USER\Documents\Ableton&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====Windows 7====&lt;br /&gt;
&lt;br /&gt;
Live Folder = \Program Files\Ableton\Live 8.x.x&lt;br /&gt;
&lt;br /&gt;
MaxMSP Folder = \Program Files\Cycling &amp;#039;74\Max 5.x&lt;br /&gt;
&lt;br /&gt;
Live Library = \users\username\documents\ableton\Library&lt;br /&gt;
&lt;br /&gt;
(see further Win7 specific instructions below)&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Once the installer has verified that the installation paths that you&amp;#039;ve chosen to be valid places to put its files, you can press the &amp;quot;Install&amp;quot; button to begin moving files to their proper places.  The terminal window on the right will indicate exactly what is being sent to the [shell] object in the patch, and if you are on MacOS, the return result from the shell will be displayed.  &lt;br /&gt;
&lt;br /&gt;
The installer will copy its payload to new folders if the correct folders don&amp;#039;t already exist.  For every new revision, a new set of folders will be generated.  This is good and bad.  It means that none your old installation will be harmed, so there will be no &amp;#039;broken&amp;#039; sets when you upgrade.  It also means, however, that if you upgrade as often as revisions are made, you will end up with a bunch of deprecated folders.  For now, you will have to delete these manually.  You can refer to the [[Manual Installation]] page to see what files go where, and what you can delete.  &lt;br /&gt;
&lt;br /&gt;
The good news is that Monomodular takes up very little room, so the only downside is a bitter of clutter (mostly in the Control Surface Scripts folder inside your Live installation....this can be a bit frustrating if you change things around often, but otherwise, is completely harmless).&lt;br /&gt;
&lt;br /&gt;
If you try to install a Monomodular revision over that same revision, the installer will not overwrite any files.  It should, however, replace any files that might have gone missing through erroneous deletion or movement.&lt;br /&gt;
&lt;br /&gt;
Once the installer is finished, it will indicate that you need to restart Live.  So....restart Live already.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====WINDOWS 7 INSTALLATION====&lt;br /&gt;
&lt;br /&gt;
The installer should be able to autodetect the file locations in the b993 installer, but it probably won&amp;#039;t be able to copy them unless you run Live with Administrator priveleges.  You can do this by right-clicking Live&amp;#039;s application and choosing &amp;quot;Run as Administator&amp;quot;.  &lt;br /&gt;
&lt;br /&gt;
However, this causes its own set of difficulties, because you can&amp;#039;t move files into Live by dragging and dropping while its running as Admin.  If you run into these problems, its best to run Live regularly first, drop the installer into Live&amp;#039;s Presets (under Max MIDI Device), then restart Live running it as Admin, and run the installer at that point.  You&amp;#039;ll still have to select the installer payload, but it should autodetect everything else.&lt;br /&gt;
&lt;br /&gt;
Sheesh.&lt;br /&gt;
&lt;br /&gt;
== Limitations ==&lt;br /&gt;
&lt;br /&gt;
All I can really say is:  &amp;#039;&amp;#039;&amp;#039;READ THE DIRECTIONS.&amp;#039;&amp;#039;&amp;#039;  I&amp;#039;ve done my best to make the installation as painless as possible, and I&amp;#039;ve included as much documentation both with the Installer patches and in this Wiki as I can think to.  &lt;br /&gt;
&lt;br /&gt;
That said, this is the first &amp;#039;m4l Native&amp;#039; installer that I&amp;#039;ve seen in the wild, and I&amp;#039;m doing all I can to make it compatible with as many systems as possible.  Worst case scenario with this installer is that you have to choose your own paths before you hit the &amp;quot;Install&amp;quot; button, which still eases the process of having to manually install all of the files.  &lt;br /&gt;
&lt;br /&gt;
The newest installation will get tagged with the revision number (e.g. blahblahb992&amp;#039;&amp;#039;&amp;#039;r030112&amp;#039;&amp;#039;&amp;#039;) , the suffix being the date that it was compiled for release. That means it should add to/overwrite any old data.  &lt;br /&gt;
&lt;br /&gt;
Currently, we&amp;#039;re still testing out the Installer on different systems to see what works and what won&amp;#039;t.  There may be problems with Lion and Win7, because I don&amp;#039;t have an installation of either at the moment and I&amp;#039;m therefore relying on end user input to work out the details.  If you have one of these operating systems and want to help out, please contact me via email and we&amp;#039;ll work on it. &lt;br /&gt;
&lt;br /&gt;
Otherwise, unless your system is &amp;quot;REALLY&amp;quot; weird, the installer should work fine.  I have no experience with trying to install to external partitions, but you should have all this stuff on the root partition anyway. Regardless, let me know how this works out (or doesn&amp;#039;t).&lt;br /&gt;
&lt;br /&gt;
== Python Persistence ==&lt;br /&gt;
&lt;br /&gt;
One of the things I&amp;#039;ve learned about Python and Live recently is that it caches all the modules on load, and likes to fill in the gaps of missing data with what it has cached.  This means if there are more than one module with the same name in its search paths, things can get tricky.  For this reason, I highly recommend that when installing new versions of the betas, you clean out the old ones from your MIDI Remote Scripts directory.  Nine times out of ten it won&amp;#039;t make a bit of difference, but if you&amp;#039;re having problems with things not working the way they are supposed to, it is the first thing I&amp;#039;d try to get things back to normal.&lt;br /&gt;
&lt;br /&gt;
== Live Crashes ==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve experienced on several occasions (in OSX) that the installer will crash Live if the log.txt file is either too long or has bad file references.  If the installer is crashing Live on your system, you might try deleting Live&amp;#039;s log.txt file.  It won&amp;#039;t hurt anything, and its solved the only crashes that I&amp;#039;ve ever encountered using the installer.  Live will create a new log.txt file the next time you start Live, and the installer will be able to do its thing without problems.&lt;br /&gt;
&lt;br /&gt;
== Root Volume ==&lt;br /&gt;
&lt;br /&gt;
Don&amp;#039;t expect the installer to work on Windows if you&amp;#039;ve got your base installation on a drive other than C:\.   It just probably won&amp;#039;t.&lt;br /&gt;
&lt;br /&gt;
== Manual Installation ==&lt;br /&gt;
&lt;br /&gt;
If the installer just doesn&amp;#039;t work for you for whatever reason, you can always put the files where they go manually.  Here&amp;#039;s some more information on how to do that:&lt;br /&gt;
&lt;br /&gt;
[[Manual Installation|Manual Installation]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Installation&amp;diff=667</id>
		<title>Installation</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Installation&amp;diff=667"/>
		<updated>2012-11-28T20:48:47Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* MacOS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Before installing Monomodular, make sure you have the most current versions of MaxMSP and Ableton Live installed on your computer.  You will also need a license to use MaxforLive (although it is possible to use everything here in Demo Mode).&lt;br /&gt;
&lt;br /&gt;
You may have navigated here from the installer itself, and you&amp;#039;re wondering what its all about.&lt;br /&gt;
&lt;br /&gt;
To install all the Monomodular software, just follow the instructions printed in the console window of the Installer patch.  &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;MAKE SURE LIVE&amp;#039;S AUDIO ENGINE IS TURNED ON BEFORE LOADING THE INSTALLER&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
There are four fields that need to be correct in order for the installation to proceed.  They display the file paths to the locations that the files will be copied on your system.  If they are correct, the field will be white.  If the path couldn&amp;#039;t automatically be found, it will say so in red, and you can locate it manually by either clicking on the text or dropping the file/folder onto the box on the left of the text.  The default paths for the files:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;IF YOU ARE USING WINDOWS 7, SEE BELOW FOR SPECIAL INSTRUCTIONS.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
==Installation Package (all platforms):==&lt;br /&gt;
&lt;br /&gt;
This is the data that the installer will copy to your computer.  If you downloaded the bundle, it should have been autodetected if you launched the installer from inside that bundles folder.  If not, you can either drag the folder from its location to the box on the left side of the text indicating the path, or you can click on the path and choose it from a file browser.&lt;br /&gt;
&lt;br /&gt;
If you are installing from SVN (not available with b993 yet), you must press the &amp;quot;Subversion&amp;quot; button on the right side of the interface, and you will be given a choice of a temp folder where the installer will download the package from its subversion repository.  You can delete this folder manually after the installation is complete, or leave it in place until the next time you update Monomodular with the installer (however, its path is not stored....it will need to be reselected the next time you run the installer).&lt;br /&gt;
&lt;br /&gt;
These are the default locations that the installer is looking for.  Under most circumstances, this is where things will be:&lt;br /&gt;
&lt;br /&gt;
Here&amp;#039;s a video from astarte describing the installation. He&amp;#039;s using a Launchpad with Monomodular in the video:&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=70sBh41X3qw&amp;amp;feature=plcp Astarte&amp;#039;s video]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====MacOS====&lt;br /&gt;
&lt;br /&gt;
Live.app   &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;           = ~/Applications/Live 8.x.x/Live.app&lt;br /&gt;
&lt;br /&gt;
or  &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;                     ~/Applications/Ableton Live 8.app  (version 8.3.x and greater)&lt;br /&gt;
  &lt;br /&gt;
MaxMSP Folder  &amp;amp;nbsp; = ~/Applications/Max 5&lt;br /&gt;
&lt;br /&gt;
Live Library    &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;    = ~/Library/Preferences/Live 8.x.x/Library&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====Windows (pre win7)====&lt;br /&gt;
&lt;br /&gt;
Live Folder        = \Program Files\Ableton\Live 8.x.x&lt;br /&gt;
&lt;br /&gt;
MaxMSP Folder = \Program Files\Cycling &amp;#039;74\Max 5.x&lt;br /&gt;
&lt;br /&gt;
Live Library       =\Documents and Settings\USER\Documents\Ableton&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====Windows 7====&lt;br /&gt;
&lt;br /&gt;
Live Folder = \Program Files\Ableton\Live 8.x.x&lt;br /&gt;
&lt;br /&gt;
MaxMSP Folder = \Program Files\Cycling &amp;#039;74\Max 5.x&lt;br /&gt;
&lt;br /&gt;
Live Library = \users\username\documents\ableton\Library&lt;br /&gt;
&lt;br /&gt;
(see further Win7 specific instructions below)&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Once the installer has verified that the installation paths that you&amp;#039;ve chosen to be valid places to put its files, you can press the &amp;quot;Install&amp;quot; button to begin moving files to their proper places.  The terminal window on the right will indicate exactly what is being sent to the [shell] object in the patch, and if you are on MacOS, the return result from the shell will be displayed.  &lt;br /&gt;
&lt;br /&gt;
The installer will copy its payload to new folders if the correct folders don&amp;#039;t already exist.  For every new revision, a new set of folders will be generated.  This is good and bad.  It means that none your old installation will be harmed, so there will be no &amp;#039;broken&amp;#039; sets when you upgrade.  It also means, however, that if you upgrade as often as revisions are made, you will end up with a bunch of deprecated folders.  For now, you will have to delete these manually.  You can refer to the [[Manual Installation]] page to see what files go where, and what you can delete.  &lt;br /&gt;
&lt;br /&gt;
The good news is that Monomodular takes up very little room, so the only downside is a bitter of clutter (mostly in the Control Surface Scripts folder inside your Live installation....this can be a bit frustrating if you change things around often, but otherwise, is completely harmless).&lt;br /&gt;
&lt;br /&gt;
If you try to install a Monomodular revision over that same revision, the installer will not overwrite any files.  It should, however, replace any files that might have gone missing through erroneous deletion or movement.&lt;br /&gt;
&lt;br /&gt;
Once the installer is finished, it will indicate that you need to restart Live.  So....restart Live already.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====WINDOWS 7 INSTALLATION====&lt;br /&gt;
&lt;br /&gt;
The installer should be able to autodetect the file locations in the b993 installer, but it probably won&amp;#039;t be able to copy them unless you run Live with Administrator priveleges.  You can do this by right-clicking Live&amp;#039;s application and choosing &amp;quot;Run as Administator&amp;quot;.  &lt;br /&gt;
&lt;br /&gt;
However, this causes its own set of difficulties, because you can&amp;#039;t move files into Live by dragging and dropping while its running as Admin.  If you run into these problems, its best to run Live regularly first, drop the installer into Live&amp;#039;s Presets (under Max MIDI Device), then restart Live running it as Admin, and run the installer at that point.  You&amp;#039;ll still have to select the installer payload, but it should autodetect everything else.&lt;br /&gt;
&lt;br /&gt;
Sheesh.&lt;br /&gt;
&lt;br /&gt;
== Limitations ==&lt;br /&gt;
&lt;br /&gt;
All I can really say is:  &amp;#039;&amp;#039;&amp;#039;READ THE DIRECTIONS.&amp;#039;&amp;#039;&amp;#039;  I&amp;#039;ve done my best to make the installation as painless as possible, and I&amp;#039;ve included as much documentation both with the Installer patches and in this Wiki as I can think to.  &lt;br /&gt;
&lt;br /&gt;
That said, this is the first &amp;#039;m4l Native&amp;#039; installer that I&amp;#039;ve seen in the wild, and I&amp;#039;m doing all I can to make it compatible with as many systems as possible.  Worst case scenario with this installer is that you have to choose your own paths before you hit the &amp;quot;Install&amp;quot; button, which still eases the process of having to manually install all of the files.  &lt;br /&gt;
&lt;br /&gt;
The newest installation will get tagged with the revision number (e.g. blahblahb992&amp;#039;&amp;#039;&amp;#039;r030112&amp;#039;&amp;#039;&amp;#039;) , the suffix being the date that it was compiled for release. That means it should add to/overwrite any old data.  &lt;br /&gt;
&lt;br /&gt;
Currently, we&amp;#039;re still testing out the Installer on different systems to see what works and what won&amp;#039;t.  There may be problems with Lion and Win7, because I don&amp;#039;t have an installation of either at the moment and I&amp;#039;m therefore relying on end user input to work out the details.  If you have one of these operating systems and want to help out, please contact me via email and we&amp;#039;ll work on it. &lt;br /&gt;
&lt;br /&gt;
Otherwise, unless your system is &amp;quot;REALLY&amp;quot; weird, the installer should work fine.  I have no experience with trying to install to external partitions, but you should have all this stuff on the root partition anyway. Regardless, let me know how this works out (or doesn&amp;#039;t).&lt;br /&gt;
&lt;br /&gt;
== Python Persistence ==&lt;br /&gt;
&lt;br /&gt;
One of the things I&amp;#039;ve learned about Python and Live recently is that it caches all the modules on load, and likes to fill in the gaps of missing data with what it has cached.  This means if there are more than one module with the same name in its search paths, things can get tricky.  For this reason, I highly recommend that when installing new versions of the betas, you clean out the old ones from your MIDI Remote Scripts directory.  Nine times out of ten it won&amp;#039;t make a bit of difference, but if you&amp;#039;re having problems with things not working the way they are supposed to, it is the first thing I&amp;#039;d try to get things back to normal.&lt;br /&gt;
&lt;br /&gt;
== Live Crashes ==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve experienced on several occasions (in OSX) that the installer will crash Live if the log.txt file is either too long or has bad file references.  If the installer is crashing Live on your system, you might try deleting Live&amp;#039;s log.txt file.  It won&amp;#039;t hurt anything, and its solved the only crashes that I&amp;#039;ve ever encountered using the installer.  Live will create a new log.txt file the next time you start Live, and the installer will be able to do its thing without problems.&lt;br /&gt;
&lt;br /&gt;
== Root Volume ==&lt;br /&gt;
&lt;br /&gt;
Don&amp;#039;t expect the installer to work on Windows if you&amp;#039;ve got your base installation on a drive other than C:\.   It just probably won&amp;#039;t.&lt;br /&gt;
&lt;br /&gt;
== Manual Installation ==&lt;br /&gt;
&lt;br /&gt;
If the installer just doesn&amp;#039;t work for you for whatever reason, you can always put the files where they go manually.  Here&amp;#039;s some more information on how to do that:&lt;br /&gt;
&lt;br /&gt;
[[Manual Installation|Manual Installation]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Installation&amp;diff=666</id>
		<title>Installation</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Installation&amp;diff=666"/>
		<updated>2012-11-28T20:48:17Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* MacOS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Before installing Monomodular, make sure you have the most current versions of MaxMSP and Ableton Live installed on your computer.  You will also need a license to use MaxforLive (although it is possible to use everything here in Demo Mode).&lt;br /&gt;
&lt;br /&gt;
You may have navigated here from the installer itself, and you&amp;#039;re wondering what its all about.&lt;br /&gt;
&lt;br /&gt;
To install all the Monomodular software, just follow the instructions printed in the console window of the Installer patch.  &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;MAKE SURE LIVE&amp;#039;S AUDIO ENGINE IS TURNED ON BEFORE LOADING THE INSTALLER&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
There are four fields that need to be correct in order for the installation to proceed.  They display the file paths to the locations that the files will be copied on your system.  If they are correct, the field will be white.  If the path couldn&amp;#039;t automatically be found, it will say so in red, and you can locate it manually by either clicking on the text or dropping the file/folder onto the box on the left of the text.  The default paths for the files:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;IF YOU ARE USING WINDOWS 7, SEE BELOW FOR SPECIAL INSTRUCTIONS.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
==Installation Package (all platforms):==&lt;br /&gt;
&lt;br /&gt;
This is the data that the installer will copy to your computer.  If you downloaded the bundle, it should have been autodetected if you launched the installer from inside that bundles folder.  If not, you can either drag the folder from its location to the box on the left side of the text indicating the path, or you can click on the path and choose it from a file browser.&lt;br /&gt;
&lt;br /&gt;
If you are installing from SVN (not available with b993 yet), you must press the &amp;quot;Subversion&amp;quot; button on the right side of the interface, and you will be given a choice of a temp folder where the installer will download the package from its subversion repository.  You can delete this folder manually after the installation is complete, or leave it in place until the next time you update Monomodular with the installer (however, its path is not stored....it will need to be reselected the next time you run the installer).&lt;br /&gt;
&lt;br /&gt;
These are the default locations that the installer is looking for.  Under most circumstances, this is where things will be:&lt;br /&gt;
&lt;br /&gt;
Here&amp;#039;s a video from astarte describing the installation. He&amp;#039;s using a Launchpad with Monomodular in the video:&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=70sBh41X3qw&amp;amp;feature=plcp Astarte&amp;#039;s video]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====MacOS====&lt;br /&gt;
&lt;br /&gt;
Live.app   &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;           = ~/Applications/Live 8.x.x/Live.app&lt;br /&gt;
&lt;br /&gt;
or  &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;                     ~/Applications/Ableton Live 8.app  (version 8.3.x and greater)&lt;br /&gt;
  &lt;br /&gt;
MaxMSP Folder  &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; = ~/Applications/Max 5&lt;br /&gt;
&lt;br /&gt;
Live Library    &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;     = ~/Library/Preferences/Live 8.x.x/Library&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====Windows (pre win7)====&lt;br /&gt;
&lt;br /&gt;
Live Folder        = \Program Files\Ableton\Live 8.x.x&lt;br /&gt;
&lt;br /&gt;
MaxMSP Folder = \Program Files\Cycling &amp;#039;74\Max 5.x&lt;br /&gt;
&lt;br /&gt;
Live Library       =\Documents and Settings\USER\Documents\Ableton&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====Windows 7====&lt;br /&gt;
&lt;br /&gt;
Live Folder = \Program Files\Ableton\Live 8.x.x&lt;br /&gt;
&lt;br /&gt;
MaxMSP Folder = \Program Files\Cycling &amp;#039;74\Max 5.x&lt;br /&gt;
&lt;br /&gt;
Live Library = \users\username\documents\ableton\Library&lt;br /&gt;
&lt;br /&gt;
(see further Win7 specific instructions below)&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Once the installer has verified that the installation paths that you&amp;#039;ve chosen to be valid places to put its files, you can press the &amp;quot;Install&amp;quot; button to begin moving files to their proper places.  The terminal window on the right will indicate exactly what is being sent to the [shell] object in the patch, and if you are on MacOS, the return result from the shell will be displayed.  &lt;br /&gt;
&lt;br /&gt;
The installer will copy its payload to new folders if the correct folders don&amp;#039;t already exist.  For every new revision, a new set of folders will be generated.  This is good and bad.  It means that none your old installation will be harmed, so there will be no &amp;#039;broken&amp;#039; sets when you upgrade.  It also means, however, that if you upgrade as often as revisions are made, you will end up with a bunch of deprecated folders.  For now, you will have to delete these manually.  You can refer to the [[Manual Installation]] page to see what files go where, and what you can delete.  &lt;br /&gt;
&lt;br /&gt;
The good news is that Monomodular takes up very little room, so the only downside is a bitter of clutter (mostly in the Control Surface Scripts folder inside your Live installation....this can be a bit frustrating if you change things around often, but otherwise, is completely harmless).&lt;br /&gt;
&lt;br /&gt;
If you try to install a Monomodular revision over that same revision, the installer will not overwrite any files.  It should, however, replace any files that might have gone missing through erroneous deletion or movement.&lt;br /&gt;
&lt;br /&gt;
Once the installer is finished, it will indicate that you need to restart Live.  So....restart Live already.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====WINDOWS 7 INSTALLATION====&lt;br /&gt;
&lt;br /&gt;
The installer should be able to autodetect the file locations in the b993 installer, but it probably won&amp;#039;t be able to copy them unless you run Live with Administrator priveleges.  You can do this by right-clicking Live&amp;#039;s application and choosing &amp;quot;Run as Administator&amp;quot;.  &lt;br /&gt;
&lt;br /&gt;
However, this causes its own set of difficulties, because you can&amp;#039;t move files into Live by dragging and dropping while its running as Admin.  If you run into these problems, its best to run Live regularly first, drop the installer into Live&amp;#039;s Presets (under Max MIDI Device), then restart Live running it as Admin, and run the installer at that point.  You&amp;#039;ll still have to select the installer payload, but it should autodetect everything else.&lt;br /&gt;
&lt;br /&gt;
Sheesh.&lt;br /&gt;
&lt;br /&gt;
== Limitations ==&lt;br /&gt;
&lt;br /&gt;
All I can really say is:  &amp;#039;&amp;#039;&amp;#039;READ THE DIRECTIONS.&amp;#039;&amp;#039;&amp;#039;  I&amp;#039;ve done my best to make the installation as painless as possible, and I&amp;#039;ve included as much documentation both with the Installer patches and in this Wiki as I can think to.  &lt;br /&gt;
&lt;br /&gt;
That said, this is the first &amp;#039;m4l Native&amp;#039; installer that I&amp;#039;ve seen in the wild, and I&amp;#039;m doing all I can to make it compatible with as many systems as possible.  Worst case scenario with this installer is that you have to choose your own paths before you hit the &amp;quot;Install&amp;quot; button, which still eases the process of having to manually install all of the files.  &lt;br /&gt;
&lt;br /&gt;
The newest installation will get tagged with the revision number (e.g. blahblahb992&amp;#039;&amp;#039;&amp;#039;r030112&amp;#039;&amp;#039;&amp;#039;) , the suffix being the date that it was compiled for release. That means it should add to/overwrite any old data.  &lt;br /&gt;
&lt;br /&gt;
Currently, we&amp;#039;re still testing out the Installer on different systems to see what works and what won&amp;#039;t.  There may be problems with Lion and Win7, because I don&amp;#039;t have an installation of either at the moment and I&amp;#039;m therefore relying on end user input to work out the details.  If you have one of these operating systems and want to help out, please contact me via email and we&amp;#039;ll work on it. &lt;br /&gt;
&lt;br /&gt;
Otherwise, unless your system is &amp;quot;REALLY&amp;quot; weird, the installer should work fine.  I have no experience with trying to install to external partitions, but you should have all this stuff on the root partition anyway. Regardless, let me know how this works out (or doesn&amp;#039;t).&lt;br /&gt;
&lt;br /&gt;
== Python Persistence ==&lt;br /&gt;
&lt;br /&gt;
One of the things I&amp;#039;ve learned about Python and Live recently is that it caches all the modules on load, and likes to fill in the gaps of missing data with what it has cached.  This means if there are more than one module with the same name in its search paths, things can get tricky.  For this reason, I highly recommend that when installing new versions of the betas, you clean out the old ones from your MIDI Remote Scripts directory.  Nine times out of ten it won&amp;#039;t make a bit of difference, but if you&amp;#039;re having problems with things not working the way they are supposed to, it is the first thing I&amp;#039;d try to get things back to normal.&lt;br /&gt;
&lt;br /&gt;
== Live Crashes ==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve experienced on several occasions (in OSX) that the installer will crash Live if the log.txt file is either too long or has bad file references.  If the installer is crashing Live on your system, you might try deleting Live&amp;#039;s log.txt file.  It won&amp;#039;t hurt anything, and its solved the only crashes that I&amp;#039;ve ever encountered using the installer.  Live will create a new log.txt file the next time you start Live, and the installer will be able to do its thing without problems.&lt;br /&gt;
&lt;br /&gt;
== Root Volume ==&lt;br /&gt;
&lt;br /&gt;
Don&amp;#039;t expect the installer to work on Windows if you&amp;#039;ve got your base installation on a drive other than C:\.   It just probably won&amp;#039;t.&lt;br /&gt;
&lt;br /&gt;
== Manual Installation ==&lt;br /&gt;
&lt;br /&gt;
If the installer just doesn&amp;#039;t work for you for whatever reason, you can always put the files where they go manually.  Here&amp;#039;s some more information on how to do that:&lt;br /&gt;
&lt;br /&gt;
[[Manual Installation|Manual Installation]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=How_to_use_the_Ohm64_script&amp;diff=665</id>
		<title>How to use the Ohm64 script</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=How_to_use_the_Ohm64_script&amp;diff=665"/>
		<updated>2012-11-28T20:46:58Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Some Video Tutorials ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=9ypoR7JH1cY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=8&amp;amp;feature=plcp  Earliest tutorial with old help patcher and little commentary]&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=00mlz1DpUTY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=7&amp;amp;feature=plcp b99 Release tutorial]&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
&lt;br /&gt;
The only component that is strictly necessary to get the Remote Script working in Ableton is the MonOhm Script itself.  It goes in the Live Application Bundle, in the &amp;quot;Remote Scripts&amp;quot; folder. &lt;br /&gt;
&lt;br /&gt;
If you&amp;#039;re using the Monomodular installer (see:  [[Installation]]), this should take care of itself. If you&amp;#039;re installing just the MonOhm script, here&amp;#039;s where it goes:&lt;br /&gt;
&lt;br /&gt;
*Macintosh – Right click on the Ableton Live application icon and select &amp;quot;show package contents&amp;quot;. Put the MonOhm folder in Contents/App-Resources/MIDI Remote Scripts&lt;br /&gt;
*Windows - put the MonOhm folder in C:\Program Files\Ableton\Live 8.x.x\Resources\MIDI Remote Scripts&lt;br /&gt;
&lt;br /&gt;
In order to use the Monomodular portion of the script, it is necessary to have Max5.18 installed, and the client plugins that are contained in the suite. Monomodular&amp;#039;s functionality in a seperate place (see:  [[How_Monomodular_Works]]).&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
The Ohm64 script (aka &amp;quot;MonOhm&amp;quot;) consists of three independent mixers.  Two of them control four channels at a time, the third mixer uses all 8 faders to control 8 channels.&lt;br /&gt;
&lt;br /&gt;
Each mixer is independent, and remembers the last tracks that were assigned to it.  When the Ohm64 is first connected to Live, it will automatically be in split mixer mode.  If there are more than four tracks in the project, the mixer will be assigned to the first 8 tracks, otherwise both sides of the mixer will be assigned to whatever tracks are present. &lt;br /&gt;
&lt;br /&gt;
Since there are several different &amp;quot;shift modes&amp;quot; available within the script, the most important concept to grasp about this scheme is that there are two shift buttons:  one left, and one right.  They are on either side of the crossfader.  By holding down the shift button, you gain access to a bunch of different alternative functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Pete @Livid says this script melts peoples&amp;#039; brains.  Really, its not all that complicated.  I tried to fit as much functionality as I could into what was available on the controller, and I can understand why that&amp;#039;s intimidating.  But its very hard to get lost unless you insist on pressing more than one button at a time without knowing what the combination is going to do.  Make this thine performance mantra:  &amp;#039;I shall not press two buttons at once until I understand....&amp;#039;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Note: If you have Max4Live, I highly recommend using a copy of the LCD patch; in addition to letting you know at all times what it is that you are controlling, it will also tell you precisely what the values of your parameters are (in plainspeak, not MIDIeze). &amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== The Grid ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_assign_main.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rows 1-5:  Fire Session Clips&lt;br /&gt;
&lt;br /&gt;
Row 6:  Mute&lt;br /&gt;
&lt;br /&gt;
Row 7:  Solo&lt;br /&gt;
&lt;br /&gt;
Row 8:  Arm&lt;br /&gt;
&lt;br /&gt;
Exception:  When in Right Mixer Mode 4, The right side of the Grid is mapped to DrumRacks (Pad Translation;  see below**).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Shifted Grid ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments with Right Shift button pressed:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_shift_l.png]] &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments with Right Shift button pressed:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_shift_r.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rows 1-5(except for column 8):  Session Zoom Navigation&lt;br /&gt;
&lt;br /&gt;
Row 6:  Record, Overdub, Loop, Stop All Clips, Zero All Sends 1-4&lt;br /&gt;
&lt;br /&gt;
Row 7: Crossfader Assignment&lt;br /&gt;
&lt;br /&gt;
Row 8: Stop Clip&lt;br /&gt;
&lt;br /&gt;
Column 8 (Rows 1-5):  Fire Scene&lt;br /&gt;
&lt;br /&gt;
By holding down one of the shifts and pressing one of the channel select buttons on the same side of the controller, you can enter a different &amp;quot;Shift Mode&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Modes ==&lt;br /&gt;
&lt;br /&gt;
=== For the Left Mixer, Modes 1-4 ===&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Faders are always mapped to Track Volume (or MIDI Velocity...see below****).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm_func1_l.png‎|180px|thumb|left]] &lt;br /&gt;
|Left Mode 1:  Left Dials(top 8) control selected Device, Left Dials (bottom 4) control Selected Track&amp;#039;s Sends.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_l_func2.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 2:  Left Dials control Sends 1-3 for the corresponding Fader&amp;#039;s Track.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func3_l.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 3:  Left Dials (top 8) control Track Filter for corresponding Fader, Left Dials (bottom 4) control Pan for corresponding Fader.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func4_l.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 4:  Left Dials are remapped to channel 2 so that they are User Mappable with Live.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For the Right Mixer, Modes 1-4 ===&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm func1 2 3 r.png|180px|thumb|left]]&lt;br /&gt;
|Right Mode 1:  Faders control Track Volume, Mixer offset at Track 5, Right Dials control Returns 1-4.&lt;br /&gt;
&lt;br /&gt;
Right Mode 2:  Faders control Track Volume, Mixer offset at Track 9, Right Dials control Returns 1-4.&lt;br /&gt;
&lt;br /&gt;
Right Mode 3:  Faders control Track Volume, Mixer offset at Track 13, Right Dials control Returns 1-4. &lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func4_r.png|180px|thumb|left]]&lt;br /&gt;
|Right Mode 4:  Faders control Return Volume, Right Dials control Return Pan&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Buttons below the Faders select Track in all modes (except when shift is being held...see below*).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Functions ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Function Buttons (top right) have the following functions (top left to bottom right):&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm function assign.png|200px|thumb|left]] &lt;br /&gt;
|Session Nav up, Play, Stop, Session Nav down,  Session Nav left, Session Nav right.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Function Buttons (top right) have the following Shifted functions (top left to bottom right):&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm function assign shift.png|200px|thumb|left]] &lt;br /&gt;
|Device Bank up, Device ON/OFF, Device Lock, Device Bank down, Device Nav left, Device Nav right.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WHILE LEFT SHIFT IS PRESSED, FADER 8 CONTROLS MASTER VOLUME.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WHILE LEFT SHIFT IS PRESSED, RIGHT DIAL 4 CONTROLS PREHEAR.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
(Master/Prehear functionality can be defeated in the MonOhm_Map.py file....it has fubarred me several times when things are lagging, so its not necessarily recommended for performance situations)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== modMode ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm modGrid.png]]&lt;br /&gt;
&lt;br /&gt;
The Livid button (aka &amp;quot;Gary the Welder&amp;quot;) switches the grid to Monomodular Mode (aka &amp;quot;modMode&amp;quot;).  Most of the controls remain the same, but the grid is now used for controlling Monomodular patches. &lt;br /&gt;
&lt;br /&gt;
When in modMode, the Function buttons (unShifted) control the following(top left to bottom right):&lt;br /&gt;
&lt;br /&gt;
Grid Nav up, Lock (the bottom row of the grid remains &amp;#039;Shifted&amp;#039;), Alt (access to Preset management in enabled patches...see below*****), Grid Nav down, Grid Nav right, Grid Nav left.&lt;br /&gt;
&lt;br /&gt;
When in modMode, the Function buttons (Shifted) control the following(top left to bottom right).&lt;br /&gt;
&lt;br /&gt;
Device Bank up, Play, Stop, Device Bank down, Device Nav left, Device Nav right.&lt;br /&gt;
&lt;br /&gt;
Track selection and Mode navigation is identical in Monomodular Mode as in normal Session Mode.&lt;br /&gt;
&lt;br /&gt;
By pressing either of the shift buttons, Zoom mode is invoked.  In Zoom mode, the center lit square of buttons indicates the current selected quadrant.  By pressing an area of that square, the grid changes assignment to the corresponding area.  &lt;br /&gt;
&lt;br /&gt;
In Zoom mode, the top row of buttons selects the current Monomodular plugin.  The second row of buttons selects the channel that plugin transmits on (this is only useful when the plugins &amp;#039;nomeout&amp;#039; is enabled...see below*****).  The bottom row of buttons transmits &amp;#039;Key&amp;#039; data (these buttons have special functionality specific to each Monomodular client...see the documenation with the client to find out what they do).&lt;br /&gt;
&lt;br /&gt;
For further info on modMode, see the section on [[How_Monomodular_Works]].&lt;br /&gt;
&lt;br /&gt;
== Linked Mixer Mode ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_linked_mixer.png]]&lt;br /&gt;
&lt;br /&gt;
By holding one shift button and pressing the other, it is possible to link both mixers so they behave like a single one. In linked mode, all mode changes correspond to the descriptions of the Left Mixer, and the right dials remain locked to the Returns.  It is still possible to access the Master/Prehear levels by pressing Right Shift.  The linked mixer&amp;#039;s position (i.e. track assignment) will be recalled independently from the other two mixers, thus allowing easy navigation between 16 tracks by the press of two buttons.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Footnotes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt; Channel Select buttons (buttons below the Faders) operate differently depending upon which Shift button is pressed.  While the left-side Shift is pressed, or when the Mixer is LINKED, the left 4 buttons select a new &amp;#039;Shift Mode&amp;#039;, while the right 4 buttons select a preset Device 5-8 (see below***).  When the right-side Shift is pressed, this behavior is reversed(i.e. preset Devices 1-4 on left, Mode on right).  &lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;**&amp;lt;/nowiki&amp;gt; Pad Translation works by reassigning the Channel/Identifier of each button.  In order to use it with Drum Racks, you must enable &amp;#039;Track Input&amp;#039; for the Ohm64&amp;#039;s MIDI Control Input, and assign that input as the source for the DrumRack&amp;#039;s input.  By default, Pad Translation transmits on MIDI Channel 10, but you can reassign this in the MonOhm_Map.py file to your liking.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;***&amp;lt;/nowiki&amp;gt; preset Device selection allows the user to select a predefined device instantly for editing with the Device knobs.  In order for this functionality to work, the Device must be renamed so that its first two characters are p1 thru p8.  Once named properly, the device may be selected by holding down a shift button and pressing one of the Channel Select buttons on the opposite side of the Ohm64 (e.g.  a device named &amp;#039;p1 Dub Delay&amp;#039; can be selected by holding down the right shift button and pressing the channel select underneath the 1st left side fader).&lt;br /&gt;
&lt;br /&gt;
[[File:Preset_example.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;****&amp;lt;/nowiki&amp;gt; when a Velocity plugin is inserted on a MIDI Track as the first plugin, any Fader currently controlling that Track will lock to its &amp;#039;Out Hi&amp;#039; parameter.  This allows the user to control the Volume of a MIDI only track.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*****&amp;lt;/nowiki&amp;gt; the Key buttons have specific functionality for each Monomodular client.  Generally, the first four control some aspect of the plugins operation, while the second four control the timing of the plugin.  However, see the individual helpfile contained in the client to find out exactly what they do for each one.  The Key buttons may be &amp;#039;Locked&amp;#039;, so that they are always accessible, by pressing the &amp;#039;Lock&amp;#039; button (the top-center Function button when in Monomodular Mode).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
phewww....I think that&amp;#039;s about it.&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Installation&amp;diff=664</id>
		<title>Installation</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Installation&amp;diff=664"/>
		<updated>2012-11-28T20:45:35Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* MacOS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Before installing Monomodular, make sure you have the most current versions of MaxMSP and Ableton Live installed on your computer.  You will also need a license to use MaxforLive (although it is possible to use everything here in Demo Mode).&lt;br /&gt;
&lt;br /&gt;
You may have navigated here from the installer itself, and you&amp;#039;re wondering what its all about.&lt;br /&gt;
&lt;br /&gt;
To install all the Monomodular software, just follow the instructions printed in the console window of the Installer patch.  &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;MAKE SURE LIVE&amp;#039;S AUDIO ENGINE IS TURNED ON BEFORE LOADING THE INSTALLER&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
There are four fields that need to be correct in order for the installation to proceed.  They display the file paths to the locations that the files will be copied on your system.  If they are correct, the field will be white.  If the path couldn&amp;#039;t automatically be found, it will say so in red, and you can locate it manually by either clicking on the text or dropping the file/folder onto the box on the left of the text.  The default paths for the files:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;IF YOU ARE USING WINDOWS 7, SEE BELOW FOR SPECIAL INSTRUCTIONS.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
==Installation Package (all platforms):==&lt;br /&gt;
&lt;br /&gt;
This is the data that the installer will copy to your computer.  If you downloaded the bundle, it should have been autodetected if you launched the installer from inside that bundles folder.  If not, you can either drag the folder from its location to the box on the left side of the text indicating the path, or you can click on the path and choose it from a file browser.&lt;br /&gt;
&lt;br /&gt;
If you are installing from SVN (not available with b993 yet), you must press the &amp;quot;Subversion&amp;quot; button on the right side of the interface, and you will be given a choice of a temp folder where the installer will download the package from its subversion repository.  You can delete this folder manually after the installation is complete, or leave it in place until the next time you update Monomodular with the installer (however, its path is not stored....it will need to be reselected the next time you run the installer).&lt;br /&gt;
&lt;br /&gt;
These are the default locations that the installer is looking for.  Under most circumstances, this is where things will be:&lt;br /&gt;
&lt;br /&gt;
Here&amp;#039;s a video from astarte describing the installation. He&amp;#039;s using a Launchpad with Monomodular in the video:&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=70sBh41X3qw&amp;amp;feature=plcp Astarte&amp;#039;s video]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====MacOS====&lt;br /&gt;
&lt;br /&gt;
Live.app             = ~/Applications/Live 8.x.x/Live.app&lt;br /&gt;
&lt;br /&gt;
or                      = ~/Applications/Ableton Live 8.app  (version 8.3.x and greater)&lt;br /&gt;
  &lt;br /&gt;
MaxMSP Folder  = ~/Applications/Max 5&lt;br /&gt;
&lt;br /&gt;
Live Library        = ~/Library/Preferences/Live 8.x.x/Library&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====Windows (pre win7)====&lt;br /&gt;
&lt;br /&gt;
Live Folder        = \Program Files\Ableton\Live 8.x.x&lt;br /&gt;
&lt;br /&gt;
MaxMSP Folder = \Program Files\Cycling &amp;#039;74\Max 5.x&lt;br /&gt;
&lt;br /&gt;
Live Library       =\Documents and Settings\USER\Documents\Ableton&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====Windows 7====&lt;br /&gt;
&lt;br /&gt;
Live Folder = \Program Files\Ableton\Live 8.x.x&lt;br /&gt;
&lt;br /&gt;
MaxMSP Folder = \Program Files\Cycling &amp;#039;74\Max 5.x&lt;br /&gt;
&lt;br /&gt;
Live Library = \users\username\documents\ableton\Library&lt;br /&gt;
&lt;br /&gt;
(see further Win7 specific instructions below)&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Once the installer has verified that the installation paths that you&amp;#039;ve chosen to be valid places to put its files, you can press the &amp;quot;Install&amp;quot; button to begin moving files to their proper places.  The terminal window on the right will indicate exactly what is being sent to the [shell] object in the patch, and if you are on MacOS, the return result from the shell will be displayed.  &lt;br /&gt;
&lt;br /&gt;
The installer will copy its payload to new folders if the correct folders don&amp;#039;t already exist.  For every new revision, a new set of folders will be generated.  This is good and bad.  It means that none your old installation will be harmed, so there will be no &amp;#039;broken&amp;#039; sets when you upgrade.  It also means, however, that if you upgrade as often as revisions are made, you will end up with a bunch of deprecated folders.  For now, you will have to delete these manually.  You can refer to the [[Manual Installation]] page to see what files go where, and what you can delete.  &lt;br /&gt;
&lt;br /&gt;
The good news is that Monomodular takes up very little room, so the only downside is a bitter of clutter (mostly in the Control Surface Scripts folder inside your Live installation....this can be a bit frustrating if you change things around often, but otherwise, is completely harmless).&lt;br /&gt;
&lt;br /&gt;
If you try to install a Monomodular revision over that same revision, the installer will not overwrite any files.  It should, however, replace any files that might have gone missing through erroneous deletion or movement.&lt;br /&gt;
&lt;br /&gt;
Once the installer is finished, it will indicate that you need to restart Live.  So....restart Live already.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====WINDOWS 7 INSTALLATION====&lt;br /&gt;
&lt;br /&gt;
The installer should be able to autodetect the file locations in the b993 installer, but it probably won&amp;#039;t be able to copy them unless you run Live with Administrator priveleges.  You can do this by right-clicking Live&amp;#039;s application and choosing &amp;quot;Run as Administator&amp;quot;.  &lt;br /&gt;
&lt;br /&gt;
However, this causes its own set of difficulties, because you can&amp;#039;t move files into Live by dragging and dropping while its running as Admin.  If you run into these problems, its best to run Live regularly first, drop the installer into Live&amp;#039;s Presets (under Max MIDI Device), then restart Live running it as Admin, and run the installer at that point.  You&amp;#039;ll still have to select the installer payload, but it should autodetect everything else.&lt;br /&gt;
&lt;br /&gt;
Sheesh.&lt;br /&gt;
&lt;br /&gt;
== Limitations ==&lt;br /&gt;
&lt;br /&gt;
All I can really say is:  &amp;#039;&amp;#039;&amp;#039;READ THE DIRECTIONS.&amp;#039;&amp;#039;&amp;#039;  I&amp;#039;ve done my best to make the installation as painless as possible, and I&amp;#039;ve included as much documentation both with the Installer patches and in this Wiki as I can think to.  &lt;br /&gt;
&lt;br /&gt;
That said, this is the first &amp;#039;m4l Native&amp;#039; installer that I&amp;#039;ve seen in the wild, and I&amp;#039;m doing all I can to make it compatible with as many systems as possible.  Worst case scenario with this installer is that you have to choose your own paths before you hit the &amp;quot;Install&amp;quot; button, which still eases the process of having to manually install all of the files.  &lt;br /&gt;
&lt;br /&gt;
The newest installation will get tagged with the revision number (e.g. blahblahb992&amp;#039;&amp;#039;&amp;#039;r030112&amp;#039;&amp;#039;&amp;#039;) , the suffix being the date that it was compiled for release. That means it should add to/overwrite any old data.  &lt;br /&gt;
&lt;br /&gt;
Currently, we&amp;#039;re still testing out the Installer on different systems to see what works and what won&amp;#039;t.  There may be problems with Lion and Win7, because I don&amp;#039;t have an installation of either at the moment and I&amp;#039;m therefore relying on end user input to work out the details.  If you have one of these operating systems and want to help out, please contact me via email and we&amp;#039;ll work on it. &lt;br /&gt;
&lt;br /&gt;
Otherwise, unless your system is &amp;quot;REALLY&amp;quot; weird, the installer should work fine.  I have no experience with trying to install to external partitions, but you should have all this stuff on the root partition anyway. Regardless, let me know how this works out (or doesn&amp;#039;t).&lt;br /&gt;
&lt;br /&gt;
== Python Persistence ==&lt;br /&gt;
&lt;br /&gt;
One of the things I&amp;#039;ve learned about Python and Live recently is that it caches all the modules on load, and likes to fill in the gaps of missing data with what it has cached.  This means if there are more than one module with the same name in its search paths, things can get tricky.  For this reason, I highly recommend that when installing new versions of the betas, you clean out the old ones from your MIDI Remote Scripts directory.  Nine times out of ten it won&amp;#039;t make a bit of difference, but if you&amp;#039;re having problems with things not working the way they are supposed to, it is the first thing I&amp;#039;d try to get things back to normal.&lt;br /&gt;
&lt;br /&gt;
== Live Crashes ==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve experienced on several occasions (in OSX) that the installer will crash Live if the log.txt file is either too long or has bad file references.  If the installer is crashing Live on your system, you might try deleting Live&amp;#039;s log.txt file.  It won&amp;#039;t hurt anything, and its solved the only crashes that I&amp;#039;ve ever encountered using the installer.  Live will create a new log.txt file the next time you start Live, and the installer will be able to do its thing without problems.&lt;br /&gt;
&lt;br /&gt;
== Root Volume ==&lt;br /&gt;
&lt;br /&gt;
Don&amp;#039;t expect the installer to work on Windows if you&amp;#039;ve got your base installation on a drive other than C:\.   It just probably won&amp;#039;t.&lt;br /&gt;
&lt;br /&gt;
== Manual Installation ==&lt;br /&gt;
&lt;br /&gt;
If the installer just doesn&amp;#039;t work for you for whatever reason, you can always put the files where they go manually.  Here&amp;#039;s some more information on how to do that:&lt;br /&gt;
&lt;br /&gt;
[[Manual Installation|Manual Installation]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Installation&amp;diff=663</id>
		<title>Installation</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Installation&amp;diff=663"/>
		<updated>2012-11-28T20:45:22Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* MacOS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Before installing Monomodular, make sure you have the most current versions of MaxMSP and Ableton Live installed on your computer.  You will also need a license to use MaxforLive (although it is possible to use everything here in Demo Mode).&lt;br /&gt;
&lt;br /&gt;
You may have navigated here from the installer itself, and you&amp;#039;re wondering what its all about.&lt;br /&gt;
&lt;br /&gt;
To install all the Monomodular software, just follow the instructions printed in the console window of the Installer patch.  &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;MAKE SURE LIVE&amp;#039;S AUDIO ENGINE IS TURNED ON BEFORE LOADING THE INSTALLER&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
There are four fields that need to be correct in order for the installation to proceed.  They display the file paths to the locations that the files will be copied on your system.  If they are correct, the field will be white.  If the path couldn&amp;#039;t automatically be found, it will say so in red, and you can locate it manually by either clicking on the text or dropping the file/folder onto the box on the left of the text.  The default paths for the files:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;IF YOU ARE USING WINDOWS 7, SEE BELOW FOR SPECIAL INSTRUCTIONS.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
==Installation Package (all platforms):==&lt;br /&gt;
&lt;br /&gt;
This is the data that the installer will copy to your computer.  If you downloaded the bundle, it should have been autodetected if you launched the installer from inside that bundles folder.  If not, you can either drag the folder from its location to the box on the left side of the text indicating the path, or you can click on the path and choose it from a file browser.&lt;br /&gt;
&lt;br /&gt;
If you are installing from SVN (not available with b993 yet), you must press the &amp;quot;Subversion&amp;quot; button on the right side of the interface, and you will be given a choice of a temp folder where the installer will download the package from its subversion repository.  You can delete this folder manually after the installation is complete, or leave it in place until the next time you update Monomodular with the installer (however, its path is not stored....it will need to be reselected the next time you run the installer).&lt;br /&gt;
&lt;br /&gt;
These are the default locations that the installer is looking for.  Under most circumstances, this is where things will be:&lt;br /&gt;
&lt;br /&gt;
Here&amp;#039;s a video from astarte describing the installation. He&amp;#039;s using a Launchpad with Monomodular in the video:&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=70sBh41X3qw&amp;amp;feature=plcp Astarte&amp;#039;s video]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====MacOS====&lt;br /&gt;
&lt;br /&gt;
Live.app             = ~/Applications/Live 8.x.x/Live.app&lt;br /&gt;
or                      = ~/Applications/Ableton Live 8.app  (version 8.3.x and greater)&lt;br /&gt;
  &lt;br /&gt;
MaxMSP Folder  = ~/Applications/Max 5&lt;br /&gt;
&lt;br /&gt;
Live Library        = ~/Library/Preferences/Live 8.x.x/Library&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====Windows (pre win7)====&lt;br /&gt;
&lt;br /&gt;
Live Folder        = \Program Files\Ableton\Live 8.x.x&lt;br /&gt;
&lt;br /&gt;
MaxMSP Folder = \Program Files\Cycling &amp;#039;74\Max 5.x&lt;br /&gt;
&lt;br /&gt;
Live Library       =\Documents and Settings\USER\Documents\Ableton&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====Windows 7====&lt;br /&gt;
&lt;br /&gt;
Live Folder = \Program Files\Ableton\Live 8.x.x&lt;br /&gt;
&lt;br /&gt;
MaxMSP Folder = \Program Files\Cycling &amp;#039;74\Max 5.x&lt;br /&gt;
&lt;br /&gt;
Live Library = \users\username\documents\ableton\Library&lt;br /&gt;
&lt;br /&gt;
(see further Win7 specific instructions below)&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Once the installer has verified that the installation paths that you&amp;#039;ve chosen to be valid places to put its files, you can press the &amp;quot;Install&amp;quot; button to begin moving files to their proper places.  The terminal window on the right will indicate exactly what is being sent to the [shell] object in the patch, and if you are on MacOS, the return result from the shell will be displayed.  &lt;br /&gt;
&lt;br /&gt;
The installer will copy its payload to new folders if the correct folders don&amp;#039;t already exist.  For every new revision, a new set of folders will be generated.  This is good and bad.  It means that none your old installation will be harmed, so there will be no &amp;#039;broken&amp;#039; sets when you upgrade.  It also means, however, that if you upgrade as often as revisions are made, you will end up with a bunch of deprecated folders.  For now, you will have to delete these manually.  You can refer to the [[Manual Installation]] page to see what files go where, and what you can delete.  &lt;br /&gt;
&lt;br /&gt;
The good news is that Monomodular takes up very little room, so the only downside is a bitter of clutter (mostly in the Control Surface Scripts folder inside your Live installation....this can be a bit frustrating if you change things around often, but otherwise, is completely harmless).&lt;br /&gt;
&lt;br /&gt;
If you try to install a Monomodular revision over that same revision, the installer will not overwrite any files.  It should, however, replace any files that might have gone missing through erroneous deletion or movement.&lt;br /&gt;
&lt;br /&gt;
Once the installer is finished, it will indicate that you need to restart Live.  So....restart Live already.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====WINDOWS 7 INSTALLATION====&lt;br /&gt;
&lt;br /&gt;
The installer should be able to autodetect the file locations in the b993 installer, but it probably won&amp;#039;t be able to copy them unless you run Live with Administrator priveleges.  You can do this by right-clicking Live&amp;#039;s application and choosing &amp;quot;Run as Administator&amp;quot;.  &lt;br /&gt;
&lt;br /&gt;
However, this causes its own set of difficulties, because you can&amp;#039;t move files into Live by dragging and dropping while its running as Admin.  If you run into these problems, its best to run Live regularly first, drop the installer into Live&amp;#039;s Presets (under Max MIDI Device), then restart Live running it as Admin, and run the installer at that point.  You&amp;#039;ll still have to select the installer payload, but it should autodetect everything else.&lt;br /&gt;
&lt;br /&gt;
Sheesh.&lt;br /&gt;
&lt;br /&gt;
== Limitations ==&lt;br /&gt;
&lt;br /&gt;
All I can really say is:  &amp;#039;&amp;#039;&amp;#039;READ THE DIRECTIONS.&amp;#039;&amp;#039;&amp;#039;  I&amp;#039;ve done my best to make the installation as painless as possible, and I&amp;#039;ve included as much documentation both with the Installer patches and in this Wiki as I can think to.  &lt;br /&gt;
&lt;br /&gt;
That said, this is the first &amp;#039;m4l Native&amp;#039; installer that I&amp;#039;ve seen in the wild, and I&amp;#039;m doing all I can to make it compatible with as many systems as possible.  Worst case scenario with this installer is that you have to choose your own paths before you hit the &amp;quot;Install&amp;quot; button, which still eases the process of having to manually install all of the files.  &lt;br /&gt;
&lt;br /&gt;
The newest installation will get tagged with the revision number (e.g. blahblahb992&amp;#039;&amp;#039;&amp;#039;r030112&amp;#039;&amp;#039;&amp;#039;) , the suffix being the date that it was compiled for release. That means it should add to/overwrite any old data.  &lt;br /&gt;
&lt;br /&gt;
Currently, we&amp;#039;re still testing out the Installer on different systems to see what works and what won&amp;#039;t.  There may be problems with Lion and Win7, because I don&amp;#039;t have an installation of either at the moment and I&amp;#039;m therefore relying on end user input to work out the details.  If you have one of these operating systems and want to help out, please contact me via email and we&amp;#039;ll work on it. &lt;br /&gt;
&lt;br /&gt;
Otherwise, unless your system is &amp;quot;REALLY&amp;quot; weird, the installer should work fine.  I have no experience with trying to install to external partitions, but you should have all this stuff on the root partition anyway. Regardless, let me know how this works out (or doesn&amp;#039;t).&lt;br /&gt;
&lt;br /&gt;
== Python Persistence ==&lt;br /&gt;
&lt;br /&gt;
One of the things I&amp;#039;ve learned about Python and Live recently is that it caches all the modules on load, and likes to fill in the gaps of missing data with what it has cached.  This means if there are more than one module with the same name in its search paths, things can get tricky.  For this reason, I highly recommend that when installing new versions of the betas, you clean out the old ones from your MIDI Remote Scripts directory.  Nine times out of ten it won&amp;#039;t make a bit of difference, but if you&amp;#039;re having problems with things not working the way they are supposed to, it is the first thing I&amp;#039;d try to get things back to normal.&lt;br /&gt;
&lt;br /&gt;
== Live Crashes ==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve experienced on several occasions (in OSX) that the installer will crash Live if the log.txt file is either too long or has bad file references.  If the installer is crashing Live on your system, you might try deleting Live&amp;#039;s log.txt file.  It won&amp;#039;t hurt anything, and its solved the only crashes that I&amp;#039;ve ever encountered using the installer.  Live will create a new log.txt file the next time you start Live, and the installer will be able to do its thing without problems.&lt;br /&gt;
&lt;br /&gt;
== Root Volume ==&lt;br /&gt;
&lt;br /&gt;
Don&amp;#039;t expect the installer to work on Windows if you&amp;#039;ve got your base installation on a drive other than C:\.   It just probably won&amp;#039;t.&lt;br /&gt;
&lt;br /&gt;
== Manual Installation ==&lt;br /&gt;
&lt;br /&gt;
If the installer just doesn&amp;#039;t work for you for whatever reason, you can always put the files where they go manually.  Here&amp;#039;s some more information on how to do that:&lt;br /&gt;
&lt;br /&gt;
[[Manual Installation|Manual Installation]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=Installation&amp;diff=662</id>
		<title>Installation</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=Installation&amp;diff=662"/>
		<updated>2012-11-28T20:44:44Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* MacOS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Before installing Monomodular, make sure you have the most current versions of MaxMSP and Ableton Live installed on your computer.  You will also need a license to use MaxforLive (although it is possible to use everything here in Demo Mode).&lt;br /&gt;
&lt;br /&gt;
You may have navigated here from the installer itself, and you&amp;#039;re wondering what its all about.&lt;br /&gt;
&lt;br /&gt;
To install all the Monomodular software, just follow the instructions printed in the console window of the Installer patch.  &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;MAKE SURE LIVE&amp;#039;S AUDIO ENGINE IS TURNED ON BEFORE LOADING THE INSTALLER&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
There are four fields that need to be correct in order for the installation to proceed.  They display the file paths to the locations that the files will be copied on your system.  If they are correct, the field will be white.  If the path couldn&amp;#039;t automatically be found, it will say so in red, and you can locate it manually by either clicking on the text or dropping the file/folder onto the box on the left of the text.  The default paths for the files:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;IF YOU ARE USING WINDOWS 7, SEE BELOW FOR SPECIAL INSTRUCTIONS.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
==Installation Package (all platforms):==&lt;br /&gt;
&lt;br /&gt;
This is the data that the installer will copy to your computer.  If you downloaded the bundle, it should have been autodetected if you launched the installer from inside that bundles folder.  If not, you can either drag the folder from its location to the box on the left side of the text indicating the path, or you can click on the path and choose it from a file browser.&lt;br /&gt;
&lt;br /&gt;
If you are installing from SVN (not available with b993 yet), you must press the &amp;quot;Subversion&amp;quot; button on the right side of the interface, and you will be given a choice of a temp folder where the installer will download the package from its subversion repository.  You can delete this folder manually after the installation is complete, or leave it in place until the next time you update Monomodular with the installer (however, its path is not stored....it will need to be reselected the next time you run the installer).&lt;br /&gt;
&lt;br /&gt;
These are the default locations that the installer is looking for.  Under most circumstances, this is where things will be:&lt;br /&gt;
&lt;br /&gt;
Here&amp;#039;s a video from astarte describing the installation. He&amp;#039;s using a Launchpad with Monomodular in the video:&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=70sBh41X3qw&amp;amp;feature=plcp Astarte&amp;#039;s video]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====MacOS====&lt;br /&gt;
&lt;br /&gt;
Live.app             = ~/Applications/Live 8.x.x/Live.app&lt;br /&gt;
                   or    = ~/Applications/Ableton Live 8.app  (version 8.3.x and greater)&lt;br /&gt;
  &lt;br /&gt;
MaxMSP Folder  = ~/Applications/Max 5&lt;br /&gt;
&lt;br /&gt;
Live Library        = ~/Library/Preferences/Live 8.x.x/Library&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====Windows (pre win7)====&lt;br /&gt;
&lt;br /&gt;
Live Folder        = \Program Files\Ableton\Live 8.x.x&lt;br /&gt;
&lt;br /&gt;
MaxMSP Folder = \Program Files\Cycling &amp;#039;74\Max 5.x&lt;br /&gt;
&lt;br /&gt;
Live Library       =\Documents and Settings\USER\Documents\Ableton&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
====Windows 7====&lt;br /&gt;
&lt;br /&gt;
Live Folder = \Program Files\Ableton\Live 8.x.x&lt;br /&gt;
&lt;br /&gt;
MaxMSP Folder = \Program Files\Cycling &amp;#039;74\Max 5.x&lt;br /&gt;
&lt;br /&gt;
Live Library = \users\username\documents\ableton\Library&lt;br /&gt;
&lt;br /&gt;
(see further Win7 specific instructions below)&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Once the installer has verified that the installation paths that you&amp;#039;ve chosen to be valid places to put its files, you can press the &amp;quot;Install&amp;quot; button to begin moving files to their proper places.  The terminal window on the right will indicate exactly what is being sent to the [shell] object in the patch, and if you are on MacOS, the return result from the shell will be displayed.  &lt;br /&gt;
&lt;br /&gt;
The installer will copy its payload to new folders if the correct folders don&amp;#039;t already exist.  For every new revision, a new set of folders will be generated.  This is good and bad.  It means that none your old installation will be harmed, so there will be no &amp;#039;broken&amp;#039; sets when you upgrade.  It also means, however, that if you upgrade as often as revisions are made, you will end up with a bunch of deprecated folders.  For now, you will have to delete these manually.  You can refer to the [[Manual Installation]] page to see what files go where, and what you can delete.  &lt;br /&gt;
&lt;br /&gt;
The good news is that Monomodular takes up very little room, so the only downside is a bitter of clutter (mostly in the Control Surface Scripts folder inside your Live installation....this can be a bit frustrating if you change things around often, but otherwise, is completely harmless).&lt;br /&gt;
&lt;br /&gt;
If you try to install a Monomodular revision over that same revision, the installer will not overwrite any files.  It should, however, replace any files that might have gone missing through erroneous deletion or movement.&lt;br /&gt;
&lt;br /&gt;
Once the installer is finished, it will indicate that you need to restart Live.  So....restart Live already.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====WINDOWS 7 INSTALLATION====&lt;br /&gt;
&lt;br /&gt;
The installer should be able to autodetect the file locations in the b993 installer, but it probably won&amp;#039;t be able to copy them unless you run Live with Administrator priveleges.  You can do this by right-clicking Live&amp;#039;s application and choosing &amp;quot;Run as Administator&amp;quot;.  &lt;br /&gt;
&lt;br /&gt;
However, this causes its own set of difficulties, because you can&amp;#039;t move files into Live by dragging and dropping while its running as Admin.  If you run into these problems, its best to run Live regularly first, drop the installer into Live&amp;#039;s Presets (under Max MIDI Device), then restart Live running it as Admin, and run the installer at that point.  You&amp;#039;ll still have to select the installer payload, but it should autodetect everything else.&lt;br /&gt;
&lt;br /&gt;
Sheesh.&lt;br /&gt;
&lt;br /&gt;
== Limitations ==&lt;br /&gt;
&lt;br /&gt;
All I can really say is:  &amp;#039;&amp;#039;&amp;#039;READ THE DIRECTIONS.&amp;#039;&amp;#039;&amp;#039;  I&amp;#039;ve done my best to make the installation as painless as possible, and I&amp;#039;ve included as much documentation both with the Installer patches and in this Wiki as I can think to.  &lt;br /&gt;
&lt;br /&gt;
That said, this is the first &amp;#039;m4l Native&amp;#039; installer that I&amp;#039;ve seen in the wild, and I&amp;#039;m doing all I can to make it compatible with as many systems as possible.  Worst case scenario with this installer is that you have to choose your own paths before you hit the &amp;quot;Install&amp;quot; button, which still eases the process of having to manually install all of the files.  &lt;br /&gt;
&lt;br /&gt;
The newest installation will get tagged with the revision number (e.g. blahblahb992&amp;#039;&amp;#039;&amp;#039;r030112&amp;#039;&amp;#039;&amp;#039;) , the suffix being the date that it was compiled for release. That means it should add to/overwrite any old data.  &lt;br /&gt;
&lt;br /&gt;
Currently, we&amp;#039;re still testing out the Installer on different systems to see what works and what won&amp;#039;t.  There may be problems with Lion and Win7, because I don&amp;#039;t have an installation of either at the moment and I&amp;#039;m therefore relying on end user input to work out the details.  If you have one of these operating systems and want to help out, please contact me via email and we&amp;#039;ll work on it. &lt;br /&gt;
&lt;br /&gt;
Otherwise, unless your system is &amp;quot;REALLY&amp;quot; weird, the installer should work fine.  I have no experience with trying to install to external partitions, but you should have all this stuff on the root partition anyway. Regardless, let me know how this works out (or doesn&amp;#039;t).&lt;br /&gt;
&lt;br /&gt;
== Python Persistence ==&lt;br /&gt;
&lt;br /&gt;
One of the things I&amp;#039;ve learned about Python and Live recently is that it caches all the modules on load, and likes to fill in the gaps of missing data with what it has cached.  This means if there are more than one module with the same name in its search paths, things can get tricky.  For this reason, I highly recommend that when installing new versions of the betas, you clean out the old ones from your MIDI Remote Scripts directory.  Nine times out of ten it won&amp;#039;t make a bit of difference, but if you&amp;#039;re having problems with things not working the way they are supposed to, it is the first thing I&amp;#039;d try to get things back to normal.&lt;br /&gt;
&lt;br /&gt;
== Live Crashes ==&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;ve experienced on several occasions (in OSX) that the installer will crash Live if the log.txt file is either too long or has bad file references.  If the installer is crashing Live on your system, you might try deleting Live&amp;#039;s log.txt file.  It won&amp;#039;t hurt anything, and its solved the only crashes that I&amp;#039;ve ever encountered using the installer.  Live will create a new log.txt file the next time you start Live, and the installer will be able to do its thing without problems.&lt;br /&gt;
&lt;br /&gt;
== Root Volume ==&lt;br /&gt;
&lt;br /&gt;
Don&amp;#039;t expect the installer to work on Windows if you&amp;#039;ve got your base installation on a drive other than C:\.   It just probably won&amp;#039;t.&lt;br /&gt;
&lt;br /&gt;
== Manual Installation ==&lt;br /&gt;
&lt;br /&gt;
If the installer just doesn&amp;#039;t work for you for whatever reason, you can always put the files where they go manually.  Here&amp;#039;s some more information on how to do that:&lt;br /&gt;
&lt;br /&gt;
[[Manual Installation|Manual Installation]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=How_Mod_Works&amp;diff=661</id>
		<title>How Mod Works</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=How_Mod_Works&amp;diff=661"/>
		<updated>2012-11-28T20:41:50Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Supported Controllers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Monomodular is the hub of all communcations between [[Mods]] and the Monomodular capable controllers.  Each client control script works in its own way, but the Monomodular standard is shared between all of them.&lt;br /&gt;
&lt;br /&gt;
Monomodular controllers all have the capability of controlling a Monome256 workspace.  Each one does it in its specific way.  The only necessity required to integrate a controller with the Monomodular design is that it has an 8x8 grid of buttons.  Other functionality is present on some controllers, but mainly, it works like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Grid ==&lt;br /&gt;
&lt;br /&gt;
There is an 8x8 grid, which represents one quadrant of the Monome256 workspace in its normal mode.  &lt;br /&gt;
&lt;br /&gt;
In addition, it will display generic information about the status of Monomodular and its connected Mods when using the other controls below.&lt;br /&gt;
&lt;br /&gt;
If you are not familiar with how a monome works, you might want to check this out:&lt;br /&gt;
&lt;br /&gt;
http://en.wikipedia.org/wiki/Monome&lt;br /&gt;
&lt;br /&gt;
and this:&lt;br /&gt;
&lt;br /&gt;
http://monome.org/&lt;br /&gt;
&lt;br /&gt;
But chances are if you&amp;#039;ve made it this far, you probably already know about monomes (and want one of your own!).  Good thing for you, here it is.....&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Shift Button ==&lt;br /&gt;
&lt;br /&gt;
There is a Shift button, which, when pressed,  does the following:&lt;br /&gt;
&lt;br /&gt;
It allows navigation to one of those 4 quadrants by pressing one of the center 16 buttons, which will be lit to indicate which area is currently selected (either by colors or by different flashing states).&lt;br /&gt;
&lt;br /&gt;
It causes the top row of buttons to indicate which of the 16 possible [[Mods]] is currently selected.  The button on column 1, row 3 allows the user to select Mod 9-16 according to its toggle status.&lt;br /&gt;
&lt;br /&gt;
It causes the second row of buttons to indicate which of the 16 possible channels the currently selected Mod is transmitting on (if it is a mono-channel instrument).  The button on column 8, row 3 allows the user to select Mod 9-16 according to its toggle status.&lt;br /&gt;
&lt;br /&gt;
It causes the bottom row of buttons to change over to &amp;#039;Key Mode&amp;#039;, and their status to be updated accordingly.  The Key buttons are patch specific in functionality, but there are general conventions about how they are used in most of the plugins.  Most of the time the left four will indicate and change the Mods &amp;#039;mode&amp;#039;, and the second four control timing of the Mod if it is slaved to its internal clock.&lt;br /&gt;
&lt;br /&gt;
As of b993, the left column sixth button will toggle into/out of [[MonoLinkComponent|MonoLink]] mode, and will indicate whether the control surface has that mode engaged or not.&lt;br /&gt;
&lt;br /&gt;
[[File:8x8_shift.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Lock Button ==&lt;br /&gt;
&lt;br /&gt;
There is a Lock button, which toggles whether the bottom row is &amp;#039;shift-locked&amp;#039; to permanently be used in &amp;#039;Key Mode&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:8x8grid_locked.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Alt Button ==&lt;br /&gt;
&lt;br /&gt;
By pressing the dedicated &amp;quot;alt&amp;quot; button on the controller, it is possible to access additional functionality from the &amp;quot;Key&amp;quot; buttons.  If there are no dedicated key buttons, the user can either engage &amp;quot;lock&amp;quot;, or hold &amp;quot;shift&amp;quot; before pressing pressing &amp;quot;alt&amp;quot; and use the bottom row of grid buttons to access these functions.&lt;br /&gt;
&lt;br /&gt;
The first four buttons have no built in functionality, but may trigger a behavior that is specific to the mod that is currently selected.  &lt;br /&gt;
&lt;br /&gt;
The last four buttons always perform the following functions:&lt;br /&gt;
&lt;br /&gt;
5: View mod in Live.  This will bring up the mod&amp;#039;s device in Lives detail view, and consequently select the track that it&amp;#039;s on.  There is unfortunately no way to navigate to it if its nested in a Device Rack, but this will select the Rack that its contained in.&lt;br /&gt;
&lt;br /&gt;
6: Toggle mod Mute.  If the mod has embedded mute functionality, this button will toggle whether it is muted.  It will be lit if unmuted while &amp;quot;alt&amp;quot; is depressed.&lt;br /&gt;
&lt;br /&gt;
7. Toggle mod Power.  This will toggle the device on/off parameter of the currently selected mod Device in Live.&lt;br /&gt;
&lt;br /&gt;
8. Select mod Device.  On controllers that offer device control,  this will select the mod&amp;#039;s parameters as the currently controlled device for the dials on the controller.&lt;br /&gt;
&lt;br /&gt;
[[File:8x8grid_alt.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== MonoLinkComponent ==&lt;br /&gt;
&lt;br /&gt;
A new component has been added to the Monomodular MIDI Remote Script as of b993 which allows the user to connect to monome-based patches with no need for m4l or any other &amp;#039;bridge&amp;#039; applications running in the background.  The MonoLinkComponent is currently considered &amp;quot;beta&amp;quot;  (er....more beta than the rest of Monomodular), so test it thoroughly on your system before depending upon it.  That said, most of the prerelease testers have had success with it.&lt;br /&gt;
&lt;br /&gt;
For more info:  [[MonoLinkComponent]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Mod Order ==&lt;br /&gt;
&lt;br /&gt;
A Mod can be used simply by placing it on an appropriate track in your Live set.  It will automatically be configured consecutively as the next Mod, and its position on the nav-grid will be indicated by a numbered block on the top left of the Mod&amp;#039;s user interface (white block means 1-8, black block means 9-16).  You can, however, change this enumeration manually in the plugin&amp;#039;s UI, and other Mods positions will be adjusted accordingly.  These changes are persistent so that the next time you load your set, everything will be in the same place.&lt;br /&gt;
&lt;br /&gt;
[[File:Block1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Mod Timing ==&lt;br /&gt;
&lt;br /&gt;
Most of the Mods have their own internal timing engine that is sync&amp;#039;ed to Live&amp;#039;s clock.  This, however, may be disengaged in order to trigger the timing process of the plugin from an external source (see below).&lt;br /&gt;
&lt;br /&gt;
For most of the Mods, timing can be controlled by the last four Keys.  The first of these changes the timing to Quarter note divisions, the second to Eighth note divisions, and the third to Sixteenth note divisions.  The last button toggles Triplet timing.&lt;br /&gt;
&lt;br /&gt;
[[File:Grid timing.png]]&lt;br /&gt;
&lt;br /&gt;
In addition to the key controls, most Mods also have a &amp;#039;Timing Multiplier&amp;#039;, which speeds the timing engine up by the chosen amount.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Input and Output Settings ==&lt;br /&gt;
&lt;br /&gt;
Each Mod has its own idea of how to get things in and out.  For most, however, there is a fairly standard MIDI settings dialog which allows the user to change how things are routed.&lt;br /&gt;
&lt;br /&gt;
To change these settings, press the &amp;#039;MIDI&amp;#039; button.  This will bring up a floating window with that Mod&amp;#039;s MIDI settings. &lt;br /&gt;
&lt;br /&gt;
[[File:Mod midi settings.png]]&lt;br /&gt;
&lt;br /&gt;
By default, a Mod will transmit its output to the TrackOutput of its plugin.  That means the data is going to be delivered to whatever is after it in the track its situated in.  In this case, the Mod&amp;#039;s channel setting has no effect, since Live does not care at all which channel MIDI data is transmitted on internally.&lt;br /&gt;
&lt;br /&gt;
However, it is possible to use &amp;#039;[[NomeOut]]&amp;#039; nodes to channelize data within Live.  By placing a [[NomeOut]] patch elsewhere in the Live set, and setting a Mod&amp;#039;s output destination to that Nome patch, you can select where a Mod&amp;#039;s output is received merely by changing its channel in Shift-mode.  [[NomeOut]] is crossplatform, however it is likely to be less accurate for timing than using the default output or MIDI.&lt;br /&gt;
&lt;br /&gt;
If you are using OSX, it is also possible to transmit and receive via the lh_midi external created by Leigh Hunt.  This object is included with the Monomodular installation, and will allow you to choose (for instance) an IAC bus as the destination for your Mods data.  You can then route that IAC bus as a Track input back to your project, with much lower and more predictable amounts of latency.&lt;br /&gt;
&lt;br /&gt;
In addition, some Mods use MIDI for input as well.  Their input source may be changed in the same way.  In a situation where you would like to use another timing engine to drive the Mod, you should assign an appropriate source for that input, and define what its clock beat will be.  Also, make sure to toggle off the &amp;#039;Internal&amp;#039; button on the MIDI configuration page.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Supported Controllers ==&lt;br /&gt;
&lt;br /&gt;
For more detailed descriptions of controller-specific functionality, please refer to the links below:&lt;br /&gt;
&lt;br /&gt;
*[[How to use the AumPC scripts|Details for the APC]]&lt;br /&gt;
&lt;br /&gt;
*[[How to use the BlockMod script|Details for the Block]]&lt;br /&gt;
&lt;br /&gt;
*[[How to use the Codec script|Details for the Code]]&lt;br /&gt;
&lt;br /&gt;
*[[How to use the iOs scripts|Details for the iPad]]&lt;br /&gt;
&lt;br /&gt;
*[[How to use the LaunchMod script|Details for the Launchpad]]&lt;br /&gt;
&lt;br /&gt;
*[[How to use the Ohm64 script|Details for the Ohm64 and Ohm64 RGB]]&lt;br /&gt;
&lt;br /&gt;
*[[How to use the AumTroll script|Details for the CNTRL:R]]&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=How_to_use_the_Ohm64_script&amp;diff=660</id>
		<title>How to use the Ohm64 script</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=How_to_use_the_Ohm64_script&amp;diff=660"/>
		<updated>2012-11-28T20:40:48Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Summary */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Some Video Tutorials ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=9ypoR7JH1cY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=8&amp;amp;feature=plcp  Earliest tutorial with old help patcher and little commentary]&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=00mlz1DpUTY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=7&amp;amp;feature=plcp b99 Release tutorial]&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
&lt;br /&gt;
The only component that is strictly necessary to get the Remote Script working in Ableton is the MonOhm Script itself.  It goes in the Live Application Bundle, in the &amp;quot;Remote Scripts&amp;quot; folder. &lt;br /&gt;
&lt;br /&gt;
If you&amp;#039;re using the Monomodular installer, this should take care of itself. If you&amp;#039;re installing just the MonOhm script, here&amp;#039;s where it goes:&lt;br /&gt;
&lt;br /&gt;
*Macintosh – Right click on the Ableton Live application icon and select &amp;quot;show package contents&amp;quot;. Put the MonOhm folder in Contents/App-Resources/MIDI Remote Scripts&lt;br /&gt;
*Windows - put the MonOhm folder in C:\Program Files\Ableton\Live 8.x.x\Resources\MIDI Remote Scripts&lt;br /&gt;
&lt;br /&gt;
In order to use the Monomodular portion of the script, it is necessary to have Max5.18 installed, and the client plugins that are contained in the suite. Monomodular&amp;#039;s functionality in a seperate place (see:  [[How_Monomodular_Works]]).  &lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
The Ohm64 script (aka &amp;quot;MonOhm&amp;quot;) consists of three independent mixers.  Two of them control four channels at a time, the third mixer uses all 8 faders to control 8 channels.&lt;br /&gt;
&lt;br /&gt;
Each mixer is independent, and remembers the last tracks that were assigned to it.  When the Ohm64 is first connected to Live, it will automatically be in split mixer mode.  If there are more than four tracks in the project, the mixer will be assigned to the first 8 tracks, otherwise both sides of the mixer will be assigned to whatever tracks are present. &lt;br /&gt;
&lt;br /&gt;
Since there are several different &amp;quot;shift modes&amp;quot; available within the script, the most important concept to grasp about this scheme is that there are two shift buttons:  one left, and one right.  They are on either side of the crossfader.  By holding down the shift button, you gain access to a bunch of different alternative functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Pete @Livid says this script melts peoples&amp;#039; brains.  Really, its not all that complicated.  I tried to fit as much functionality as I could into what was available on the controller, and I can understand why that&amp;#039;s intimidating.  But its very hard to get lost unless you insist on pressing more than one button at a time without knowing what the combination is going to do.  Make this thine performance mantra:  &amp;#039;I shall not press two buttons at once until I understand....&amp;#039;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Note: If you have Max4Live, I highly recommend using a copy of the LCD patch; in addition to letting you know at all times what it is that you are controlling, it will also tell you precisely what the values of your parameters are (in plainspeak, not MIDIeze). &amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== The Grid ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_assign_main.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rows 1-5:  Fire Session Clips&lt;br /&gt;
&lt;br /&gt;
Row 6:  Mute&lt;br /&gt;
&lt;br /&gt;
Row 7:  Solo&lt;br /&gt;
&lt;br /&gt;
Row 8:  Arm&lt;br /&gt;
&lt;br /&gt;
Exception:  When in Right Mixer Mode 4, The right side of the Grid is mapped to DrumRacks (Pad Translation;  see below**).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Shifted Grid ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments with Right Shift button pressed:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_shift_l.png]] &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments with Right Shift button pressed:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_shift_r.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rows 1-5(except for column 8):  Session Zoom Navigation&lt;br /&gt;
&lt;br /&gt;
Row 6:  Record, Overdub, Loop, Stop All Clips, Zero All Sends 1-4&lt;br /&gt;
&lt;br /&gt;
Row 7: Crossfader Assignment&lt;br /&gt;
&lt;br /&gt;
Row 8: Stop Clip&lt;br /&gt;
&lt;br /&gt;
Column 8 (Rows 1-5):  Fire Scene&lt;br /&gt;
&lt;br /&gt;
By holding down one of the shifts and pressing one of the channel select buttons on the same side of the controller, you can enter a different &amp;quot;Shift Mode&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Modes ==&lt;br /&gt;
&lt;br /&gt;
=== For the Left Mixer, Modes 1-4 ===&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Faders are always mapped to Track Volume (or MIDI Velocity...see below****).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm_func1_l.png‎|180px|thumb|left]] &lt;br /&gt;
|Left Mode 1:  Left Dials(top 8) control selected Device, Left Dials (bottom 4) control Selected Track&amp;#039;s Sends.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_l_func2.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 2:  Left Dials control Sends 1-3 for the corresponding Fader&amp;#039;s Track.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func3_l.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 3:  Left Dials (top 8) control Track Filter for corresponding Fader, Left Dials (bottom 4) control Pan for corresponding Fader.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func4_l.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 4:  Left Dials are remapped to channel 2 so that they are User Mappable with Live.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For the Right Mixer, Modes 1-4 ===&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm func1 2 3 r.png|180px|thumb|left]]&lt;br /&gt;
|Right Mode 1:  Faders control Track Volume, Mixer offset at Track 5, Right Dials control Returns 1-4.&lt;br /&gt;
&lt;br /&gt;
Right Mode 2:  Faders control Track Volume, Mixer offset at Track 9, Right Dials control Returns 1-4.&lt;br /&gt;
&lt;br /&gt;
Right Mode 3:  Faders control Track Volume, Mixer offset at Track 13, Right Dials control Returns 1-4. &lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func4_r.png|180px|thumb|left]]&lt;br /&gt;
|Right Mode 4:  Faders control Return Volume, Right Dials control Return Pan&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Buttons below the Faders select Track in all modes (except when shift is being held...see below*).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Functions ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Function Buttons (top right) have the following functions (top left to bottom right):&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm function assign.png|200px|thumb|left]] &lt;br /&gt;
|Session Nav up, Play, Stop, Session Nav down,  Session Nav left, Session Nav right.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Function Buttons (top right) have the following Shifted functions (top left to bottom right):&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm function assign shift.png|200px|thumb|left]] &lt;br /&gt;
|Device Bank up, Device ON/OFF, Device Lock, Device Bank down, Device Nav left, Device Nav right.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WHILE LEFT SHIFT IS PRESSED, FADER 8 CONTROLS MASTER VOLUME.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WHILE LEFT SHIFT IS PRESSED, RIGHT DIAL 4 CONTROLS PREHEAR.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
(Master/Prehear functionality can be defeated in the MonOhm_Map.py file....it has fubarred me several times when things are lagging, so its not necessarily recommended for performance situations)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== modMode ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm modGrid.png]]&lt;br /&gt;
&lt;br /&gt;
The Livid button (aka &amp;quot;Gary the Welder&amp;quot;) switches the grid to Monomodular Mode (aka &amp;quot;modMode&amp;quot;).  Most of the controls remain the same, but the grid is now used for controlling Monomodular patches. &lt;br /&gt;
&lt;br /&gt;
When in modMode, the Function buttons (unShifted) control the following(top left to bottom right):&lt;br /&gt;
&lt;br /&gt;
Grid Nav up, Lock (the bottom row of the grid remains &amp;#039;Shifted&amp;#039;), Alt (access to Preset management in enabled patches...see below*****), Grid Nav down, Grid Nav right, Grid Nav left.&lt;br /&gt;
&lt;br /&gt;
When in modMode, the Function buttons (Shifted) control the following(top left to bottom right).&lt;br /&gt;
&lt;br /&gt;
Device Bank up, Play, Stop, Device Bank down, Device Nav left, Device Nav right.&lt;br /&gt;
&lt;br /&gt;
Track selection and Mode navigation is identical in Monomodular Mode as in normal Session Mode.&lt;br /&gt;
&lt;br /&gt;
By pressing either of the shift buttons, Zoom mode is invoked.  In Zoom mode, the center lit square of buttons indicates the current selected quadrant.  By pressing an area of that square, the grid changes assignment to the corresponding area.  &lt;br /&gt;
&lt;br /&gt;
In Zoom mode, the top row of buttons selects the current Monomodular plugin.  The second row of buttons selects the channel that plugin transmits on (this is only useful when the plugins &amp;#039;nomeout&amp;#039; is enabled...see below*****).  The bottom row of buttons transmits &amp;#039;Key&amp;#039; data (these buttons have special functionality specific to each Monomodular client...see the documenation with the client to find out what they do).&lt;br /&gt;
&lt;br /&gt;
For further info on modMode, see the section on [[How_Monomodular_Works]].&lt;br /&gt;
&lt;br /&gt;
== Linked Mixer Mode ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_linked_mixer.png]]&lt;br /&gt;
&lt;br /&gt;
By holding one shift button and pressing the other, it is possible to link both mixers so they behave like a single one. In linked mode, all mode changes correspond to the descriptions of the Left Mixer, and the right dials remain locked to the Returns.  It is still possible to access the Master/Prehear levels by pressing Right Shift.  The linked mixer&amp;#039;s position (i.e. track assignment) will be recalled independently from the other two mixers, thus allowing easy navigation between 16 tracks by the press of two buttons.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Footnotes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt; Channel Select buttons (buttons below the Faders) operate differently depending upon which Shift button is pressed.  While the left-side Shift is pressed, or when the Mixer is LINKED, the left 4 buttons select a new &amp;#039;Shift Mode&amp;#039;, while the right 4 buttons select a preset Device 5-8 (see below***).  When the right-side Shift is pressed, this behavior is reversed(i.e. preset Devices 1-4 on left, Mode on right).  &lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;**&amp;lt;/nowiki&amp;gt; Pad Translation works by reassigning the Channel/Identifier of each button.  In order to use it with Drum Racks, you must enable &amp;#039;Track Input&amp;#039; for the Ohm64&amp;#039;s MIDI Control Input, and assign that input as the source for the DrumRack&amp;#039;s input.  By default, Pad Translation transmits on MIDI Channel 10, but you can reassign this in the MonOhm_Map.py file to your liking.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;***&amp;lt;/nowiki&amp;gt; preset Device selection allows the user to select a predefined device instantly for editing with the Device knobs.  In order for this functionality to work, the Device must be renamed so that its first two characters are p1 thru p8.  Once named properly, the device may be selected by holding down a shift button and pressing one of the Channel Select buttons on the opposite side of the Ohm64 (e.g.  a device named &amp;#039;p1 Dub Delay&amp;#039; can be selected by holding down the right shift button and pressing the channel select underneath the 1st left side fader).&lt;br /&gt;
&lt;br /&gt;
[[File:Preset_example.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;****&amp;lt;/nowiki&amp;gt; when a Velocity plugin is inserted on a MIDI Track as the first plugin, any Fader currently controlling that Track will lock to its &amp;#039;Out Hi&amp;#039; parameter.  This allows the user to control the Volume of a MIDI only track.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*****&amp;lt;/nowiki&amp;gt; the Key buttons have specific functionality for each Monomodular client.  Generally, the first four control some aspect of the plugins operation, while the second four control the timing of the plugin.  However, see the individual helpfile contained in the client to find out exactly what they do for each one.  The Key buttons may be &amp;#039;Locked&amp;#039;, so that they are always accessible, by pressing the &amp;#039;Lock&amp;#039; button (the top-center Function button when in Monomodular Mode).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
phewww....I think that&amp;#039;s about it.&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=How_to_use_the_Ohm64_script&amp;diff=659</id>
		<title>How to use the Ohm64 script</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=How_to_use_the_Ohm64_script&amp;diff=659"/>
		<updated>2012-11-28T20:39:15Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Summary */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Some Video Tutorials ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=9ypoR7JH1cY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=8&amp;amp;feature=plcp  Earliest tutorial with old help patcher and little commentary]&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=00mlz1DpUTY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=7&amp;amp;feature=plcp b99 Release tutorial]&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
&lt;br /&gt;
The only component that is strictly necessary to get the Remote Script working in Ableton is the MonOhm Script itself.  It goes in the Live Application Bundle, in the &amp;quot;Remote Scripts&amp;quot; folder. &lt;br /&gt;
&lt;br /&gt;
If you&amp;#039;re using the Monomodular installer, this should take care of itself. If you&amp;#039;re installing just the MonOhm script, here&amp;#039;s where it goes:&lt;br /&gt;
&lt;br /&gt;
*Macintosh – Right click on the Ableton Live application icon and select &amp;quot;show package contents&amp;quot;. Put the MonOhm folder in Contents/App-Resources/MIDI Remote Scripts&lt;br /&gt;
*Windows - put the MonOhm folder in C:\Program Files\Ableton\Live 8.x.x\Resources\MIDI Remote Scripts&lt;br /&gt;
&lt;br /&gt;
In order to use the Monomodular portion of the script, it is necessary to have Max5.18 installed, and the client plugins that are contained in the suite. Monomodular&amp;#039;s functionality in a seperate place (see:  [[How_Monomodular_Works]]).  &lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
MonOhm consists of three independent mixers.  Two of them control four channels at a time, the third mixer uses all 8 faders to control 8 channels.&lt;br /&gt;
&lt;br /&gt;
Each mixer is independent, and remembers the last tracks that were assigned to it.  When the Ohm is first connected to Live, it will automatically be in split mixer mode.  If there are more than four tracks in the project, the mixer will be assigned to the first 8 tracks, otherwise both sides of the mixer will be assigned to whatever tracks are present. &lt;br /&gt;
&lt;br /&gt;
Since there are several different &amp;quot;shift modes&amp;quot; available within the script, the most important concept to grasp about this scheme is that there are two shift buttons:  one left, and one right.  They are on either side of the crossfader.  By holding down the shift button, you gain access to a bunch of different alternative functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Pete @Livid says this script melts peoples&amp;#039; brains.  Really, its not all that complicated.  I tried to fit as much functionality as I could into what was available on the controller, and I can understand why that&amp;#039;s intimidating.  But its very hard to get lost unless you insist on pressing more than one button at a time without knowing what the combination is going to do.  Make this thine performance mantra:  &amp;#039;I shall not press two buttons at once until I understand....&amp;#039;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Note: If you have Max4Live, I highly recommend using a copy of the LCD patch; in addition to letting you know at all times what it is that you are controlling, it will also tell you precisely what the values of your parameters are (in plainspeak, not MIDIeze). &amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== The Grid ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_assign_main.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rows 1-5:  Fire Session Clips&lt;br /&gt;
&lt;br /&gt;
Row 6:  Mute&lt;br /&gt;
&lt;br /&gt;
Row 7:  Solo&lt;br /&gt;
&lt;br /&gt;
Row 8:  Arm&lt;br /&gt;
&lt;br /&gt;
Exception:  When in Right Mixer Mode 4, The right side of the Grid is mapped to DrumRacks (Pad Translation;  see below**).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Shifted Grid ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments with Right Shift button pressed:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_shift_l.png]] &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments with Right Shift button pressed:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_shift_r.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rows 1-5(except for column 8):  Session Zoom Navigation&lt;br /&gt;
&lt;br /&gt;
Row 6:  Record, Overdub, Loop, Stop All Clips, Zero All Sends 1-4&lt;br /&gt;
&lt;br /&gt;
Row 7: Crossfader Assignment&lt;br /&gt;
&lt;br /&gt;
Row 8: Stop Clip&lt;br /&gt;
&lt;br /&gt;
Column 8 (Rows 1-5):  Fire Scene&lt;br /&gt;
&lt;br /&gt;
By holding down one of the shifts and pressing one of the channel select buttons on the same side of the controller, you can enter a different &amp;quot;Shift Mode&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Modes ==&lt;br /&gt;
&lt;br /&gt;
=== For the Left Mixer, Modes 1-4 ===&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Faders are always mapped to Track Volume (or MIDI Velocity...see below****).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm_func1_l.png‎|180px|thumb|left]] &lt;br /&gt;
|Left Mode 1:  Left Dials(top 8) control selected Device, Left Dials (bottom 4) control Selected Track&amp;#039;s Sends.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_l_func2.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 2:  Left Dials control Sends 1-3 for the corresponding Fader&amp;#039;s Track.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func3_l.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 3:  Left Dials (top 8) control Track Filter for corresponding Fader, Left Dials (bottom 4) control Pan for corresponding Fader.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func4_l.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 4:  Left Dials are remapped to channel 2 so that they are User Mappable with Live.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For the Right Mixer, Modes 1-4 ===&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm func1 2 3 r.png|180px|thumb|left]]&lt;br /&gt;
|Right Mode 1:  Faders control Track Volume, Mixer offset at Track 5, Right Dials control Returns 1-4.&lt;br /&gt;
&lt;br /&gt;
Right Mode 2:  Faders control Track Volume, Mixer offset at Track 9, Right Dials control Returns 1-4.&lt;br /&gt;
&lt;br /&gt;
Right Mode 3:  Faders control Track Volume, Mixer offset at Track 13, Right Dials control Returns 1-4. &lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func4_r.png|180px|thumb|left]]&lt;br /&gt;
|Right Mode 4:  Faders control Return Volume, Right Dials control Return Pan&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Buttons below the Faders select Track in all modes (except when shift is being held...see below*).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Functions ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Function Buttons (top right) have the following functions (top left to bottom right):&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm function assign.png|200px|thumb|left]] &lt;br /&gt;
|Session Nav up, Play, Stop, Session Nav down,  Session Nav left, Session Nav right.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Function Buttons (top right) have the following Shifted functions (top left to bottom right):&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm function assign shift.png|200px|thumb|left]] &lt;br /&gt;
|Device Bank up, Device ON/OFF, Device Lock, Device Bank down, Device Nav left, Device Nav right.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WHILE LEFT SHIFT IS PRESSED, FADER 8 CONTROLS MASTER VOLUME.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WHILE LEFT SHIFT IS PRESSED, RIGHT DIAL 4 CONTROLS PREHEAR.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
(Master/Prehear functionality can be defeated in the MonOhm_Map.py file....it has fubarred me several times when things are lagging, so its not necessarily recommended for performance situations)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== modMode ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm modGrid.png]]&lt;br /&gt;
&lt;br /&gt;
The Livid button (aka &amp;quot;Gary the Welder&amp;quot;) switches the grid to Monomodular Mode (aka &amp;quot;modMode&amp;quot;).  Most of the controls remain the same, but the grid is now used for controlling Monomodular patches. &lt;br /&gt;
&lt;br /&gt;
When in modMode, the Function buttons (unShifted) control the following(top left to bottom right):&lt;br /&gt;
&lt;br /&gt;
Grid Nav up, Lock (the bottom row of the grid remains &amp;#039;Shifted&amp;#039;), Alt (access to Preset management in enabled patches...see below*****), Grid Nav down, Grid Nav right, Grid Nav left.&lt;br /&gt;
&lt;br /&gt;
When in modMode, the Function buttons (Shifted) control the following(top left to bottom right).&lt;br /&gt;
&lt;br /&gt;
Device Bank up, Play, Stop, Device Bank down, Device Nav left, Device Nav right.&lt;br /&gt;
&lt;br /&gt;
Track selection and Mode navigation is identical in Monomodular Mode as in normal Session Mode.&lt;br /&gt;
&lt;br /&gt;
By pressing either of the shift buttons, Zoom mode is invoked.  In Zoom mode, the center lit square of buttons indicates the current selected quadrant.  By pressing an area of that square, the grid changes assignment to the corresponding area.  &lt;br /&gt;
&lt;br /&gt;
In Zoom mode, the top row of buttons selects the current Monomodular plugin.  The second row of buttons selects the channel that plugin transmits on (this is only useful when the plugins &amp;#039;nomeout&amp;#039; is enabled...see below*****).  The bottom row of buttons transmits &amp;#039;Key&amp;#039; data (these buttons have special functionality specific to each Monomodular client...see the documenation with the client to find out what they do).&lt;br /&gt;
&lt;br /&gt;
For further info on modMode, see the section on [[How_Monomodular_Works]].&lt;br /&gt;
&lt;br /&gt;
== Linked Mixer Mode ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_linked_mixer.png]]&lt;br /&gt;
&lt;br /&gt;
By holding one shift button and pressing the other, it is possible to link both mixers so they behave like a single one. In linked mode, all mode changes correspond to the descriptions of the Left Mixer, and the right dials remain locked to the Returns.  It is still possible to access the Master/Prehear levels by pressing Right Shift.  The linked mixer&amp;#039;s position (i.e. track assignment) will be recalled independently from the other two mixers, thus allowing easy navigation between 16 tracks by the press of two buttons.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Footnotes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt; Channel Select buttons (buttons below the Faders) operate differently depending upon which Shift button is pressed.  While the left-side Shift is pressed, or when the Mixer is LINKED, the left 4 buttons select a new &amp;#039;Shift Mode&amp;#039;, while the right 4 buttons select a preset Device 5-8 (see below***).  When the right-side Shift is pressed, this behavior is reversed(i.e. preset Devices 1-4 on left, Mode on right).  &lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;**&amp;lt;/nowiki&amp;gt; Pad Translation works by reassigning the Channel/Identifier of each button.  In order to use it with Drum Racks, you must enable &amp;#039;Track Input&amp;#039; for the Ohm64&amp;#039;s MIDI Control Input, and assign that input as the source for the DrumRack&amp;#039;s input.  By default, Pad Translation transmits on MIDI Channel 10, but you can reassign this in the MonOhm_Map.py file to your liking.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;***&amp;lt;/nowiki&amp;gt; preset Device selection allows the user to select a predefined device instantly for editing with the Device knobs.  In order for this functionality to work, the Device must be renamed so that its first two characters are p1 thru p8.  Once named properly, the device may be selected by holding down a shift button and pressing one of the Channel Select buttons on the opposite side of the Ohm64 (e.g.  a device named &amp;#039;p1 Dub Delay&amp;#039; can be selected by holding down the right shift button and pressing the channel select underneath the 1st left side fader).&lt;br /&gt;
&lt;br /&gt;
[[File:Preset_example.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;****&amp;lt;/nowiki&amp;gt; when a Velocity plugin is inserted on a MIDI Track as the first plugin, any Fader currently controlling that Track will lock to its &amp;#039;Out Hi&amp;#039; parameter.  This allows the user to control the Volume of a MIDI only track.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*****&amp;lt;/nowiki&amp;gt; the Key buttons have specific functionality for each Monomodular client.  Generally, the first four control some aspect of the plugins operation, while the second four control the timing of the plugin.  However, see the individual helpfile contained in the client to find out exactly what they do for each one.  The Key buttons may be &amp;#039;Locked&amp;#039;, so that they are always accessible, by pressing the &amp;#039;Lock&amp;#039; button (the top-center Function button when in Monomodular Mode).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
phewww....I think that&amp;#039;s about it.&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=How_to_use_the_Ohm64_script&amp;diff=658</id>
		<title>How to use the Ohm64 script</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=How_to_use_the_Ohm64_script&amp;diff=658"/>
		<updated>2012-11-28T20:35:38Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* modMode */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Some Video Tutorials ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=9ypoR7JH1cY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=8&amp;amp;feature=plcp  Earliest tutorial with old help patcher and little commentary]&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=00mlz1DpUTY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=7&amp;amp;feature=plcp b99 Release tutorial]&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
&lt;br /&gt;
The only component that is strictly necessary to get the Remote Script working in Ableton is the MonOhm Script itself.  It goes in the Live Application Bundle, in the &amp;quot;Remote Scripts&amp;quot; folder. &lt;br /&gt;
&lt;br /&gt;
If you&amp;#039;re using the Monomodular installer, this should take care of itself. If you&amp;#039;re installing just the MonOhm script, here&amp;#039;s where it goes:&lt;br /&gt;
&lt;br /&gt;
*Macintosh – Right click on the Ableton Live application icon and select &amp;quot;show package contents&amp;quot;. Put the MonOhm folder in Contents/App-Resources/MIDI Remote Scripts&lt;br /&gt;
*Windows - put the MonOhm folder in C:\Program Files\Ableton\Live 8.x.x\Resources\MIDI Remote Scripts&lt;br /&gt;
&lt;br /&gt;
In order to use the Monomodular portion of the script, it is necessary to have Max5.18 installed, and the client plugins that are contained in the suite. Monomodular&amp;#039;s functionality in a seperate place (see:  [[How_Monomodular_Works]]).  &lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
MonOhm consists of three independent mixers.  Two of them control four channels at a time, the third mixer uses all 8 faders to control 8 channels.&lt;br /&gt;
&lt;br /&gt;
Each mixer is independent, and remembers the last tracks that were assigned to it.  When the Ohm is first connected to Live, it will automatically be in split mixer mode.  If there are more than four tracks in the project, the mixer will be assigned to the first 8 tracks, otherwise both sides of the mixer will be assigned to whatever tracks are present. &lt;br /&gt;
&lt;br /&gt;
Since there are several different &amp;quot;shift modes&amp;quot; available within the script, the most important concept to grasp about this scheme is that there are two shift buttons:  one left, and one right.  They are on either side of the crossfader.  By holding down the shift button, you gain access to a bunch of different alternative functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Pete @Livid says this script melts peoples&amp;#039; brains.  Really, its not all that complicated.  I tried to fit as much functionality as I could into what was available on the controller, and I can understand why that&amp;#039;s intimidating.  But its very hard to get lost unless you insist on pressing more than one button at a time without knowing what the combination is going to do.  Make this thine performance mantra:  &amp;#039;I shall not press two buttons at once until I understand....&amp;#039;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Note: I highly recommend using a copy of the LCD patch; in addition to letting you know at all times what it is that you are controlling, it will also tell you precisely what the values of your parameters are (in plainspeak, not MIDIeze).  Of course, you&amp;#039;ll need m4l in order to use it.&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== The Grid ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_assign_main.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rows 1-5:  Fire Session Clips&lt;br /&gt;
&lt;br /&gt;
Row 6:  Mute&lt;br /&gt;
&lt;br /&gt;
Row 7:  Solo&lt;br /&gt;
&lt;br /&gt;
Row 8:  Arm&lt;br /&gt;
&lt;br /&gt;
Exception:  When in Right Mixer Mode 4, The right side of the Grid is mapped to DrumRacks (Pad Translation;  see below**).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Shifted Grid ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments with Right Shift button pressed:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_shift_l.png]] &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments with Right Shift button pressed:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_shift_r.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rows 1-5(except for column 8):  Session Zoom Navigation&lt;br /&gt;
&lt;br /&gt;
Row 6:  Record, Overdub, Loop, Stop All Clips, Zero All Sends 1-4&lt;br /&gt;
&lt;br /&gt;
Row 7: Crossfader Assignment&lt;br /&gt;
&lt;br /&gt;
Row 8: Stop Clip&lt;br /&gt;
&lt;br /&gt;
Column 8 (Rows 1-5):  Fire Scene&lt;br /&gt;
&lt;br /&gt;
By holding down one of the shifts and pressing one of the channel select buttons on the same side of the controller, you can enter a different &amp;quot;Shift Mode&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Modes ==&lt;br /&gt;
&lt;br /&gt;
=== For the Left Mixer, Modes 1-4 ===&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Faders are always mapped to Track Volume (or MIDI Velocity...see below****).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm_func1_l.png‎|180px|thumb|left]] &lt;br /&gt;
|Left Mode 1:  Left Dials(top 8) control selected Device, Left Dials (bottom 4) control Selected Track&amp;#039;s Sends.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_l_func2.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 2:  Left Dials control Sends 1-3 for the corresponding Fader&amp;#039;s Track.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func3_l.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 3:  Left Dials (top 8) control Track Filter for corresponding Fader, Left Dials (bottom 4) control Pan for corresponding Fader.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func4_l.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 4:  Left Dials are remapped to channel 2 so that they are User Mappable with Live.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For the Right Mixer, Modes 1-4 ===&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm func1 2 3 r.png|180px|thumb|left]]&lt;br /&gt;
|Right Mode 1:  Faders control Track Volume, Mixer offset at Track 5, Right Dials control Returns 1-4.&lt;br /&gt;
&lt;br /&gt;
Right Mode 2:  Faders control Track Volume, Mixer offset at Track 9, Right Dials control Returns 1-4.&lt;br /&gt;
&lt;br /&gt;
Right Mode 3:  Faders control Track Volume, Mixer offset at Track 13, Right Dials control Returns 1-4. &lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func4_r.png|180px|thumb|left]]&lt;br /&gt;
|Right Mode 4:  Faders control Return Volume, Right Dials control Return Pan&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Buttons below the Faders select Track in all modes (except when shift is being held...see below*).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Functions ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Function Buttons (top right) have the following functions (top left to bottom right):&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm function assign.png|200px|thumb|left]] &lt;br /&gt;
|Session Nav up, Play, Stop, Session Nav down,  Session Nav left, Session Nav right.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Function Buttons (top right) have the following Shifted functions (top left to bottom right):&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm function assign shift.png|200px|thumb|left]] &lt;br /&gt;
|Device Bank up, Device ON/OFF, Device Lock, Device Bank down, Device Nav left, Device Nav right.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WHILE LEFT SHIFT IS PRESSED, FADER 8 CONTROLS MASTER VOLUME.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WHILE LEFT SHIFT IS PRESSED, RIGHT DIAL 4 CONTROLS PREHEAR.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
(Master/Prehear functionality can be defeated in the MonOhm_Map.py file....it has fubarred me several times when things are lagging, so its not necessarily recommended for performance situations)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== modMode ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm modGrid.png]]&lt;br /&gt;
&lt;br /&gt;
The Livid button (aka &amp;quot;Gary the Welder&amp;quot;) switches the grid to Monomodular Mode (aka &amp;quot;modMode&amp;quot;).  Most of the controls remain the same, but the grid is now used for controlling Monomodular patches. &lt;br /&gt;
&lt;br /&gt;
When in modMode, the Function buttons (unShifted) control the following(top left to bottom right):&lt;br /&gt;
&lt;br /&gt;
Grid Nav up, Lock (the bottom row of the grid remains &amp;#039;Shifted&amp;#039;), Alt (access to Preset management in enabled patches...see below*****), Grid Nav down, Grid Nav right, Grid Nav left.&lt;br /&gt;
&lt;br /&gt;
When in modMode, the Function buttons (Shifted) control the following(top left to bottom right).&lt;br /&gt;
&lt;br /&gt;
Device Bank up, Play, Stop, Device Bank down, Device Nav left, Device Nav right.&lt;br /&gt;
&lt;br /&gt;
Track selection and Mode navigation is identical in Monomodular Mode as in normal Session Mode.&lt;br /&gt;
&lt;br /&gt;
By pressing either of the shift buttons, Zoom mode is invoked.  In Zoom mode, the center lit square of buttons indicates the current selected quadrant.  By pressing an area of that square, the grid changes assignment to the corresponding area.  &lt;br /&gt;
&lt;br /&gt;
In Zoom mode, the top row of buttons selects the current Monomodular plugin.  The second row of buttons selects the channel that plugin transmits on (this is only useful when the plugins &amp;#039;nomeout&amp;#039; is enabled...see below*****).  The bottom row of buttons transmits &amp;#039;Key&amp;#039; data (these buttons have special functionality specific to each Monomodular client...see the documenation with the client to find out what they do).&lt;br /&gt;
&lt;br /&gt;
For further info on modMode, see the section on [[How_Monomodular_Works]].&lt;br /&gt;
&lt;br /&gt;
== Linked Mixer Mode ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_linked_mixer.png]]&lt;br /&gt;
&lt;br /&gt;
By holding one shift button and pressing the other, it is possible to link both mixers so they behave like a single one. In linked mode, all mode changes correspond to the descriptions of the Left Mixer, and the right dials remain locked to the Returns.  It is still possible to access the Master/Prehear levels by pressing Right Shift.  The linked mixer&amp;#039;s position (i.e. track assignment) will be recalled independently from the other two mixers, thus allowing easy navigation between 16 tracks by the press of two buttons.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Footnotes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt; Channel Select buttons (buttons below the Faders) operate differently depending upon which Shift button is pressed.  While the left-side Shift is pressed, or when the Mixer is LINKED, the left 4 buttons select a new &amp;#039;Shift Mode&amp;#039;, while the right 4 buttons select a preset Device 5-8 (see below***).  When the right-side Shift is pressed, this behavior is reversed(i.e. preset Devices 1-4 on left, Mode on right).  &lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;**&amp;lt;/nowiki&amp;gt; Pad Translation works by reassigning the Channel/Identifier of each button.  In order to use it with Drum Racks, you must enable &amp;#039;Track Input&amp;#039; for the Ohm64&amp;#039;s MIDI Control Input, and assign that input as the source for the DrumRack&amp;#039;s input.  By default, Pad Translation transmits on MIDI Channel 10, but you can reassign this in the MonOhm_Map.py file to your liking.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;***&amp;lt;/nowiki&amp;gt; preset Device selection allows the user to select a predefined device instantly for editing with the Device knobs.  In order for this functionality to work, the Device must be renamed so that its first two characters are p1 thru p8.  Once named properly, the device may be selected by holding down a shift button and pressing one of the Channel Select buttons on the opposite side of the Ohm64 (e.g.  a device named &amp;#039;p1 Dub Delay&amp;#039; can be selected by holding down the right shift button and pressing the channel select underneath the 1st left side fader).&lt;br /&gt;
&lt;br /&gt;
[[File:Preset_example.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;****&amp;lt;/nowiki&amp;gt; when a Velocity plugin is inserted on a MIDI Track as the first plugin, any Fader currently controlling that Track will lock to its &amp;#039;Out Hi&amp;#039; parameter.  This allows the user to control the Volume of a MIDI only track.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*****&amp;lt;/nowiki&amp;gt; the Key buttons have specific functionality for each Monomodular client.  Generally, the first four control some aspect of the plugins operation, while the second four control the timing of the plugin.  However, see the individual helpfile contained in the client to find out exactly what they do for each one.  The Key buttons may be &amp;#039;Locked&amp;#039;, so that they are always accessible, by pressing the &amp;#039;Lock&amp;#039; button (the top-center Function button when in Monomodular Mode).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
phewww....I think that&amp;#039;s about it.&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
	<entry>
		<id>https://aumhaa.com/wiki/index.php?title=How_to_use_the_Ohm64_script&amp;diff=657</id>
		<title>How to use the Ohm64 script</title>
		<link rel="alternate" type="text/html" href="https://aumhaa.com/wiki/index.php?title=How_to_use_the_Ohm64_script&amp;diff=657"/>
		<updated>2012-11-28T20:33:20Z</updated>

		<summary type="html">&lt;p&gt;Okyeron: /* Summary */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Some Video Tutorials ==&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=9ypoR7JH1cY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=8&amp;amp;feature=plcp  Earliest tutorial with old help patcher and little commentary]&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=00mlz1DpUTY&amp;amp;list=UUffhayZv3WqTz2ZaEkIwR3w&amp;amp;index=7&amp;amp;feature=plcp b99 Release tutorial]&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
&lt;br /&gt;
The only component that is strictly necessary to get the Remote Script working in Ableton is the MonOhm Script itself.  It goes in the Live Application Bundle, in the &amp;quot;Remote Scripts&amp;quot; folder. &lt;br /&gt;
&lt;br /&gt;
If you&amp;#039;re using the Monomodular installer, this should take care of itself. If you&amp;#039;re installing just the MonOhm script, here&amp;#039;s where it goes:&lt;br /&gt;
&lt;br /&gt;
*Macintosh – Right click on the Ableton Live application icon and select &amp;quot;show package contents&amp;quot;. Put the MonOhm folder in Contents/App-Resources/MIDI Remote Scripts&lt;br /&gt;
*Windows - put the MonOhm folder in C:\Program Files\Ableton\Live 8.x.x\Resources\MIDI Remote Scripts&lt;br /&gt;
&lt;br /&gt;
In order to use the Monomodular portion of the script, it is necessary to have Max5.18 installed, and the client plugins that are contained in the suite. Monomodular&amp;#039;s functionality in a seperate place (see:  [[How_Monomodular_Works]]).  &lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
MonOhm consists of three independent mixers.  Two of them control four channels at a time, the third mixer uses all 8 faders to control 8 channels.&lt;br /&gt;
&lt;br /&gt;
Each mixer is independent, and remembers the last tracks that were assigned to it.  When the Ohm is first connected to Live, it will automatically be in split mixer mode.  If there are more than four tracks in the project, the mixer will be assigned to the first 8 tracks, otherwise both sides of the mixer will be assigned to whatever tracks are present. &lt;br /&gt;
&lt;br /&gt;
Since there are several different &amp;quot;shift modes&amp;quot; available within the script, the most important concept to grasp about this scheme is that there are two shift buttons:  one left, and one right.  They are on either side of the crossfader.  By holding down the shift button, you gain access to a bunch of different alternative functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Pete @Livid says this script melts peoples&amp;#039; brains.  Really, its not all that complicated.  I tried to fit as much functionality as I could into what was available on the controller, and I can understand why that&amp;#039;s intimidating.  But its very hard to get lost unless you insist on pressing more than one button at a time without knowing what the combination is going to do.  Make this thine performance mantra:  &amp;#039;I shall not press two buttons at once until I understand....&amp;#039;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Note: I highly recommend using a copy of the LCD patch; in addition to letting you know at all times what it is that you are controlling, it will also tell you precisely what the values of your parameters are (in plainspeak, not MIDIeze).  Of course, you&amp;#039;ll need m4l in order to use it.&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== The Grid ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_assign_main.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rows 1-5:  Fire Session Clips&lt;br /&gt;
&lt;br /&gt;
Row 6:  Mute&lt;br /&gt;
&lt;br /&gt;
Row 7:  Solo&lt;br /&gt;
&lt;br /&gt;
Row 8:  Arm&lt;br /&gt;
&lt;br /&gt;
Exception:  When in Right Mixer Mode 4, The right side of the Grid is mapped to DrumRacks (Pad Translation;  see below**).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Shifted Grid ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments with Right Shift button pressed:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_shift_l.png]] &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments with Right Shift button pressed:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_shift_r.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rows 1-5(except for column 8):  Session Zoom Navigation&lt;br /&gt;
&lt;br /&gt;
Row 6:  Record, Overdub, Loop, Stop All Clips, Zero All Sends 1-4&lt;br /&gt;
&lt;br /&gt;
Row 7: Crossfader Assignment&lt;br /&gt;
&lt;br /&gt;
Row 8: Stop Clip&lt;br /&gt;
&lt;br /&gt;
Column 8 (Rows 1-5):  Fire Scene&lt;br /&gt;
&lt;br /&gt;
By holding down one of the shifts and pressing one of the channel select buttons on the same side of the controller, you can enter a different &amp;quot;Shift Mode&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Modes ==&lt;br /&gt;
&lt;br /&gt;
=== For the Left Mixer, Modes 1-4 ===&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Faders are always mapped to Track Volume (or MIDI Velocity...see below****).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm_func1_l.png‎|180px|thumb|left]] &lt;br /&gt;
|Left Mode 1:  Left Dials(top 8) control selected Device, Left Dials (bottom 4) control Selected Track&amp;#039;s Sends.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_l_func2.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 2:  Left Dials control Sends 1-3 for the corresponding Fader&amp;#039;s Track.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func3_l.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 3:  Left Dials (top 8) control Track Filter for corresponding Fader, Left Dials (bottom 4) control Pan for corresponding Fader.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func4_l.png|180px|thumb|left]] &lt;br /&gt;
|Left Mode 4:  Left Dials are remapped to channel 2 so that they are User Mappable with Live.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For the Right Mixer, Modes 1-4 ===&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm func1 2 3 r.png|180px|thumb|left]]&lt;br /&gt;
|Right Mode 1:  Faders control Track Volume, Mixer offset at Track 5, Right Dials control Returns 1-4.&lt;br /&gt;
&lt;br /&gt;
Right Mode 2:  Faders control Track Volume, Mixer offset at Track 9, Right Dials control Returns 1-4.&lt;br /&gt;
&lt;br /&gt;
Right Mode 3:  Faders control Track Volume, Mixer offset at Track 13, Right Dials control Returns 1-4. &lt;br /&gt;
|-&lt;br /&gt;
|[[File:Monohm_func4_r.png|180px|thumb|left]]&lt;br /&gt;
|Right Mode 4:  Faders control Return Volume, Right Dials control Return Pan&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Buttons below the Faders select Track in all modes (except when shift is being held...see below*).&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Functions ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Function Buttons (top right) have the following functions (top left to bottom right):&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm function assign.png|200px|thumb|left]] &lt;br /&gt;
|Session Nav up, Play, Stop, Session Nav down,  Session Nav left, Session Nav right.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Function Buttons (top right) have the following Shifted functions (top left to bottom right):&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;color:black; background-color:white;&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|[[File:Monohm function assign shift.png|200px|thumb|left]] &lt;br /&gt;
|Device Bank up, Device ON/OFF, Device Lock, Device Bank down, Device Nav left, Device Nav right.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WHILE LEFT SHIFT IS PRESSED, FADER 8 CONTROLS MASTER VOLUME.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WHILE LEFT SHIFT IS PRESSED, RIGHT DIAL 4 CONTROLS PREHEAR.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
(Master/Prehear functionality can be defeated in the MonOhm_Map.py file....it has fubarred me several times when things are lagging, so its not necessarily recommended for performance situations)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== modMode ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm modGrid.png]]&lt;br /&gt;
&lt;br /&gt;
The Livid button switches the grid to Monomodular Mode (i.e. modMode).  Most of the controls remain the same, but the grid is now used for controlling Monomodular patches. &lt;br /&gt;
&lt;br /&gt;
When in modMode, the Function buttons (unShifted) control the following(top left to bottom right):&lt;br /&gt;
&lt;br /&gt;
Grid Nav up, Lock (the bottom row of the grid remains &amp;#039;Shifted&amp;#039;), Alt (access to Preset management in enabled patches...see below*****), Grid Nav down, Grid Nav right, Grid Nav left.&lt;br /&gt;
&lt;br /&gt;
When in modMode, the Function buttons (Shifted) control the following(top left to bottom right).&lt;br /&gt;
&lt;br /&gt;
Device Bank up, Play, Stop, Device Bank down, Device Nav left, Device Nav right.&lt;br /&gt;
&lt;br /&gt;
Track selection and Mode navigation is identical in Monomodular Mode as in normal Session Mode.&lt;br /&gt;
&lt;br /&gt;
By pressing either of the shift buttons, Zoom mode is invoked.  In Zoom mode, the center lit square of buttons indicates the current selected quadrant.  By pressing an area of that square, the grid changes assignment to the corresponding area.  &lt;br /&gt;
&lt;br /&gt;
In Zoom mode, the top row of buttons selects the current Monomodular plugin.  The second row of buttons selects the channel that plugin transmits on (this is only useful when the plugins &amp;#039;nomeout&amp;#039; is enabled...see below*****).  The bottom row of buttons transmits &amp;#039;Key&amp;#039; data (these buttons have special functionality specific to each Monomodular client...see the documenation with the client to find out what they do).&lt;br /&gt;
&lt;br /&gt;
For further info on modMode, see the section on [[How_Monomodular_Works]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Linked Mixer Mode ==&lt;br /&gt;
&lt;br /&gt;
[[File:Monohm_linked_mixer.png]]&lt;br /&gt;
&lt;br /&gt;
By holding one shift button and pressing the other, it is possible to link both mixers so they behave like a single one. In linked mode, all mode changes correspond to the descriptions of the Left Mixer, and the right dials remain locked to the Returns.  It is still possible to access the Master/Prehear levels by pressing Right Shift.  The linked mixer&amp;#039;s position (i.e. track assignment) will be recalled independently from the other two mixers, thus allowing easy navigation between 16 tracks by the press of two buttons.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Footnotes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt; Channel Select buttons (buttons below the Faders) operate differently depending upon which Shift button is pressed.  While the left-side Shift is pressed, or when the Mixer is LINKED, the left 4 buttons select a new &amp;#039;Shift Mode&amp;#039;, while the right 4 buttons select a preset Device 5-8 (see below***).  When the right-side Shift is pressed, this behavior is reversed(i.e. preset Devices 1-4 on left, Mode on right).  &lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;**&amp;lt;/nowiki&amp;gt; Pad Translation works by reassigning the Channel/Identifier of each button.  In order to use it with Drum Racks, you must enable &amp;#039;Track Input&amp;#039; for the Ohm64&amp;#039;s MIDI Control Input, and assign that input as the source for the DrumRack&amp;#039;s input.  By default, Pad Translation transmits on MIDI Channel 10, but you can reassign this in the MonOhm_Map.py file to your liking.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;***&amp;lt;/nowiki&amp;gt; preset Device selection allows the user to select a predefined device instantly for editing with the Device knobs.  In order for this functionality to work, the Device must be renamed so that its first two characters are p1 thru p8.  Once named properly, the device may be selected by holding down a shift button and pressing one of the Channel Select buttons on the opposite side of the Ohm64 (e.g.  a device named &amp;#039;p1 Dub Delay&amp;#039; can be selected by holding down the right shift button and pressing the channel select underneath the 1st left side fader).&lt;br /&gt;
&lt;br /&gt;
[[File:Preset_example.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;****&amp;lt;/nowiki&amp;gt; when a Velocity plugin is inserted on a MIDI Track as the first plugin, any Fader currently controlling that Track will lock to its &amp;#039;Out Hi&amp;#039; parameter.  This allows the user to control the Volume of a MIDI only track.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*****&amp;lt;/nowiki&amp;gt; the Key buttons have specific functionality for each Monomodular client.  Generally, the first four control some aspect of the plugins operation, while the second four control the timing of the plugin.  However, see the individual helpfile contained in the client to find out exactly what they do for each one.  The Key buttons may be &amp;#039;Locked&amp;#039;, so that they are always accessible, by pressing the &amp;#039;Lock&amp;#039; button (the top-center Function button when in Monomodular Mode).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
phewww....I think that&amp;#039;s about it.&lt;/div&gt;</summary>
		<author><name>Okyeron</name></author>
		
	</entry>
</feed>