How Mod Works - Revision history

Amounra at 05:08, 6 April 2015

2015-04-06T05:08:58Z

Amounra: /* Mod Timing */

2015-03-31T18:46:30Z

‎Mod Timing

Amounra: /* Mod Timing */

2015-03-31T18:30:23Z

‎Mod Timing

Amounra at 18:29, 31 March 2015

2015-03-31T18:29:05Z

Amounra: Amounra moved page How Monomodular Works to How Mod Works: Changed project name

2015-03-31T17:54:29Z

Amounra moved page How Monomodular Works to How Mod Works: Changed project name

Okyeron: /* Supported Controllers */

2012-11-28T20:41:50Z

‎Supported Controllers

Amounra: /* Supported Controllers */

2012-11-13T05:00:50Z

‎Supported Controllers

Ground state: style cleanup; "Supported Controllers" section now mirrors the same section from the Main Page

2012-06-29T17:54:33Z

style cleanup; "Supported Controllers" section now mirrors the same section from the Main Page

Amounra: /* Supported Controllers */

2012-03-18T08:25:50Z

‎Supported Controllers

Amounra: /* Input and Output Settings */

2012-03-17T22:53:00Z

‎Input and Output Settings

@@ Line 1: / Line 1: @@
-Mod is the hub of all communcations between [[Mods]] and their Mod capable controllers.  Each client control script works in its own way, but the Mod standard is shared between all of them.
+Mod is the hub of all communcations between [[Mods]] and their Mod capable controllers.  Each client control script works in a unique way, but most of them share some standard features when it comes to manipulating the m4l patches they are designed to interact with.
-Mod 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 Mod design is that it has an 8x8 grid of buttons.  Other functionality is present on some controllers, but mainly, it works like this:
+Mod 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 Mod design is that it has an 8x8 grid of buttons.  Other functionality is present on some controllers, but the main features of Mod are encapsulated below.
 == The Grid ==

← Older revision		Revision as of 18:46, 31 March 2015
Line 41:		Line 41:


−	== ~~Mod~~ Timing ==	+	== mod Timing ==

	Most of the Mods have their own internal timing engine that is sync'ed to Live's clock. This, however, may be disengaged in order to trigger the timing process of the plugin from an external source (see below).		Most of the Mods have their own internal timing engine that is sync'ed to Live's clock. This, however, may be disengaged in order to trigger the timing process of the plugin from an external source (see below).

@@ Line 49: / Line 49: @@
 [[File:Grid timing.png]]
-In addition to the key controls, most Mods also have a 'Timing Multiplier', which speeds the timing engine up by the chosen amount.
+In addition to the modKey controls, most Mods also have a 'Timing Multiplier', which speeds the timing engine up by the chosen amount.
 == Input and Output Settings ==

@@ Line 1: / Line 1: @@
-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.
+Mod is the hub of all communcations between [[Mods]] and their Mod capable controllers.  Each client control script works in its own way, but the Mod standard is shared between all of them.
-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:
+Mod 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 Mod design is that it has an 8x8 grid of buttons.  Other functionality is present on some controllers, but mainly, it works like this:
 == The Grid ==
-There is an 8x8 grid, which represents one quadrant of the Monome256 workspace in its normal mode.
+Since each supported controller has a different layout, the grid and its assignments will vary between different mods depending on the controller that you're using to access it.
-In addition, it will display generic information about the status of Monomodular and its connected Mods when using the other controls below.
+Mod provides a way to access a 256 cells (16x16) grid even even when the controller itself has a smaller workspace.  Although some mods use a smaller, fixed workspace, others (specifically mods which are ported from monome applications) utilize the full grid of 256 cells and only display a portion of the workspace at any given time.  It is possible to navigate the currently viewed portion of the grid on within these mods by using the modNav buttons, or pressing shift and using the grid buttons to select the currently viewed portion of the grid.
 If you are not familiar with how a monome works, you might want to check this out:
@@ Line 18: / Line 20: @@
 http://monome.org/
-There is a Shift button, which, when pressed,  does the following:
+== The modShift Button ==
-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).
+The modShift button generally  does the following:
-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.
+The modShift button, while pressed or locked, allows navigation to the selected viewing area of the 256Grid on mods that support a full grid.  When active, the grid will light to indicate which area is currently selected (either by colors or by different flashing states).
-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.
+On most controllers, while holding down modShift and pressing one buttons on the top row of the grid allows the user to select a new device in Live via the [[Device Selector]].
-It causes the bottom row of buttons to change over to 'Key Mode', 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 'mode', and the second four control timing of the Mod if it is slaved to its internal clock.
+For "Legacy Mode" mods, holding down modShift and pressing one of the buttons on the second row from the top of the grid allows the user to change the MIDI output channel on mods that support multi-channel MIDI transmission.
-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.
+It causes the bottom row of buttons to change over to 'modKey Mode', and their status to be updated accordingly.  The modKey buttons are patch specific in functionality, but there are general conventions about how they are used in most of the mods.  Most of the time the left four will indicate and change the mod's 'mode', and the second four control timing of the mod if it is slaved to its internal clock.
 [[File:8x8_shift.png]]
-== The Lock Button ==
+== The modAlt Button ==
-: View mod in Live.  This will bring up the mod's device in Lives detail view, and consequently select the track that it'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.
+By pressing the dedicated "modAlt" button on the controller, it is possible to access additional functionality from the "modKey" buttons as well as mod specific functionality (see the description of each mod for information on how this works for the specific implementation).
@@ Line 98: / Line 61: @@
 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's channel setting has no effect, since Live does not care at all which channel MIDI data is transmitted on internally.
 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.

@@ Line 120: / Line 120: @@
 *[[How to use the LaunchMod script|Details for the Launchpad]]
-*[[How to use the Ohm64 script|Details for the Ohm64]]
+*[[How to use the Ohm64 script|Details for the Ohm64 and Ohm64 RGB]]
 *[[How to use the AumTroll script|Details for the CNTRL:R]]

← Older revision	Revision as of 17:54, 31 March 2015
(No difference)

← Older revision		Revision as of 05:00, 13 November 2012
Line 121:		Line 121:

	*[[How to use the Ohm64 script\|Details for the Ohm64]]		*[[How to use the Ohm64 script\|Details for the Ohm64]]
		+
		+	*[[How to use the AumTroll script\|Details for the CNTRL:R]]

@@ Line 4: / Line 4: @@
 == The Grid ==
 There is an 8x8 grid, which represents one quadrant of the Monome256 workspace in its normal mode.
@@ Line 22: / Line 20: @@
 But chances are if you've made it this far, you probably already know about monomes (and want one of your own!).  Good thing for you, here it is.....
 There is a Shift button, which, when pressed,  does the following:
@@ Line 39: / Line 37: @@
 [[File:8x8_shift.png]]
 There is a Lock button, which toggles whether the bottom row is 'shift-locked' to permanently be used in 'Key Mode'.
@@ Line 46: / Line 44: @@
 [[File:8x8grid_locked.png]]
-== '''The Alt Button''' ==
 By pressing the dedicated "alt" button on the controller, it is possible to access additional functionality from the "Key" buttons.  If there are no dedicated key buttons, the user can either engage "lock", or hold "shift" before pressing pressing "alt" and use the bottom row of grid buttons to access these functions.
@@ Line 64: / Line 63: @@
 [[File:8x8grid_alt.png]]
-=='''MonoLinkComponent'''==
 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 'bridge' applications running in the background.  The MonoLinkComponent is currently considered "beta"  (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.
@@ Line 70: / Line 70: @@
 For more info:  [[MonoLinkComponent]]
-== '''Mod Order''' ==
 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's user interface (white block means 1-8, black block means 9-16).  You can, however, change this enumeration manually in the plugin'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.
@@ Line 76: / Line 77: @@
 [[File:Block1.png]]
-== '''Mod Timing''' ==
 Most of the Mods have their own internal timing engine that is sync'ed to Live's clock.  This, however, may be disengaged in order to trigger the timing process of the plugin from an external source (see below).
@@ Line 84: / Line 86: @@
 [[File:Grid timing.png]]
-== '''Input and Output Settings''' ==
+== Input and Output Settings ==
 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.
 To change these settings, press the 'MIDI' button.  This will bring up a floating window with that Mod's MIDI settings.
 [[File:Mod midi settings.png]]
 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's channel setting has no effect, since Live does not care at all which channel MIDI data is transmitted on internally.
@@ Line 105: / Line 105: @@
 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 'Internal' button on the MIDI configuration page.
-For a detailed description of the rest of a control scripts functionality, please refer to the links below:
+== Supported Controllers ==
-[[How to use the Ohm64 script]]
+*[[How to use the AumPC scripts|Details for the APC]]
-[[How to use the BlockMod script]]
+*[[How to use the BlockMod script|Details for the Block]]
-[[How to use the LaunchMod script]]
+*[[How to use the Codec script|Details for the Code]]
-[[How to use the Codec script]]
+*[[How to use the iOs scripts|Details for the iPad]]
-[[How to use the AumPC scripts]]
+*[[How to use the LaunchMod script|Details for the Launchpad]]
-[[How to use the iOs scripts]]
+*[[How to use the Ohm64 script|Details for the Ohm64]]

← Older revision		Revision as of 08:25, 18 March 2012
Line 118:		Line 118:

	[[How to use the AumPC scripts]]		[[How to use the AumPC scripts]]
		+
		+	[[How to use the iOs scripts]]

← Older revision		Revision as of 22:53, 17 March 2012
Line 92:		Line 92:

	To change these settings, press the 'MIDI' button. This will bring up a floating window with that Mod's MIDI settings.		To change these settings, press the 'MIDI' button. This will bring up a floating window with that Mod's MIDI settings.
		+
		+
		+	[[File:Mod midi settings.png]]
		+

	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's channel setting has no effect, since Live does not care at all which channel MIDI data is transmitted on internally.		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's channel setting has no effect, since Live does not care at all which channel MIDI data is transmitted on internally.