Modlink - Revision history

Amounra: /* Overview */

2016-11-16T02:08:20Z

‎Overview

2016-11-16T02:07:44Z

‎Overview

2013-11-19T09:03:29Z

‎Overview

2013-11-19T09:03:14Z

‎Overview

2013-11-19T09:02:42Z

‎Overview

2013-11-19T09:01:34Z

‎Overview

2012-07-19T19:28:32Z

add category

2012-03-24T10:54:28Z

‎Overview

2012-03-24T10:54:08Z

‎Overview

2012-03-24T10:52:51Z

‎Overview

@@ Line 23: / Line 23: @@
 ''details: ''  [http://monome.org/docs/app:serialosc monome serialosc]
-"The mod version of the serialosc object is contained in m4m7/javascript/serialosc.  You'll need to place this in the Max 7 application bundle in order for communication between modlink and your monome Max patch.  In some instances (e.g. a frozen m4l amxd) you may need to replace serialosc inside the frozen patch."
+''The mod version of the serialosc object is contained in m4m7/javascript/serialosc.  You'll need to place this in the Max 7 application bundle in order for communication between modlink and your monome Max patch.  In some instances (e.g. a frozen m4l amxd) you may need to replace serialosc inside the frozen patch.''
 ----------

← Older revision		Revision as of 02:07, 16 November 2016
Line 22:		Line 22:

	''details: '' [http://monome.org/docs/app:serialosc monome serialosc]		''details: '' [http://monome.org/docs/app:serialosc monome serialosc]
		+
		+	"The mod version of the serialosc object is contained in m4m7/javascript/serialosc. You'll need to place this in the Max 7 application bundle in order for communication between modlink and your monome Max patch. In some instances (e.g. a frozen m4l amxd) you may need to replace serialosc inside the frozen patch."
		+
	----------		----------

@@ Line 21: / Line 21: @@
 ''It is necessary to install the zeroconf version of the monomeserial MaxMSP object in order to use modLink with most current published applications.''
-''details: ''  [http://monome.org/docs/app:serialosc "monome serialosc page"]
+''details: ''  [http://monome.org/docs/app:serialosc monome serialosc]
 ----------

@@ Line 21: / Line 21: @@
 ''It is necessary to install the zeroconf version of the monomeserial MaxMSP object in order to use modLink with most current published applications.''
-''details: ''  [http://monome.org/docs/app:serialosc]
+''details: ''  [http://monome.org/docs/app:serialosc "monome serialosc page"]
 ----------

← Older revision		Revision as of 09:02, 19 November 2013
Line 21:		Line 21:
	''It is necessary to install the zeroconf version of the monomeserial MaxMSP object in order to use modLink with most current published applications.''		''It is necessary to install the zeroconf version of the monomeserial MaxMSP object in order to use modLink with most current published applications.''

		+	''details: '' [http://monome.org/docs/app:serialosc]
	----------		----------

← Older revision		Revision as of 09:01, 19 November 2013
Line 18:		Line 18:

	''Currently, most monomeserial and serialosc messages are supported. However, luminosity and cable messages will be ignored.''		''Currently, most monomeserial and serialosc messages are supported. However, luminosity and cable messages will be ignored.''
		+
		+	''It is necessary to install the zeroconf version of the monomeserial MaxMSP object in order to use modLink with most current published applications.''

	----------		----------

← Older revision		Revision as of 19:28, 19 July 2012
Line 38:		Line 38:

	Also, if you are using multiple versions of the Monolink plugin, make sure that each one has its own UDP port settings, otherwise you will get some strange interactions between each instance (e.g. feedback from one on the others grid, etc.).		Also, if you are using multiple versions of the Monolink plugin, make sure that each one has its own UDP port settings, otherwise you will get some strange interactions between each instance (e.g. feedback from one on the others grid, etc.).
		+
		+	[[Category:Mods]]

@@ Line 17: / Line 17: @@
 Each individual instance of modlink will be initialized with a unique input port.  This should prevent interference from other instances, but also means you'll have to be mindful of which instance is which when auto-connecting.
+''Currently, most monomeserial and serialosc messages are supported.  However, luminosity and cable messages will be ignored.''
 ----------

← Older revision		Revision as of 10:54, 24 March 2012
Line 16:		Line 16:

	Each individual instance of modlink will be initialized with a unique input port. This should prevent interference from other instances, but also means you'll have to be mindful of which instance is which when auto-connecting.		Each individual instance of modlink will be initialized with a unique input port. This should prevent interference from other instances, but also means you'll have to be mindful of which instance is which when auto-connecting.
		+
		+
		+	Currently, most monomeserial and serialosc messages are supported. However, luminosity and cable messages will be ignored.

	----------		----------

@@ Line 5: / Line 5: @@
 =='''Overview'''==
-Modlink is a mod that allows connection to any standard monome patch.
+Modlink is a mod that allows connection to any standard monome patch as though it were a mod.
 [[File:Modlink_pic.png]]
 Here's a screenshot of 3 instances of modlink being used, 2 with SerialOSC connections (_xor and polygome), and one with MonomeSerial (molar).