Mods - Revision history

Amounra at 20:58, 31 March 2015

2015-03-31T20:58:57Z

Amounra at 20:49, 31 March 2015

2015-03-31T20:49:53Z

Amounra: /* Real mods */

2015-03-30T03:30:31Z

‎Real mods

Amounra at 03:29, 30 March 2015

2015-03-30T03:29:12Z

Amounra at 03:11, 30 March 2015

2015-03-30T03:11:13Z

Amounra: /* hex */

2012-11-03T05:24:14Z

‎hex

Amounra at 05:23, 3 November 2012

2012-11-03T05:23:36Z

Amounra: /* AumPad and Aum256 */

2012-03-24T03:32:00Z

‎AumPad and Aum256

Amounra at 23:28, 23 March 2012

2012-03-23T23:28:45Z

Amounra: /* AumPad and Aum256 */

2012-03-19T22:26:45Z

‎AumPad and Aum256

← Older revision		Revision as of 20:58, 31 March 2015
Line 1:		Line 1:
−	A 'mod' is just a convenient name for ~~m4l patches~~ designed to be used within the Mod framework. They all share at least one thing: they contain a javascript object that communicates directly with the control surface scripts included with the Mod package. An explanation of how this works, and examples of ways to use certain parts of the javascript, are contained in the [[help\|Monomods_help]] patch that is installed in the folder with the rest of the mods.	+	A 'mod' is just a convenient name for a Max for Live patche designed to be used within the Mod framework. They all share at least one thing: they contain a javascript object that communicates directly with the control surface scripts included with the Mod package. An explanation of how this works, and examples of ways to use certain parts of the javascript, are contained in the [[help\|Monomods_help]] patch that is installed in the folder with the rest of the mods.

	Some of the mods are creations of amounra, while others are ports of Monome patches (mostly Stretta's). Each one will function in an independant way, but most have some common features. To learn about the common ground that all plugins share, you should take a look at the [[How Mod Works]] page. The specifics of each, however, are described on the following pages (see details by clicking on the header of each of the following summaries):		Some of the mods are creations of amounra, while others are ports of Monome patches (mostly Stretta's). Each one will function in an independant way, but most have some common features. To learn about the common ground that all plugins share, you should take a look at the [[How Mod Works]] page. The specifics of each, however, are described on the following pages (see details by clicking on the header of each of the following summaries):

← Older revision		Revision as of 20:49, 31 March 2015
Line 1:		Line 1:
−	A 'mod' is just a convenient name for m4l patches designed to be used ~~with~~ Mod. They all share at least one thing: they contain a javascript object that communicates directly with the ~~Mod Python script, which in turn communicates with mod embedded _Framework~~ control surface scripts. An explanation of how this works, and examples of ways to use certain parts of the javascript, are contained in the [[help\|Monomods_help]] patch that is installed in the folder with the rest of the mods.	+	A 'mod' is just a convenient name for m4l patches designed to be used within the Mod framework. They all share at least one thing: they contain a javascript object that communicates directly with the control surface scripts included with the Mod package. An explanation of how this works, and examples of ways to use certain parts of the javascript, are contained in the [[help\|Monomods_help]] patch that is installed in the folder with the rest of the mods.

−	Some of the mods are creations of amounra, while others are ports of Monome patches (mostly Stretta's). Each one will function in an independant way, but ~~they all~~ have ~~several things in~~ common ~~with one another~~. To learn about the common ground that all plugins share, you should take a look at the [[How ~~Monomodular~~ Works]] page. The specifics of each ~~mod~~, however, are ~~covered~~ on the following pages ~~that can reached~~ by clicking on the header of each of the following summaries:	+	Some of the mods are creations of amounra, while others are ports of Monome patches (mostly Stretta's). Each one will function in an independant way, but most have some common features. To learn about the common ground that all plugins share, you should take a look at the [[How Mod Works]] page. The specifics of each, however, are described on the following pages (see details by clicking on the header of each of the following summaries):

@@ Line 28: / Line 28: @@
 [[File:Endcoders_pic.png]]
 A Livid Code based script designed to easily assign dials to Live's parameters.  Adaptable to just about any controller with knobs or encoders.
 === [[life]] ===
@@ Line 52: / Line 46: @@
 A simple triggering device that allows assignment of the grids keys to different notes and MIDI/Nome channels.
 === [[tr256|TR256]] ===
@@ Line 82: / Line 70: @@
 Polyrhythmic mother ship.  A bunch of guys came up with this one....Stretta was involved.
 === [[boiingg]] ===

@@ Line 1: / Line 1: @@
-A 'mod' is just a convenient name for m4l patches designed to be used with Mod.  They all share at least one thing:  they contain a javascript object that communicates directly with the Monomodular Python script, which in turn communicates with Mod embedded _Framework control surface scripts.  An explanation of how this works, and examples of ways to use certain parts of the javascript, are contained in the [[help|Monomods_help]] patch that is installed in the folder with the rest of the Mods.
+A 'mod' is just a convenient name for m4l patches designed to be used with Mod.  They all share at least one thing:  they contain a javascript object that communicates directly with the Mod Python script, which in turn communicates with mod embedded _Framework control surface scripts.  An explanation of how this works, and examples of ways to use certain parts of the javascript, are contained in the [[help|Monomods_help]] patch that is installed in the folder with the rest of the mods.
 Some of the mods are creations of amounra, while others are ports of Monome patches (mostly Stretta's).  Each one will function in an independant way, but they all have several things in common with one another.  To learn about the common ground that all plugins share, you should take a look at the [[How Monomodular Works]] page.  The specifics of each mod, however, are covered on the following pages that can reached by clicking on the header of each of the following summaries:
@@ Line 10: / Line 10: @@
 [[File:Hex pic a.png]]
-This Mod is actually built for CNTRL:R, but in short order will also become available for the Monomodular enabled grid controllers.  It is a basic step sequencer with lots of bells and whistles.
+This mod is actually built for CNTRL:R, but in short order will also become available for the Mod enabled grid controllers.  It is a basic step sequencer with lots of bells and whistles.
 === [[modlink]] ===
@@ Line 16: / Line 16: @@
 [[File:Modlink_pic.png]]
-This Mod allows connection to anything that is built for a monome.  It formats data back and forth between Monomodular and monome-speak.  Consider it as a pure monome wrapper.  As of version b993, both serialosc and monomeserial protocols are supported.
+This mod allows connection to anything that is built for a monome.  It formats data back and forth between Mod and monome-speak.  Consider it as a pure monome wrapper.  As of version b993, both serialosc and monomeserial protocols are supported.
 === [[plinko]] ===
@@ Line 22: / Line 22: @@
 [[File:Plinko_pic.png]]
-A generative Mod designed to be programmed and manipulated in a Live situation.  Each cell on the grid becomes a probability generator, and particles move through the grid with the chance of striking these cells based either on randomness or predetermined paths.
+A generative mod designed to be programmed and manipulated in a Live situation.  Each cell on the grid becomes a probability generator, and particles move through the grid with the chance of striking these cells based either on randomness or predetermined paths.
 === [[endcoders]] ===
@@ Line 52: / Line 52: @@
 A simple triggering device that allows assignment of the grids keys to different notes and MIDI/Nome channels.
 === [[loopmaster]] ===
@@ Line 63: / Line 57: @@
 [[File:Loopmaster.jpg]]
-A Mod capable of controlling four instances of the tape-based looper, MaxLooper.  It allows recording controls and manipulation of those loops with the Mod grid.
+A mod capable of controlling four instances of the tape-based looper, MaxLooper.  It allows recording controls and manipulation of those loops with the Mod grid.
 === [[tr256|TR256]] ===
@@ Line 112: / Line 106: @@
 Tehn's xor.  A very quick port that is fairly self explanatory if you check out his docs.  Lots of fun!
 === [[help|monomods_help]] ===
@@ Line 123: / Line 111: @@
 [[File:Mod_help_pic.png]]
-This is where you start if you want to build your own patches, or just to see how the Monomodular framework is built on the Max side of things.
+This is where you start if you want to build your own patches, or just to see how the Mod framework is built on the Max side of things.
-A very useful patch for routing things in Live, since they didn't give us the capability to direct things with reasonable and predicable latency within m4l.  If you have a Mac, you should probably use IAC, but that being said, I run on OSX and I still use Nome a bit here and there.
+== Other Patches contained in the Mod suite ==
 === [[MaxLooper]] ===

@@ Line 1: / Line 1: @@
-A 'Mod' is just a convenient name for m4l patches designed to be used with Monomodular.  They all share at least one thing:  they contain a javascript object that communicates directly with the Monomodular Python script, which in turn communicates with Monomodular embedded _Framework control surface scripts.  An explanation of how this works, and examples of ways to use certain parts of the javascript, are contained in the [[help|Monomods_help]] patch that is installed in the folder with the rest of the Mods.
+A 'mod' is just a convenient name for m4l patches designed to be used with Mod.  They all share at least one thing:  they contain a javascript object that communicates directly with the Monomodular Python script, which in turn communicates with Mod embedded _Framework control surface scripts.  An explanation of how this works, and examples of ways to use certain parts of the javascript, are contained in the [[help|Monomods_help]] patch that is installed in the folder with the rest of the Mods.
-Some of the Mods are creations of amounra, while others are ports of Monome patches (mostly Stretta's).  Each one will function in an independant way, but they all have several things in common with one another.  To learn about the common ground that all plugins share, you should take a look at the [[How Monomodular Works]] page.  The specifics of each Mod, however, are covered on the following pages that can reached by clicking on the header of each of the following summaries:
+Some of the mods are creations of amounra, while others are ports of Monome patches (mostly Stretta's).  Each one will function in an independant way, but they all have several things in common with one another.  To learn about the common ground that all plugins share, you should take a look at the [[How Monomodular Works]] page.  The specifics of each mod, however, are covered on the following pages that can reached by clicking on the header of each of the following summaries:
-== Real Mods ==
+== Real mods ==
 ===[[hex]]===

← Older revision		Revision as of 03:32, 24 March 2012
Line 141:		Line 141:

	=== [[How_to_use_the_iOs_scripts\| AumPad and Aum256]] ===		=== [[How_to_use_the_iOs_scripts\| AumPad and Aum256]] ===
		+
		+	[[File:Ipad plugs.png]]
		+

	These patches serve to link together the Python scripts and the iPad via OSC. They are necessary to provide a UDP connection to the AumPad/256 and LemuarPad/256 scripts, as well as translate some things that are sent back and forth.		These patches serve to link together the Python scripts and the iPad via OSC. They are necessary to provide a UDP connection to the AumPad/256 and LemuarPad/256 scripts, as well as translate some things that are sent back and forth.

@@ Line 140: / Line 140: @@
 The current implementation of LCD requires only one patch, and autoswitches between all supported and installed devices based on which one is currently being operated.  In addition, it supports output to the Lemur AumPad and Aum256 templates.
-=== [[iOs| AumPad and Aum256]] ===
+=== [[How_to_use_the_iOs_scripts| AumPad and Aum256]] ===
 These patches serve to link together the Python scripts and the iPad via OSC.  They are necessary to provide a UDP connection to the AumPad/256 and LemuarPad/256 scripts, as well as translate some things that are sent back and forth.