ModWiki - User contributions [en]

Aum256

2020-06-13T06:06:37Z

Amounra: Created page with "This is a placeholder page for an upcoming MIDI Remote Script/iPad application combination for use with m4m8. The Aum256 script is included in the m4m8 repository here: [h..."

This is a placeholder page for an upcoming MIDI Remote Script/iPad application combination for use with m4m8.

The Aum256 script is included in the m4m8 repository here:

[https://github.com/aumhaa/m4m8 m4m8 Github]

You will need a current version of Live (10.1.14 currently) to use the script.

To install the script, you should copy the entire contents of m4m8/Python Scripts to ~/Music/Ableton/User Library/Remote Scripts folder. (This was recently changed from the old .app bundle contents location).

The script is capable of communicating with the included lemur template (m4m8/miscelaneous/aum256.jzml). Set the input/output ports of the Aum256 script in Live to the virtual ports assigned in the lemur app (port 0). If you're not using the lemur template, make sure the port assignments in Live's MIDI preferences for the Aum256 script are not assigned to anything.

The script is also capable of overriding three different Novation Launchpad scripts (Launchpad, Launchpad_MkII, and Launchpad Pro). When the Aum256 script is loaded, any instance of those stock scripts will load with an additional mod-mode attached to them. The behavior is slightly different for each Launchpad model:

*For the original Launchpad (also LP mini mki), User2 button puts the device into "mod" mode, and also acts as a shift button while mod mode is active.

*For the Launchpad MkII, User1 button puts the device into "mod" mode, and acts as a shift button while mod mode is active.

*For the Launchpad Pro MkI, mod mode is always engaged whenever the controller is in Note mode and a mod device is the selected device in Live. The shift button works as the mod-shift button while a mod is the active device.

This script is in active development.

Modlink

2016-11-16T02:08:20Z

Amounra: /* Overview */

== Video Tutorials ==

[http://www.youtube.com/watch?v=ylDHUlO_m1c MorphicField's Tutorial]

=='''Overview'''==

Modlink is a mod that allows connection to any standard monome patch as though it were a mod.

[[File:Modlink_pic.png]]

The top selection menu allows changing the communication protocol used to connect to the monome patch.

The title-bar also contains the unique instance number of the modlink. This number will also be present in any Bonjour listing available in a serialosc monome patch, so make sure when enabling a connection from serialosc that you choose the right modlink instance.

The prefix, input, and output port textboxes can be changed manually, or via serialosc. New settings initiated from serialosc will automatically be entered in the user interface.

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.''

''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]

''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.''

----------

Here's a screenshot of 3 instances of modlink being used, 2 with SerialOSC connections (_xor and polygome), and one with MonomeSerial (molar).

[[File:Modlink_example.png]]

== Examples ==

Here's an example using the older Monolink plugin from b992. This setup is kind of redundant now, since LCC has been ported over to a mod.

Monolink using the BlockMod control surface and Live Clip Chopper:

These are the basic settings for getting the [http://www.maxforlive.com/library/device.php?id=230 Live Clip Chopper] to work with Monolink.

[[File:clipchopwin.jpg]]

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]]

Modlink

2016-11-16T02:07:44Z

Amounra: /* Overview */

== Video Tutorials ==

[http://www.youtube.com/watch?v=ylDHUlO_m1c MorphicField's Tutorial]

=='''Overview'''==

Modlink is a mod that allows connection to any standard monome patch as though it were a mod.

[[File:Modlink_pic.png]]

The top selection menu allows changing the communication protocol used to connect to the monome patch.

The title-bar also contains the unique instance number of the modlink. This number will also be present in any Bonjour listing available in a serialosc monome patch, so make sure when enabling a connection from serialosc that you choose the right modlink instance.

The prefix, input, and output port textboxes can be changed manually, or via serialosc. New settings initiated from serialosc will automatically be entered in the user interface.

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.''

''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]

"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."

----------

Here's a screenshot of 3 instances of modlink being used, 2 with SerialOSC connections (_xor and polygome), and one with MonomeSerial (molar).

[[File:Modlink_example.png]]

== Examples ==

Here's an example using the older Monolink plugin from b992. This setup is kind of redundant now, since LCC has been ported over to a mod.

Monolink using the BlockMod control surface and Live Clip Chopper:

These are the basic settings for getting the [http://www.maxforlive.com/library/device.php?id=230 Live Clip Chopper] to work with Monolink.

[[File:clipchopwin.jpg]]

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]]

How Mod Works

2015-04-06T05:08:58Z

Amounra:

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 the main features of Mod are encapsulated below.

== mod Selection ==

Mod controller's automatically detect the currently selected device in Live's GUI. If the device is a mod and the control surface is in the appropriate mode, it will hand over its controls to the mod.

== The Grid ==

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.

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.

Mods that emulate monome256 workspaces use what is called "Legacy Mode", and provide some basic controls that are fairly universal between all the "Legacy Mode" mods. Some of the controls (such as modNav, modChannel, and some common modKeys) will be available in all "Legacy Mode" mods.

If you are not familiar with how a monome works, you might want to check this out:

http://en.wikipedia.org/wiki/Monome

and this:

http://monome.org/

== The modShift Button ==

The modShift button generally does the following:

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).

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]].

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.

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 modAlt Button ==

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).

== 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).

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.

[[File:Grid timing.png]]

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 ==

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.

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.

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.

== Supported Controllers ==

For more detailed descriptions of controller-specific functionality, please refer to the links below:

*[[How to use the AumPC scripts|Details for the APC]]

*[[How to use the BlockMod script|Details for the Block]]

*[[How to use the Codec script|Details for the Code]]

*[[How to use the iOs scripts|Details for the iPad]]

*[[How to use the LaunchMod script|Details for the Launchpad]]

*[[How to use the Ohm64 script|Details for the Ohm64 and Ohm64 RGB]]

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

Main Page

2015-04-05T21:34:31Z

Amounra: /* Supported controllers */

== Mod (formerly Monomodular) ==
Mod is a collection of software for use with Ableton Live 9 that provides its supported control surfaces with additional functionality to their stock implementations. Some of these augmentations are useful directly in Live's native environment, while other enhancements are modular and accessible through the use of add-on Max for Live [[mods]].

Mod began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal, and borrows heavily from the [http://www.monome.org monome] paradigm. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256, so familiarity with its concepts are useful for

The MIDI Remote Scripts distributed with the Mod installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Mod" server (implemented within each control script), which in turn manages and communicates with different [[Mods]] via m4l.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing mods are for MIDI generation and generative processes, but the Mod development framework allows developers to leverage the full power of Live + M4L + Max/MSP.

A recent decision was made to change the name of the (original) Monomodular project to '''Mod''', mostly to distinguish the older versions of Monomodular that worked with Live8 from the current version (but also because its shorter and easier to say; brevity is next to godliness).

== Installation ==

To use Mod, you'll need to download the github repository and place it in Max's packages folder, as well as copy some of its contained files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Mod Works ==

Monomodular is roughly based on a server/client principle, with the Mod framework acting as an intermediary between the various mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Mod-enabled control scripts on the [[How Mod Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using Lemur App]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Mod ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

Main Page

2015-04-05T21:33:28Z

Amounra: /* Mod (formerly Monomodular) */

== Mod (formerly Monomodular) ==
Mod is a collection of software for use with Ableton Live 9 that provides its supported control surfaces with additional functionality to their stock implementations. Some of these augmentations are useful directly in Live's native environment, while other enhancements are modular and accessible through the use of add-on Max for Live [[mods]].

Mod began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal, and borrows heavily from the [http://www.monome.org monome] paradigm. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256, so familiarity with its concepts are useful for

The MIDI Remote Scripts distributed with the Mod installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Mod" server (implemented within each control script), which in turn manages and communicates with different [[Mods]] via m4l.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing mods are for MIDI generation and generative processes, but the Mod development framework allows developers to leverage the full power of Live + M4L + Max/MSP.

A recent decision was made to change the name of the (original) Monomodular project to '''Mod''', mostly to distinguish the older versions of Monomodular that worked with Live8 from the current version (but also because its shorter and easier to say; brevity is next to godliness).

== Installation ==

To use Mod, you'll need to download the github repository and place it in Max's packages folder, as well as copy some of its contained files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Mod Works ==

Monomodular is roughly based on a server/client principle, with the Mod framework acting as an intermediary between the various mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Mod-enabled control scripts on the [[How Mod Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Mod ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

Mods

2015-03-31T20:58:57Z

Amounra:

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):

== Real mods ==

===[[hex]]===

[[File:Hex pic a.png]]

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]] ===

[[File:Modlink_pic.png]]

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]] ===

[[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.

=== [[endcoders]] ===

[[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]] ===

[[File:Life_pic.png]]

A rhythmic sequencer based on a jitter implementation of Conway's 'Game of Life' rules.

=== [[aumboids]] ===

[[File:Aumboids_pic.png]]

Experimentation with flocking behaviour in javascript. Judges distance between agents and sends out as controller data, while triggering notes based upon arbitrary relationships between individual agents and their leader.

=== [[monotes]] ===

[[File:Monotes_pic.png]]

A simple triggering device that allows assignment of the grids keys to different notes and MIDI/Nome channels.

=== [[tr256|TR256]] ===

[[File:tr256_pic.png]]

16 step rhythm sequencer. Capable of holding 16 patterns, recording real-time MIDI input, and editing patterns on the fly. Thank you, Stretta.

=== [[pressCafe]] ===

[[File:Presscafe_pic.png]]

16 step rhythm sequencer. Just, well, 'rad'. Thank you, Stretta.

=== [[polygome]] ===

[[File:Polygome_pic.png]]

Um....polyphonic rhythmic whatchamadoohicky that sounds really cool and is way fun to play. It does everything. Except my dishes. '''REALLY, thanks Stretta.'''

=== [[tintinnabulome|tintinabulome]] ===

[[File:Tintin_pic.png]]

Polyrhythmic mother ship. A bunch of guys came up with this one....Stretta was involved.

=== [[boiingg]] ===

[[File:Boinngg_pic.png]]

Ok, this is just good clean fun. Nodes bounce up and down depending upon how high you drop them from. When they hit the bottom, it makes a sound.

=== [[grainstorm]] ===

[[File:Grainstorm_pic.png]]

More Stretta, this one a new one built for the Arc. I've ported it to work with the Code/c all inclusive, or you can use any grid for manipulation. This one is still very young.

=== [[xor]] ===

[[File:xor_pic.png]]

Tehn's xor. A very quick port that is fairly self explanatory if you check out his docs. Lots of fun!

=== [[help|monomods_help]] ===

[[File:Mod_help_pic.png]]

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.

== Other Patches contained in the Mod suite ==

=== [[MaxLooper]] ===

[[File:Maxlooperrack.jpg‎]]

A tape-based looper. It provides visual output to the LCD patch, so that you can display loop data HUD style on your computer, or in the Lemur AumPad/256 LCD screen. It's of little use to anyone but its writer currently, since it's built around a custom pedal that connects to the expansion port of an OhmRGB and is, well, still a work in progress besides. That said, it hasn't crashed in over 2 months, so it is at least stable at this point if still not quite 'in-time, all-the-time'.

=== [[LCD]] ===

[[File:lcd_pic.png]]

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.

=== [[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.

Mods

2015-03-31T20:49:53Z

Amounra:

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 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):

== Real mods ==

===[[hex]]===

[[File:Hex pic a.png]]

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]] ===

[[File:Modlink_pic.png]]

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]] ===

[[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.

=== [[endcoders]] ===

[[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]] ===

[[File:Life_pic.png]]

A rhythmic sequencer based on a jitter implementation of Conway's 'Game of Life' rules.

=== [[aumboids]] ===

[[File:Aumboids_pic.png]]

Experimentation with flocking behaviour in javascript. Judges distance between agents and sends out as controller data, while triggering notes based upon arbitrary relationships between individual agents and their leader.

=== [[monotes]] ===

[[File:Monotes_pic.png]]

A simple triggering device that allows assignment of the grids keys to different notes and MIDI/Nome channels.

=== [[tr256|TR256]] ===

[[File:tr256_pic.png]]

16 step rhythm sequencer. Capable of holding 16 patterns, recording real-time MIDI input, and editing patterns on the fly. Thank you, Stretta.

=== [[pressCafe]] ===

[[File:Presscafe_pic.png]]

16 step rhythm sequencer. Just, well, 'rad'. Thank you, Stretta.

=== [[polygome]] ===

[[File:Polygome_pic.png]]

Um....polyphonic rhythmic whatchamadoohicky that sounds really cool and is way fun to play. It does everything. Except my dishes. '''REALLY, thanks Stretta.'''

=== [[tintinnabulome|tintinabulome]] ===

[[File:Tintin_pic.png]]

Polyrhythmic mother ship. A bunch of guys came up with this one....Stretta was involved.

=== [[boiingg]] ===

[[File:Boinngg_pic.png]]

Ok, this is just good clean fun. Nodes bounce up and down depending upon how high you drop them from. When they hit the bottom, it makes a sound.

=== [[grainstorm]] ===

[[File:Grainstorm_pic.png]]

More Stretta, this one a new one built for the Arc. I've ported it to work with the Code/c all inclusive, or you can use any grid for manipulation. This one is still very young.

=== [[xor]] ===

[[File:xor_pic.png]]

Tehn's xor. A very quick port that is fairly self explanatory if you check out his docs. Lots of fun!

=== [[help|monomods_help]] ===

[[File:Mod_help_pic.png]]

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.

== Other Patches contained in the Mod suite ==

=== [[MaxLooper]] ===

[[File:Maxlooperrack.jpg‎]]

A tape-based looper. It provides visual output to the LCD patch, so that you can display loop data HUD style on your computer, or in the Lemur AumPad/256 LCD screen. It's of little use to anyone but its writer currently, since it's built around a custom pedal that connects to the expansion port of an OhmRGB and is, well, still a work in progress besides. That said, it hasn't crashed in over 2 months, so it is at least stable at this point if still not quite 'in-time, all-the-time'.

=== [[LCD]] ===

[[File:lcd_pic.png]]

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.

=== [[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.

Main Page

2015-03-31T20:44:16Z

Amounra: /* Why doesn't anything work!? */

== Mod (formerly Monomodular) ==
Mod is a collection of software for use with Ableton Live 9 that provides its supported control surfaces with additional functionality to their stock implementations. Some of these augmentations are useful directly in Live's native environment, while other enhancements are modular and accessible through the use of add-on Max for Live [[mods]].

Mod began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal.

Mod borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Mod installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Mod" server (implemented within each control script), which in turn manages and communicates with different [[Mods]] via m4l.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing mods are for MIDI generation and generative processes, but the Mod development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

A recent decision was made to change the name of the (original) Monomodular project to '''Mod''', mostly to distinguish older versions of Monomodular that worked with Live8 from the current version (but also because its shorter and easier to say; brevity is next to godliness).

== Installation ==

To use Mod, you'll need to download the github repository and place it in Max's packages folder, as well as copy some of its contained files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Mod Works ==

Monomodular is roughly based on a server/client principle, with the Mod framework acting as an intermediary between the various mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Mod-enabled control scripts on the [[How Mod Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Mod ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

Main Page

2015-03-31T20:42:38Z

Amounra: /* How Mod Works */

== Mod (formerly Monomodular) ==
Mod is a collection of software for use with Ableton Live 9 that provides its supported control surfaces with additional functionality to their stock implementations. Some of these augmentations are useful directly in Live's native environment, while other enhancements are modular and accessible through the use of add-on Max for Live [[mods]].

Mod began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal.

Mod borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Mod installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Mod" server (implemented within each control script), which in turn manages and communicates with different [[Mods]] via m4l.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing mods are for MIDI generation and generative processes, but the Mod development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

A recent decision was made to change the name of the (original) Monomodular project to '''Mod''', mostly to distinguish older versions of Monomodular that worked with Live8 from the current version (but also because its shorter and easier to say; brevity is next to godliness).

== Installation ==

To use Mod, you'll need to download the github repository and place it in Max's packages folder, as well as copy some of its contained files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Mod Works ==

Monomodular is roughly based on a server/client principle, with the Mod framework acting as an intermediary between the various mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Mod-enabled control scripts on the [[How Mod Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Mod ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

I've tried to make things as simple as possible, but hey: things can go wrong. Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

Main Page

2015-03-31T20:41:14Z

Amounra: /* Installation */

== Mod (formerly Monomodular) ==
Mod is a collection of software for use with Ableton Live 9 that provides its supported control surfaces with additional functionality to their stock implementations. Some of these augmentations are useful directly in Live's native environment, while other enhancements are modular and accessible through the use of add-on Max for Live [[mods]].

Mod began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal.

Mod borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Mod installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Mod" server (implemented within each control script), which in turn manages and communicates with different [[Mods]] via m4l.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing mods are for MIDI generation and generative processes, but the Mod development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

A recent decision was made to change the name of the (original) Monomodular project to '''Mod''', mostly to distinguish older versions of Monomodular that worked with Live8 from the current version (but also because its shorter and easier to say; brevity is next to godliness).

== Installation ==

To use Mod, you'll need to download the github repository and place it in Max's packages folder, as well as copy some of its contained files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Mod Works ==

Monomodular is roughly based on a server/client principle, with Monomodular acting as an intermediary between the various Mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Monomodular-enabled control scripts on the [[How Monomodular Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Mod ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

I've tried to make things as simple as possible, but hey: things can go wrong. Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

Main Page

2015-03-31T20:39:29Z

Amounra: /* Mod (formerly Monomodular) */

== Mod (formerly Monomodular) ==
Mod is a collection of software for use with Ableton Live 9 that provides its supported control surfaces with additional functionality to their stock implementations. Some of these augmentations are useful directly in Live's native environment, while other enhancements are modular and accessible through the use of add-on Max for Live [[mods]].

Mod began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal.

Mod borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Mod installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Mod" server (implemented within each control script), which in turn manages and communicates with different [[Mods]] via m4l.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing mods are for MIDI generation and generative processes, but the Mod development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

A recent decision was made to change the name of the (original) Monomodular project to '''Mod''', mostly to distinguish older versions of Monomodular that worked with Live8 from the current version (but also because its shorter and easier to say; brevity is next to godliness).

== Installation ==

To use Mod, you'll need to download the github repository and copy the files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Mod Works ==

Monomodular is roughly based on a server/client principle, with Monomodular acting as an intermediary between the various Mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Monomodular-enabled control scripts on the [[How Monomodular Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Mod ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

I've tried to make things as simple as possible, but hey: things can go wrong. Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

Main Page

2015-03-31T20:38:00Z

Amounra: /* Mod (formerly Monomodular) */

== Mod (formerly Monomodular) ==
Mod is a collection of software for use with Ableton Live 9 that provides supported control surfaces with augmented built-in functionality. Some of these augmentations are useful directly in Live's native environment, while other enhancements are modular and accessible through the use of add-on Max for Live [[mods]].

Mod began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal.

Mod borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Mod installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Mod" server (implemented within each control script), which in turn manages and communicates with different [[Mods]] via m4l.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing mods are for MIDI generation and generative processes, but the Mod development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

A recent decision was made to change the name of the Monomodular project to '''Mod''', mostly to distinguish older versions of Monomodular that worked with Live8 from the current version (but also because its shorter and easier to say; brevity is next to godliness).

== Installation ==

To use Mod, you'll need to download the github repository and copy the files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Mod Works ==

Monomodular is roughly based on a server/client principle, with Monomodular acting as an intermediary between the various Mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Monomodular-enabled control scripts on the [[How Monomodular Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Mod ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

I've tried to make things as simple as possible, but hey: things can go wrong. Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

Main Page

2015-03-31T20:17:01Z

Amounra: /* Mod (formerly Monomodular) */

== Mod (formerly Monomodular) ==
First a tiny bit of history: Mod began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal. So: Mod is a modular environment for using (possibly multiple) [[#Supported controllers|supported grid-style controllers]] (APC40, Launchpad, etc.) with (possibly multiple) Max for Live (M4L) plugins (a.k.a. [[Mods]]), as well as a framework for M4L plugin development.

Mod borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Mod installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Monomodular" server (a seperate script that must be chosen), which in turn manages and communicates with different [[Mods]] via m4l.

Mod is still under active development, and is being offered as a beta, but it '''is''' being used for both production '''and''' performance by its author and many others.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing mods are for MIDI generation and generative processes, but the Mod development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

I've recently decided to change the name of the Monomodular project to '''Mod''', mostly to distinguish older versions of Monomodular that worked with Live8 from the current version (but also because I'm tired of saying Monomodular all the time; brevity is next to godliness).

== Installation ==

To use Mod, you'll need to download the github repository and copy the files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Mod Works ==

Monomodular is roughly based on a server/client principle, with Monomodular acting as an intermediary between the various Mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Monomodular-enabled control scripts on the [[How Monomodular Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Mod ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

I've tried to make things as simple as possible, but hey: things can go wrong. Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

Main Page

2015-03-31T19:30:53Z

Amounra: /* Mod (formerly Monomodular) */

== Mod (formerly Monomodular) ==
First a tiny bit of history: Mod began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal. So: Mod is a modular environment for using (possibly multiple) [[#Supported controllers|supported grid-style controllers]] (APC40, Launchpad, etc.) with (possibly multiple) Max for Live (M4L) plugins (a.k.a. [[Mods]]), as well as a framework for M4L plugin development.

Mod borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Mod installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Monomodular" server (a seperate script that must be chosen), which in turn manages and communicates with different [[Mods]] via m4l.

Mod is still under active development, and is being offered as a beta, but it '''is''' being used for both production '''and''' performance by its author and many others.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing mods are for MIDI generation and generative processes, but the Mod development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

I've recently decided to change the name of the project to '''Mod''', mostly because I'm tired of saying Monomodular all the time, but also to distinguish older versions of Monomodular that worked with Live8 from the current version. Brevity is next to godliness.

== Installation ==

To use Mod, you'll need to download the github repository and copy the files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Mod Works ==

Monomodular is roughly based on a server/client principle, with Monomodular acting as an intermediary between the various Mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Monomodular-enabled control scripts on the [[How Monomodular Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Mod ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

I've tried to make things as simple as possible, but hey: things can go wrong. Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

MediaWiki:Sidebar

2015-03-31T18:56:18Z

Amounra:

MediaWiki:Sidebar

2015-03-31T18:54:36Z

Amounra:

Main Page

2015-03-31T18:47:36Z

Amounra: /* What Comes with Monomodular */

== Mod (formerly Monomodular) ==
First a tiny bit of history: Monomodular began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal. So: Monomodular is a modular environment for using (possibly multiple) [[#Supported controllers|supported grid-style controllers]] (APC40, Launchpad, etc.) with (possibly multiple) Max for Live (M4L) plugins (a.k.a. [[Mods]]), as well as a framework for M4L plugin development.

Monomodular borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Monomodular installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Monomodular" server (a seperate script that must be chosen), which in turn manages and communicates with different [[Mods]] via m4l. The Monomodular script is also capable of communicating directly with external Max patches via OSC without the need for m4l.

Monomodular is still under active development, and is being offered as a beta, but it '''is''' being used for both production '''and''' performance by its author and many others.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing Mods are for MIDI generation and generative processes, but the Monomodular development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

I've recently decided to change the name of the project to '''Mod''', mostly because I'm tired of saying Monomodular all the time, but also to distinguish versions of Monomodular that worked with Live8 from the current version. Brevity is next to godliness.

== Installation ==

To use Mod, you'll need to download the github repository and copy the files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Mod Works ==

Monomodular is roughly based on a server/client principle, with Monomodular acting as an intermediary between the various Mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Monomodular-enabled control scripts on the [[How Monomodular Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Mod ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

I've tried to make things as simple as possible, but hey: things can go wrong. Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

How Mod Works

2015-03-31T18:46:30Z

Amounra: /* Mod Timing */

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 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 ==

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.

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.

Mods that emulate monome256 workspaces use what is called "Legacy Mode", and provide some basic controls that are fairly universal between all the "Legacy Mode" mods. Some of the controls (such as modNav, modChannel, and some common modKeys) will be available in all "Legacy Mode" mods.

If you are not familiar with how a monome works, you might want to check this out:

http://en.wikipedia.org/wiki/Monome

and this:

http://monome.org/

== The modShift Button ==

The modShift button generally does the following:

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).

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]].

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.

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 modAlt Button ==

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).

== 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).

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.

[[File:Grid timing.png]]

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 ==

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.

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.

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.

== Supported Controllers ==

For more detailed descriptions of controller-specific functionality, please refer to the links below:

*[[How to use the AumPC scripts|Details for the APC]]

*[[How to use the BlockMod script|Details for the Block]]

*[[How to use the Codec script|Details for the Code]]

*[[How to use the iOs scripts|Details for the iPad]]

*[[How to use the LaunchMod script|Details for the Launchpad]]

*[[How to use the Ohm64 script|Details for the Ohm64 and Ohm64 RGB]]

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

How Mod Works

2015-03-31T18:30:23Z

Amounra: /* Mod Timing */

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 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 ==

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.

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.

Mods that emulate monome256 workspaces use what is called "Legacy Mode", and provide some basic controls that are fairly universal between all the "Legacy Mode" mods. Some of the controls (such as modNav, modChannel, and some common modKeys) will be available in all "Legacy Mode" mods.

If you are not familiar with how a monome works, you might want to check this out:

http://en.wikipedia.org/wiki/Monome

and this:

http://monome.org/

== The modShift Button ==

The modShift button generally does the following:

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).

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]].

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.

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 modAlt Button ==

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).

== 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).

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.

[[File:Grid timing.png]]

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 ==

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.

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.

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.

== Supported Controllers ==

For more detailed descriptions of controller-specific functionality, please refer to the links below:

*[[How to use the AumPC scripts|Details for the APC]]

*[[How to use the BlockMod script|Details for the Block]]

*[[How to use the Codec script|Details for the Code]]

*[[How to use the iOs scripts|Details for the iPad]]

*[[How to use the LaunchMod script|Details for the Launchpad]]

*[[How to use the Ohm64 script|Details for the Ohm64 and Ohm64 RGB]]

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

How Mod Works

2015-03-31T18:29:05Z

Amounra:

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 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 ==

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.

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.

Mods that emulate monome256 workspaces use what is called "Legacy Mode", and provide some basic controls that are fairly universal between all the "Legacy Mode" mods. Some of the controls (such as modNav, modChannel, and some common modKeys) will be available in all "Legacy Mode" mods.

If you are not familiar with how a monome works, you might want to check this out:

http://en.wikipedia.org/wiki/Monome

and this:

http://monome.org/

== The modShift Button ==

The modShift button generally does the following:

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).

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]].

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.

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 modAlt Button ==

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).

== 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).

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.

[[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.

== 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.

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.

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.

== Supported Controllers ==

For more detailed descriptions of controller-specific functionality, please refer to the links below:

*[[How to use the AumPC scripts|Details for the APC]]

*[[How to use the BlockMod script|Details for the Block]]

*[[How to use the Codec script|Details for the Code]]

*[[How to use the iOs scripts|Details for the iPad]]

*[[How to use the LaunchMod script|Details for the Launchpad]]

*[[How to use the Ohm64 script|Details for the Ohm64 and Ohm64 RGB]]

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

How Monomodular Works

2015-03-31T17:54:42Z

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

#REDIRECT [[How Mod Works]]

How Mod Works

2015-03-31T17:54:29Z

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

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.

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:

== The Grid ==

There is an 8x8 grid, which represents one quadrant of the Monome256 workspace in its normal mode.

In addition, it will display generic information about the status of Monomodular and its connected Mods when using the other controls below.

If you are not familiar with how a monome works, you might want to check this out:

http://en.wikipedia.org/wiki/Monome

and this:

http://monome.org/

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.....

== The Shift Button ==

There is a Shift button, which, when pressed, does the following:

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).

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.

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.

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.

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.

[[File:8x8_shift.png]]

== The Lock Button ==

There is a Lock button, which toggles whether the bottom row is 'shift-locked' to permanently be used in 'Key Mode'.

[[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.

The first four buttons have no built in functionality, but may trigger a behavior that is specific to the mod that is currently selected.

The last four buttons always perform the following functions:

5: 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.

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 "alt" is depressed.

7. Toggle mod Power. This will toggle the device on/off parameter of the currently selected mod Device in Live.

8. Select mod Device. On controllers that offer device control, this will select the mod's parameters as the currently controlled device for the dials on the controller.

[[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.

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.

[[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).

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.

[[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.

== 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.

However, it is possible to use '[[NomeOut]]' nodes to channelize data within Live. By placing a [[NomeOut]] patch elsewhere in the Live set, and setting a Mod's output destination to that Nome patch, you can select where a Mod'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.

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.

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.

== Supported Controllers ==

For more detailed descriptions of controller-specific functionality, please refer to the links below:

*[[How to use the AumPC scripts|Details for the APC]]

*[[How to use the BlockMod script|Details for the Block]]

*[[How to use the Codec script|Details for the Code]]

*[[How to use the iOs scripts|Details for the iPad]]

*[[How to use the LaunchMod script|Details for the Launchpad]]

*[[How to use the Ohm64 script|Details for the Ohm64 and Ohm64 RGB]]

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

Mods

2015-03-30T03:30:31Z

Amounra: /* Real 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:

== Real mods ==

===[[hex]]===

[[File:Hex pic a.png]]

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]] ===

[[File:Modlink_pic.png]]

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]] ===

[[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.

=== [[endcoders]] ===

[[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]] ===

[[File:Life_pic.png]]

A rhythmic sequencer based on a jitter implementation of Conway's 'Game of Life' rules.

=== [[aumboids]] ===

[[File:Aumboids_pic.png]]

Experimentation with flocking behaviour in javascript. Judges distance between agents and sends out as controller data, while triggering notes based upon arbitrary relationships between individual agents and their leader.

=== [[monotes]] ===

[[File:Monotes_pic.png]]

A simple triggering device that allows assignment of the grids keys to different notes and MIDI/Nome channels.

=== [[tr256|TR256]] ===

[[File:tr256_pic.png]]

16 step rhythm sequencer. Capable of holding 16 patterns, recording real-time MIDI input, and editing patterns on the fly. Thank you, Stretta.

=== [[pressCafe]] ===

[[File:Presscafe_pic.png]]

16 step rhythm sequencer. Just, well, 'rad'. Thank you, Stretta.

=== [[polygome]] ===

[[File:Polygome_pic.png]]

Um....polyphonic rhythmic whatchamadoohicky that sounds really cool and is way fun to play. It does everything. Except my dishes. '''REALLY, thanks Stretta.'''

=== [[tintinnabulome|tintinabulome]] ===

[[File:Tintin_pic.png]]

Polyrhythmic mother ship. A bunch of guys came up with this one....Stretta was involved.

=== [[boiingg]] ===

[[File:Boinngg_pic.png]]

Ok, this is just good clean fun. Nodes bounce up and down depending upon how high you drop them from. When they hit the bottom, it makes a sound.

=== [[grainstorm]] ===

[[File:Grainstorm_pic.png]]

More Stretta, this one a new one built for the Arc. I've ported it to work with the Code/c all inclusive, or you can use any grid for manipulation. This one is still very young.

=== [[xor]] ===

[[File:xor_pic.png]]

Tehn's xor. A very quick port that is fairly self explanatory if you check out his docs. Lots of fun!

=== [[help|monomods_help]] ===

[[File:Mod_help_pic.png]]

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.

== Other Patches contained in the Mod suite ==

=== [[MaxLooper]] ===

[[File:Maxlooperrack.jpg‎]]

A tape-based looper. It provides visual output to the LCD patch, so that you can display loop data HUD style on your computer, or in the Lemur AumPad/256 LCD screen. It's of little use to anyone but its writer currently, since it's built around a custom pedal that connects to the expansion port of an OhmRGB and is, well, still a work in progress besides. That said, it hasn't crashed in over 2 months, so it is at least stable at this point if still not quite 'in-time, all-the-time'.

=== [[LCD]] ===

[[File:lcd_pic.png]]

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.

=== [[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.

Mods

2015-03-30T03:29:12Z

Amounra:

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:

== Real mods ==

===[[hex]]===

[[File:Hex pic a.png]]

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]] ===

[[File:Modlink_pic.png]]

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]] ===

[[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.

=== [[endcoders]] ===

[[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.

=== [[binary]] ===

[[File:Binary_pick.png]]

A Livid Code based step sequencer which allows easy timing manipulation and polyphonic assignments. Works great as a timing engine for other Mods, as well.

=== [[life]] ===

[[File:Life_pic.png]]

A rhythmic sequencer based on a jitter implementation of Conway's 'Game of Life' rules.

=== [[aumboids]] ===

[[File:Aumboids_pic.png]]

Experimentation with flocking behaviour in javascript. Judges distance between agents and sends out as controller data, while triggering notes based upon arbitrary relationships between individual agents and their leader.

=== [[monotes]] ===

[[File:Monotes_pic.png]]

A simple triggering device that allows assignment of the grids keys to different notes and MIDI/Nome channels.

=== [[loopmaster]] ===

[[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.

=== [[tr256|TR256]] ===

[[File:tr256_pic.png]]

16 step rhythm sequencer. Capable of holding 16 patterns, recording real-time MIDI input, and editing patterns on the fly. Thank you, Stretta.

=== [[pressCafe]] ===

[[File:Presscafe_pic.png]]

16 step rhythm sequencer. Just, well, 'rad'. Thank you, Stretta.

=== [[polygome]] ===

[[File:Polygome_pic.png]]

Um....polyphonic rhythmic whatchamadoohicky that sounds really cool and is way fun to play. It does everything. Except my dishes. '''REALLY, thanks Stretta.'''

=== [[tintinnabulome|tintinabulome]] ===

[[File:Tintin_pic.png]]

Polyrhythmic mother ship. A bunch of guys came up with this one....Stretta was involved.

=== [[sment]] ===

[[File:Sment_pic.png]]

Um. Stretta.

=== [[boiingg]] ===

[[File:Boinngg_pic.png]]

Ok, this is just good clean fun. Nodes bounce up and down depending upon how high you drop them from. When they hit the bottom, it makes a sound.

=== [[grainstorm]] ===

[[File:Grainstorm_pic.png]]

More Stretta, this one a new one built for the Arc. I've ported it to work with the Code/c all inclusive, or you can use any grid for manipulation. This one is still very young.

=== [[xor]] ===

[[File:xor_pic.png]]

Tehn's xor. A very quick port that is fairly self explanatory if you check out his docs. Lots of fun!

=== [[help|monomods_help]] ===

[[File:Mod_help_pic.png]]

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.

== Other Patches contained in the Mod suite ==

=== [[MaxLooper]] ===

[[File:Maxlooperrack.jpg‎]]

A tape-based looper. It provides visual output to the LCD patch, so that you can display loop data HUD style on your computer, or in the Lemur AumPad/256 LCD screen. It's of little use to anyone but its writer currently, since it's built around a custom pedal that connects to the expansion port of an OhmRGB and is, well, still a work in progress besides. That said, it hasn't crashed in over 2 months, so it is at least stable at this point if still not quite 'in-time, all-the-time'.

=== [[LCD]] ===

[[File:lcd_pic.png]]

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.

=== [[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.

Mods

2015-03-30T03:11:13Z

Amounra:

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:

== Real mods ==

===[[hex]]===

[[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.

=== [[modlink]] ===

[[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.

=== [[plinko]] ===

[[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.

=== [[endcoders]] ===

[[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.

=== [[binary]] ===

[[File:Binary_pick.png]]

A Livid Code based step sequencer which allows easy timing manipulation and polyphonic assignments. Works great as a timing engine for other Mods, as well.

=== [[life]] ===

[[File:Life_pic.png]]

A rhythmic sequencer based on a jitter implementation of Conway's 'Game of Life' rules.

=== [[aumboids]] ===

[[File:Aumboids_pic.png]]

Experimentation with flocking behaviour in javascript. Judges distance between agents and sends out as controller data, while triggering notes based upon arbitrary relationships between individual agents and their leader.

=== [[monotes]] ===

[[File:Monotes_pic.png]]

A simple triggering device that allows assignment of the grids keys to different notes and MIDI/Nome channels.

=== [[swing16]] ===

[[File:Swing8_pic.png]]

Barely a Mod, this one just allows Device Controllers to lock to the swing parameter of all the instantiated Mods (if they have swing capability).

=== [[loopmaster]] ===

[[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.

=== [[tr256|TR256]] ===

[[File:tr256_pic.png]]

16 step rhythm sequencer. Capable of holding 16 patterns, recording real-time MIDI input, and editing patterns on the fly. Thank you, Stretta.

=== [[pressCafe]] ===

[[File:Presscafe_pic.png]]

16 step rhythm sequencer. Just, well, 'rad'. Thank you, Stretta.

=== [[polygome]] ===

[[File:Polygome_pic.png]]

Um....polyphonic rhythmic whatchamadoohicky that sounds really cool and is way fun to play. It does everything. Except my dishes. '''REALLY, thanks Stretta.'''

=== [[tintinnabulome|tintinabulome]] ===

[[File:Tintin_pic.png]]

Polyrhythmic mother ship. A bunch of guys came up with this one....Stretta was involved.

=== [[sment]] ===

[[File:Sment_pic.png]]

Um. Stretta.

=== [[boiingg]] ===

[[File:Boinngg_pic.png]]

Ok, this is just good clean fun. Nodes bounce up and down depending upon how high you drop them from. When they hit the bottom, it makes a sound.

=== [[grainstorm]] ===

[[File:Grainstorm_pic.png]]

More Stretta, this one a new one built for the Arc. I've ported it to work with the Code/c all inclusive, or you can use any grid for manipulation. This one is still very young.

=== [[xor]] ===

[[File:xor_pic.png]]

Tehn's xor. A very quick port that is fairly self explanatory if you check out his docs. Lots of fun!

=== [[clipchopper]] ===

[[File:clipchop_pic.png]]

A highly requested one....so I spent a few minutes (literally....it took about 5 minutes) to port this over to mod-land. Obviously, it can use a bit of work....but I'm pretty sure anything funky going on is NOT due to my meddling.

=== [[help|monomods_help]] ===

[[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.

== Other Patches contained in the Monomodular suite ==

=== [[NomeOut]] ===

[[File:Monolink pic.png]]

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.

=== [[MaxLooper]] ===

[[File:Maxlooperrack.jpg‎]]

A tape-based looper. It provides visual output to the LCD patch, so that you can display loop data HUD style on your computer, or in the Lemur AumPad/256 LCD screen. It's of little use to anyone but its writer currently, since it's built around a custom pedal that connects to the expansion port of an OhmRGB and is, well, still a work in progress besides. That said, it hasn't crashed in over 2 months, so it is at least stable at this point if still not quite 'in-time, all-the-time'.

=== [[LCD]] ===

[[File:lcd_pic.png]]

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.

=== [[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.

Main Page

2015-03-30T03:10:08Z

Amounra: /* How Monomodular Works */

== Mod (formerly Monomodular) ==
First a tiny bit of history: Monomodular began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal. So: Monomodular is a modular environment for using (possibly multiple) [[#Supported controllers|supported grid-style controllers]] (APC40, Launchpad, etc.) with (possibly multiple) Max for Live (M4L) plugins (a.k.a. [[Mods]]), as well as a framework for M4L plugin development.

Monomodular borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Monomodular installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Monomodular" server (a seperate script that must be chosen), which in turn manages and communicates with different [[Mods]] via m4l. The Monomodular script is also capable of communicating directly with external Max patches via OSC without the need for m4l.

Monomodular is still under active development, and is being offered as a beta, but it '''is''' being used for both production '''and''' performance by its author and many others.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing Mods are for MIDI generation and generative processes, but the Monomodular development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

I've recently decided to change the name of the project to '''Mod''', mostly because I'm tired of saying Monomodular all the time, but also to distinguish versions of Monomodular that worked with Live8 from the current version. Brevity is next to godliness.

== Installation ==

To use Mod, you'll need to download the github repository and copy the files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Mod Works ==

Monomodular is roughly based on a server/client principle, with Monomodular acting as an intermediary between the various Mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Monomodular-enabled control scripts on the [[How Monomodular Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Monomodular ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

I've tried to make things as simple as possible, but hey: things can go wrong. Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

Main Page

2015-03-30T01:11:50Z

Amounra: /* Mod (formerly Monomodular) */

== Mod (formerly Monomodular) ==
First a tiny bit of history: Monomodular began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal. So: Monomodular is a modular environment for using (possibly multiple) [[#Supported controllers|supported grid-style controllers]] (APC40, Launchpad, etc.) with (possibly multiple) Max for Live (M4L) plugins (a.k.a. [[Mods]]), as well as a framework for M4L plugin development.

Monomodular borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Monomodular installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Monomodular" server (a seperate script that must be chosen), which in turn manages and communicates with different [[Mods]] via m4l. The Monomodular script is also capable of communicating directly with external Max patches via OSC without the need for m4l.

Monomodular is still under active development, and is being offered as a beta, but it '''is''' being used for both production '''and''' performance by its author and many others.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing Mods are for MIDI generation and generative processes, but the Monomodular development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

I've recently decided to change the name of the project to '''Mod''', mostly because I'm tired of saying Monomodular all the time, but also to distinguish versions of Monomodular that worked with Live8 from the current version. Brevity is next to godliness.

== Installation ==

To use Mod, you'll need to download the github repository and copy the files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Monomodular Works ==

Monomodular is roughly based on a server/client principle, with Monomodular acting as an intermediary between the various Mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Monomodular-enabled control scripts on the [[How Monomodular Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Monomodular ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

I've tried to make things as simple as possible, but hey: things can go wrong. Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

Main Page

2015-03-30T01:11:00Z

Amounra: /* Mod (previously Monomodular) */

== Mod (formerly Monomodular) ==
First a tiny bit of history: Monomodular began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal. So: Monomodular is a modular environment for using (possibly multiple) [[#Supported controllers|supported grid-style controllers]] (APC40, Launchpad, etc.) with (possibly multiple) Max for Live (M4L) plugins (a.k.a. [[Mods]]), as well as a framework for M4L plugin development.

Monomodular borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Monomodular installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Monomodular" server (a seperate script that must be chosen), which in turn manages and communicates with different [[Mods]] via m4l. The Monomodular script is also capable of communicating directly with external Max patches via OSC without the need for m4l.

Monomodular is still under active development, and is being offered as a beta, but it '''is''' being used for both production '''and''' performance by its author and many others.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing Mods are for MIDI generation and generative processes, but the Monomodular development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

I've recently decided to change the name of the project to '''Mod''', simply because I'm tired of saying Monomodular all the time. Brevity is next to godliness.

== Installation ==

To use Mod, you'll need to download the github repository and copy the files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

== How Monomodular Works ==

Monomodular is roughly based on a server/client principle, with Monomodular acting as an intermediary between the various Mods and [[#Supported controllers|supported]] controllers.

You can read a description of the basic functionality of the Monomodular-enabled control scripts on the [[How Monomodular Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

*[[How to use the Cntrlr script|Livid's CNTRL:R]]

*[[How to use the Base script|Livid's Base]]

== What Comes with Monomodular ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

I've tried to make things as simple as possible, but hey: things can go wrong. Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

Main Page

2015-03-29T23:30:41Z

Amounra: /* How Monomodular Works */

Main Page

2015-03-29T23:29:16Z

Amounra: /* Installation */

Main Page

2015-03-29T23:28:39Z

Amounra: /* How? */

== Mod (previously Monomodular) ==
First a tiny bit of history: Monomodular began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal. So: Monomodular is a modular environment for using (possibly multiple) [[#Supported controllers|supported grid-style controllers]] (APC40, Launchpad, etc.) with (possibly multiple) Max for Live (M4L) plugins (a.k.a. [[Mods]]), as well as a framework for M4L plugin development.

Monomodular borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Monomodular installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Monomodular" server (a seperate script that must be chosen), which in turn manages and communicates with different [[Mods]] via m4l. The Monomodular script is also capable of communicating directly with external Max patches via OSC without the need for m4l.

Monomodular is still under active development, and is being offered as a beta, but it '''is''' being used for both production '''and''' performance by its author and many others.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing Mods are for MIDI generation and generative processes, but the Monomodular development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

I've recently decided to change the name of the project to '''Mod''', simply because I'm tired of saying Monomodular all the time. Brevity is next to godliness.

== Installation ==

==== How? ====

To use Mod, you'll need to download the github repository and copy the files into Live's application bundle (on OS X) or its folder structure (on Windows).

For the details about how where everything goes, please visit the [[Installation]] page.

==== What? ====

The Installer patch is a fairly simple M4L utility which reads information about your Live and Max installations and tries to determine where files should be put on your system. Because Monomodular is not an application in itself, but is instead a collection of scripts and Max patches, it needs to be installed using different methods than most traditional installers can provide. The installer patch gets some information from Ableton's log and the currently running instance of Live. This process is not perfect, however, and under certain circumstances you'll have to locate the correct installation paths manually. The installer will alert you if it is unable to locate something it needs.

If you have a persistent problem with installation, please contact the author with the specifics, and a copy of Ableton's '''[[log.txt]]''', so that the installer can be improved.

The installer installs three main categories of files:

* '''Mods'''
:M4L patches which "do stuff" in conjunction with a grid controller. The list is growing, but you can go to the [[Mods]] page to learn a little bit about what's currently available. You can also access an information page on this wiki from within the plugin itself by hitting the Help button.
* '''Framework Scripts'''
:These are the Python scripts which
::* Allow your grid controller to interact with Live and link to the main Monomodular script.
::* Set up the main Monomodular script, the "hub" which controls interactions among the grid controller, Live, and Mods.
* '''Other Stuff'''
:Miscellaneous files which need to be here or there in order for things to work correctly.

==== Where? ====

If you need to know where certain files are located, or would like to change some things with the installation, please refer to the [[Manual Installation]] page.

== How Monomodular Works ==

Monomodular is roughly based on a server/client principle, with Monomodular acting as an intermediary between the various Mods and [[#Supported controllers|supported]] controllers.

As of version b993, Monomodular allows native communication with patches/M4L devices specifically designed to work with monome hardware, without needing anything else, using SerialOSC.

As of version b994, Monomodular is fully compatible with Max6.

You can read a description of the basic functionality of the Monomodular-enabled control scripts on the [[How Monomodular Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

In addition, there is a custom tie-in script for Livid's CNTRL:R that the author uses:

*[[How to use the AumTroll script|Livid's CNTRL:R]]

== What Comes with Monomodular ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

I've tried to make things as simple as possible, but hey: things can go wrong. Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

Main Page

2015-03-29T23:26:04Z

Amounra: /* Monomodular */

== Mod (previously Monomodular) ==
First a tiny bit of history: Monomodular began as a multi-color [http://monome.org/devices monome] emulation experiment in 2008. It was designed with live music performance as its primary goal. So: Monomodular is a modular environment for using (possibly multiple) [[#Supported controllers|supported grid-style controllers]] (APC40, Launchpad, etc.) with (possibly multiple) Max for Live (M4L) plugins (a.k.a. [[Mods]]), as well as a framework for M4L plugin development.

Monomodular borrows heavily from the [http://www.monome.org monome] paradigm, and familiarity with its concepts are useful. Many of the [[Mods]] descriptions assume familiarity with the monome format, and most of the Ableton MIDI Remote Scripts that are the backbone of the Monomodular system emulate the functions of a monome256.

The MIDI Remote Scripts distributed with the Monomodular installation are complete in themselves, and require neither Max for Live nor any external patches to function correctly within Ableton's environment. They provide a backend for communicating with the "Monomodular" server (a seperate script that must be chosen), which in turn manages and communicates with different [[Mods]] via m4l. The Monomodular script is also capable of communicating directly with external Max patches via OSC without the need for m4l.

Monomodular is still under active development, and is being offered as a beta, but it '''is''' being used for both production '''and''' performance by its author and many others.

Most of the early mods were ports of popular Max patches or M4L devices designed for use with the monome, but now the release includes many of amounra's own creations (which are not tied to any specific controller). The majority of the existing Mods are for MIDI generation and generative processes, but the Monomodular development framework allows developers to leverage the full power of Live + M4L + Max/MSP. The sky's the limit! See [[Help|Building your own Mods]].

I've recently decided to change the name of the project to '''Mod''', simply because I'm tired of saying Monomodular all the time. Brevity is next to godliness.

== Installation ==

==== How? ====

Download the installer and use its "SVN" button to install the most recent version (recommended):

[http://www.aumhaa.com/Monomodular/Monomodular_Installer_OSX.amxd OSX Installer]

[http://www.aumhaa.com/Monomodular/Monomodular_Installer_Win.amxd Windows Installer]

If you are using Windows, you will need to install the command-line subversion tool, [http://www.sliksvn.com/en/download SlikSVN] (or something else which takes svn commands).

SVN installation through the installer has returned in b994, but you can also just download the complete [http://www.aumhaa.com/Monomodular/Monomodular_b994.zip Monomodular b994 Content] package (which contains installers for Win and OSX), unpack it somewhere convenient, then either double-click the appropriate .amxd for your platform, or drop same into an open Live set.

Be aware that there are some problems with the Windows installer. It's recommended (and usually necessary) on Win7 to select "Run as Administrator" when starting Live for a session with the installer.

If you run into trouble, the [[Installation]] page contains a few tips and gotchas, as well as a more detailed explanation of how the installer works, for the curious.

==== What? ====

The Installer patch is a fairly simple M4L utility which reads information about your Live and Max installations and tries to determine where files should be put on your system. Because Monomodular is not an application in itself, but is instead a collection of scripts and Max patches, it needs to be installed using different methods than most traditional installers can provide. The installer patch gets some information from Ableton's log and the currently running instance of Live. This process is not perfect, however, and under certain circumstances you'll have to locate the correct installation paths manually. The installer will alert you if it is unable to locate something it needs.

If you have a persistent problem with installation, please contact the author with the specifics, and a copy of Ableton's '''[[log.txt]]''', so that the installer can be improved.

The installer installs three main categories of files:

* '''Mods'''
:M4L patches which "do stuff" in conjunction with a grid controller. The list is growing, but you can go to the [[Mods]] page to learn a little bit about what's currently available. You can also access an information page on this wiki from within the plugin itself by hitting the Help button.
* '''Framework Scripts'''
:These are the Python scripts which
::* Allow your grid controller to interact with Live and link to the main Monomodular script.
::* Set up the main Monomodular script, the "hub" which controls interactions among the grid controller, Live, and Mods.
* '''Other Stuff'''
:Miscellaneous files which need to be here or there in order for things to work correctly.

==== Where? ====

If you need to know where certain files are located, or would like to change some things with the installation, please refer to the [[Manual Installation]] page.

== How Monomodular Works ==

Monomodular is roughly based on a server/client principle, with Monomodular acting as an intermediary between the various Mods and [[#Supported controllers|supported]] controllers.

As of version b993, Monomodular allows native communication with patches/M4L devices specifically designed to work with monome hardware, without needing anything else, using SerialOSC.

As of version b994, Monomodular is fully compatible with Max6.

You can read a description of the basic functionality of the Monomodular-enabled control scripts on the [[How Monomodular Works]] page.
Each supported controller has its own page with further instructions and tips for usage.

====== Supported controllers ======

*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]

*[[How to use the BlockMod script|Livid's Block]]

*[[How to use the Codec script|Livid's Code]]

*[[How to use the iOs scripts|Apple's iPad, using either TouchOSC or Lemur]]

*[[How to use the LaunchMod script|Novation's Launchpad]]

*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]

In addition, there is a custom tie-in script for Livid's CNTRL:R that the author uses:

*[[How to use the AumTroll script|Livid's CNTRL:R]]

== What Comes with Monomodular ==

The [[Mods|Mods page]] lists all current mods. It's an evolving work-in-progress instruction and commentary on each plugin, so it's a good idea to check back from time to time for new information.

== Why doesn't anything work!? ==

I've tried to make things as simple as possible, but hey: things can go wrong. Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.

==Links==
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]

[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]

[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

How to use the MonoWing script

2015-01-16T09:58:39Z

Amounra:

Modes:

The four (currently only 3) modes of the script can be accessed by pressing one of the side buttons. The modes are:

Looper Mode

Each of the bottom 4 rectangular buttons represent one of four loopers. A looper can be an instance of Live's built in looper, or Jove (from Monomodular). Preface the looper name with "@looper" and it's number.

Select the loop by using the four select buttons. The color of each button represents its corresponding looper's state:

Red: recording.
Cyan: overdubbing.
Blue: muted.
Green: playing.
Magenta: waiting to sync (for quantized features).
White: selected.

The round pads control loop functions for the selected loop, and the long slider controls feedback amount. The buttons are: Overdub, Record, Mute, Reverse, and Clear (on the tip of the wing).

Scene Launcher Mode

The select buttons select from banks 1 - 4. In each bank, there are 4 launch buttons. This allows launching up to 16 scenes. Preface a scene with "@launch" + the bank number + the slot number. (e.g. "@launch 1 1").

Device Mode

The select buttons select from devices 1 - 4 (designated by prefacing device name with "@fx:" + its number, e.g. "@fx:1"). Each device should be a rack. The pad buttons allow toggling of macros, while the long slider allows continuous control. By renaming the macro controls in the device to "@prm:" + its number, you can toggle its value between 0 and 127 by pressing the button. By renaming one of the macro controls to "@exp:" + its number, you can control its value with one of the sliders.

How to use the MonoWing script

2015-01-16T09:34:56Z

Amounra:

Modes:

The four (currently only 3) modes of the script can be accessed by pressing one of the side buttons. The modes are:

Looper Mode

Each of the bottom 4 rectangular buttons represent one of four loopers. A looper can be an instance of Live's built in looper, or Jove (from Monomodular). Preface the looper name with "@looper" and it's number.

Select the loop by using the four select buttons. The color of each button represents its corresponding looper's state:

Red: recording.
Cyan: overdubbing.
Blue: muted.
Green: playing.
Magenta: waiting to sync (for quantized features).
White: selected.

The round pads control loop functions for the selected loop, and the long slider controls feedback amount. The buttons are: Overdub, Record, Mute, Reverse, and Clear (on the tip of the wing).

Scene Launcher Mode

The select buttons select from banks 1 - 4. In each bank, there are 4 launch buttons. This allows launching up to 16 scenes. Preface a scene with "@launch" + the bank number + the slot number. (e.g. "@launch 1 1").

Device Mode

The select buttons select from devices 1 - 4 (designated by prefacing device name with "@fx" + its number, e.g. "@fx1"). Each device should be a rack. The pad buttons allow toggling of macros, while the long slider allows continuous control. By renaming the macro controls in the device to "@param" + its number, you can toggle its value between 0 and 127 by pressing the button. By renaming one of the macro controls to "@exp", you can control its value with the long slider.

How to use the MonoWing script

2015-01-16T09:33:58Z

Amounra: Created page with "Modes: Looper Mode Each of the bottom 4 rectangular buttons represent one of four loopers. A looper can be an instance of Live's built in looper, or Jove (from Monomodular)..."

Modes:

Looper Mode

Each of the bottom 4 rectangular buttons represent one of four loopers. A looper can be an instance of Live's built in looper, or Jove (from Monomodular). Preface the looper name with "@looper" and it's number.

Select the loop by using the four select buttons. The color of each button represents its corresponding looper's state:

Red: recording.
Cyan: overdubbing.
Blue: muted.
Green: playing.
Magenta: waiting to sync (for quantized features).
White: selected.

The round pads control loop functions for the selected loop, and the long slider controls feedback amount. The buttons are: Overdub, Record, Mute, Reverse, and Clear (on the tip of the wing).

Scene Launcher Mode

The select buttons select from banks 1 - 4. In each bank, there are 4 launch buttons. This allows launching up to 16 scenes. Preface a scene with "@launch" + the bank number + the slot number. (e.g. "@launch 1 1").

Device Mode

The select buttons select from devices 1 - 4 (designated by prefacing device name with "@fx" + its number, e.g. "@fx1"). Each device should be a rack. The pad buttons allow toggling of macros, while the long slider allows continuous control. By renaming the macro controls in the device to "@param" + its number, you can toggle its value between 0 and 127 by pressing the button. By renaming one of the macro controls to "@exp", you can control its value with the long slider.

To designate a rack to be used for one

Older Versions

2014-04-07T07:04:41Z

Amounra:

Here is a link to the pre-Live9 installers which are linked to archived SVN repos from before when I started working on b995/b996 for Live9.

[http://www.aumhaa.com/Monomodular/Monomodular_Installer_Windows.amxd Windows Installer]

[http://www.aumhaa.com/Monomodular/Monomodular_Installer_OSX.amxd OSX Installer]

Older Versions

2014-04-07T07:03:50Z

Amounra:

Here is a link to the pre-Live9 installers which are linked to archived SVN repos from before when I started working on b995/b996 for Live9.

[http://www.aumhaa.com/home/aumhaa/aumhaa.com/Monomodular/Monomodular_Installer_Windows.amxd Windows Installer]

[http://www.aumhaa.com/home/aumhaa/aumhaa.com/Monomodular/Monomodular_Installer_OSX.amxd OSX Installer]

Older Versions

2014-04-07T07:03:12Z

Amounra: Created page with "Here is a link to the pre-Live9 installers which are linked to archived SVN repos from before when I started working on b995/b996 for Live9. [http://www.aumhaa.com/home/aumha..."

Here is a link to the pre-Live9 installers which are linked to archived SVN repos from before when I started working on b995/b996 for Live9.

[http://www.aumhaa.com/home/aumhaa/aumhaa.com/Monomodular/Monomodular_Installer_Windows.amxd|Windows Installer]

http://www.aumhaa.com/home/aumhaa/aumhaa.com/Monomodular/Monomodular_Installer_OSX.amxd|OSX Installer]

Manual Installation

2014-01-06T00:22:44Z

Amounra:

Back in the old days, we had to put all this stuff where it went on our own.

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.

== Mods ==

All of the m4l patches that accompany the static build of Monomodular (i.e. the frozen version) should be placed in Live'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's browser, then drop it there. All the patches inside it should be copied into your library.

If you are using Live 8, the last stable version of mods are in the b994 folder. However, most of the early material in b995 will also work with Live8, but I ceased development for Live8 during this version so I haven't been checking compatibility.

If you are using Live9, you will want to use the mods in the b995 folder.

For the adventurous, the b996 folder has newly created mods for the upcoming release. To date, however, these mods only work with AumPush and Livid Base scripts.

The default paths for Live's Library are:

MacOS = ~/Library/Preferences/Live 8.x.x/Library/Presets/MIDI Effects/Max MIDI Effect

<= Windows XP =\Documents and Settings\USER\Documents\Ableton\Library\Presets\MIDI Effects\Max MIDI Effect

Windows 7+ = \users\username\documents\ableton\Library\Presets\MIDI Effects\Max MIDI Effect

== Python Scripts ==

All of the control surface scripts should be placed inside the "MIDI Remote Scripts" folder.

This folder resides inside the Live.app bundle on OSX (ctrl-click the Live app, then select 'Show Package Contents' in order to navigate to the right place. Once inside, the path is: /Contents/App-Resources/MIDI Remote Scripts/).

On Windows, this process is a little simpler. The default file paths for the Remote Scripts folder are detailed on the [[Installation]] page.

Make sure NOT to move the entire 'Python Scripts' 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.

You will only need the contents of one of these folders, depending on whether you are using Live8 or Live9. Make sure only to copy the contents of the correct folder for your version of Live to the MIDI Remote Scripts folder.

MacOS: Live.app = ~/Applications/Live 8.x.x/Live.app/Resources\MIDI Remote Scripts

Windows: Live Folder =\Program Files\Ableton\Live 8.2.2\Resources\MIDI Remote Scripts

== Java ==

There are a couple of files required by Boinng, Plinko, and Aumboids that must be place inside the Cycling '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 '74/java/classes/, and there place the files from the Java folder from the Monomodular Installation Package.

MacOS = ~/Applications/Max 5/java/classes

Windows = \Program Files\Cycling '74\Max 5.x\java\classes

== aumhaa_blocks ==

These are support files needed by the patches. Depending on how you received the package (direct download or SVN), it's contents will be different.

When downloading via SVN, this folder will contain additional resources for opening the unfrozen patch versions that are included in Live's library installation.

These files can be placed anywhere as long as you add the location to your search path in Max's file preferences. However, its easiest to just place them inside the "patches" folder in your Max installation, since it is already part of the search path.

It's also VERY important that only one copy of this folder be present in your search path, otherwise you may have conflicting versions present when you update Monomodular with future patches/releases.

If are getting errors in Max's status window, or there is no "wood block" display on the top right of your patches, these files aren't in the right place. There are graphics files inside the aumhaa_blocks folder that I'm unable to compile with the patches, and this behavior indicates that Max can't find them in their current location. Make sure they are inside Max's search path.

MacOS = ~/Applications/Max 5/patches

Windows = \Program Files\Cycling '74\Max 5.x\patches

== Monomodular ==

This folder contains several files useful to those using an iPad with TouchOSC or Lemur. If you don't have one, then you won't need them. Otherwise, you'll need to put them on your iOS device in order to use the AumPad or Aum256 Python scripts.

Installation

2014-01-06T00:15:18Z

Amounra:

NOTICE: Currently, use of the installer for current Live versions (9>) isn't really supported. Although I have updated the installer for MacOS sometime in the last year, I haven't been maintaining it. Consequently, I'd recommend manual installation for any new users. You can find information about where each file goes here:

[[Manual Installation|Manual Installation]]

----

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).

You may have navigated here from the installer itself, and you're wondering what its all about.

To install all the Monomodular software, just follow the instructions printed in the console window of the Installer patch.

'''MAKE SURE LIVE'S AUDIO ENGINE IS TURNED ON BEFORE LOADING THE INSTALLER'''

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'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:

'''IF YOU ARE USING WINDOWS 7, SEE BELOW FOR SPECIAL INSTRUCTIONS.'''

==Installation Package (all platforms):==

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.

If you are installing from SVN (not available with b993 yet), you must press the "Subversion" 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).

These are the default locations that the installer is looking for. Under most circumstances, this is where things will be:

Here's a video from astarte describing the installation. He's using a Launchpad with Monomodular in the video:

[http://www.youtube.com/watch?v=70sBh41X3qw&feature=plcp Astarte's video]

----

====MacOS====

Live.app             = ~/Applications/Live 8.x.x/Live.app

or                 ~/Applications/Ableton Live 8.app (version 8.3.x and greater)

MaxMSP Folder   = ~/Applications/Max 5

Live Library       = ~/Library/Preferences/Live 8.x.x/Library

----

====Windows (pre win7)====

Live Folder = \Program Files\Ableton\Live 8.x.x

MaxMSP Folder = \Program Files\Cycling '74\Max 5.x

Live Library =\Documents and Settings\USER\Documents\Ableton

----

====Windows 7====

Live Folder = \Program Files\Ableton\Live 8.x.x

MaxMSP Folder = \Program Files\Cycling '74\Max 5.x

Live Library = \users\username\documents\ableton\Library

(see further Win7 specific instructions below)
----

Once the installer has verified that the installation paths that you've chosen to be valid places to put its files, you can press the "Install" 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.

The installer will copy its payload to new folders if the correct folders don'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 'broken' 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.

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).

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.

Once the installer is finished, it will indicate that you need to restart Live. So....restart Live already.

====WINDOWS 7 INSTALLATION====

The installer should be able to autodetect the file locations in the b993 installer, but it probably won't be able to copy them unless you run Live with Administrator priveleges. You can do this by right-clicking Live's application and choosing "Run as Administator".

However, this causes its own set of difficulties, because you can'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's Presets (under Max MIDI Device), then restart Live running it as Admin, and run the installer at that point. You'll still have to select the installer payload, but it should autodetect everything else.

Sheesh.

== Limitations ==

All I can really say is: '''READ THE DIRECTIONS.''' I've done my best to make the installation as painless as possible, and I've included as much documentation both with the Installer patches and in this Wiki as I can think to.

That said, this is the first 'm4l Native' installer that I've seen in the wild, and I'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 "Install" button, which still eases the process of having to manually install all of the files.

The newest installation will get tagged with the revision number (e.g. blahblahb992'''r030112''') , the suffix being the date that it was compiled for release. That means it should add to/overwrite any old data.

Currently, we're still testing out the Installer on different systems to see what works and what won't. There may be problems with Lion and Win7, because I don't have an installation of either at the moment and I'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'll work on it.

Otherwise, unless your system is "REALLY" 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't).

== Python Persistence ==

One of the things I'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't make a bit of difference, but if you're having problems with things not working the way they are supposed to, it is the first thing I'd try to get things back to normal.

== Live Crashes ==

I'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's log.txt file. It won't hurt anything, and its solved the only crashes that I'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.

== Root Volume ==

Don't expect the installer to work on Windows if you've got your base installation on a drive other than C:\. It just probably won't.

== Manual Installation ==

If the installer just doesn't work for you for whatever reason, you can always put the files where they go manually. Here's some more information on how to do that:

[[Manual Installation|Manual Installation]]

Modlink

2013-11-19T09:03:29Z

Amounra: /* Overview */

== Video Tutorials ==

[http://www.youtube.com/watch?v=ylDHUlO_m1c MorphicField's Tutorial]

=='''Overview'''==

Modlink is a mod that allows connection to any standard monome patch as though it were a mod.

[[File:Modlink_pic.png]]

The top selection menu allows changing the communication protocol used to connect to the monome patch.

The title-bar also contains the unique instance number of the modlink. This number will also be present in any Bonjour listing available in a serialosc monome patch, so make sure when enabling a connection from serialosc that you choose the right modlink instance.

The prefix, input, and output port textboxes can be changed manually, or via serialosc. New settings initiated from serialosc will automatically be entered in the user interface.

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.''

''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]
----------

Here's a screenshot of 3 instances of modlink being used, 2 with SerialOSC connections (_xor and polygome), and one with MonomeSerial (molar).

[[File:Modlink_example.png]]

== Examples ==

Here's an example using the older Monolink plugin from b992. This setup is kind of redundant now, since LCC has been ported over to a mod.

Monolink using the BlockMod control surface and Live Clip Chopper:

These are the basic settings for getting the [http://www.maxforlive.com/library/device.php?id=230 Live Clip Chopper] to work with Monolink.

[[File:clipchopwin.jpg]]

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]]

Modlink

2013-11-19T09:03:14Z

Amounra: /* Overview */

== Video Tutorials ==

[http://www.youtube.com/watch?v=ylDHUlO_m1c MorphicField's Tutorial]

=='''Overview'''==

Modlink is a mod that allows connection to any standard monome patch as though it were a mod.

[[File:Modlink_pic.png]]

The top selection menu allows changing the communication protocol used to connect to the monome patch.

The title-bar also contains the unique instance number of the modlink. This number will also be present in any Bonjour listing available in a serialosc monome patch, so make sure when enabling a connection from serialosc that you choose the right modlink instance.

The prefix, input, and output port textboxes can be changed manually, or via serialosc. New settings initiated from serialosc will automatically be entered in the user interface.

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.''

''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"]
----------

Here's a screenshot of 3 instances of modlink being used, 2 with SerialOSC connections (_xor and polygome), and one with MonomeSerial (molar).

[[File:Modlink_example.png]]

== Examples ==

Here's an example using the older Monolink plugin from b992. This setup is kind of redundant now, since LCC has been ported over to a mod.

Monolink using the BlockMod control surface and Live Clip Chopper:

These are the basic settings for getting the [http://www.maxforlive.com/library/device.php?id=230 Live Clip Chopper] to work with Monolink.

[[File:clipchopwin.jpg]]

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]]

Modlink

2013-11-19T09:02:42Z

Amounra: /* Overview */

== Video Tutorials ==

[http://www.youtube.com/watch?v=ylDHUlO_m1c MorphicField's Tutorial]

=='''Overview'''==

Modlink is a mod that allows connection to any standard monome patch as though it were a mod.

[[File:Modlink_pic.png]]

The top selection menu allows changing the communication protocol used to connect to the monome patch.

The title-bar also contains the unique instance number of the modlink. This number will also be present in any Bonjour listing available in a serialosc monome patch, so make sure when enabling a connection from serialosc that you choose the right modlink instance.

The prefix, input, and output port textboxes can be changed manually, or via serialosc. New settings initiated from serialosc will automatically be entered in the user interface.

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.''

''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]
----------

Here's a screenshot of 3 instances of modlink being used, 2 with SerialOSC connections (_xor and polygome), and one with MonomeSerial (molar).

[[File:Modlink_example.png]]

== Examples ==

Here's an example using the older Monolink plugin from b992. This setup is kind of redundant now, since LCC has been ported over to a mod.

Monolink using the BlockMod control surface and Live Clip Chopper:

These are the basic settings for getting the [http://www.maxforlive.com/library/device.php?id=230 Live Clip Chopper] to work with Monolink.

[[File:clipchopwin.jpg]]

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]]

Modlink

2013-11-19T09:01:34Z

Amounra: /* Overview */

== Video Tutorials ==

[http://www.youtube.com/watch?v=ylDHUlO_m1c MorphicField's Tutorial]

=='''Overview'''==

Modlink is a mod that allows connection to any standard monome patch as though it were a mod.

[[File:Modlink_pic.png]]

The top selection menu allows changing the communication protocol used to connect to the monome patch.

The title-bar also contains the unique instance number of the modlink. This number will also be present in any Bonjour listing available in a serialosc monome patch, so make sure when enabling a connection from serialosc that you choose the right modlink instance.

The prefix, input, and output port textboxes can be changed manually, or via serialosc. New settings initiated from serialosc will automatically be entered in the user interface.

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.''

''It is necessary to install the zeroconf version of the monomeserial MaxMSP object in order to use modLink with most current published applications.''

----------

Here's a screenshot of 3 instances of modlink being used, 2 with SerialOSC connections (_xor and polygome), and one with MonomeSerial (molar).

[[File:Modlink_example.png]]

== Examples ==

Here's an example using the older Monolink plugin from b992. This setup is kind of redundant now, since LCC has been ported over to a mod.

Monolink using the BlockMod control surface and Live Clip Chopper:

These are the basic settings for getting the [http://www.maxforlive.com/library/device.php?id=230 Live Clip Chopper] to work with Monolink.

[[File:clipchopwin.jpg]]

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]]

Troubleshooting

2013-08-22T07:52:43Z

Amounra: /* mod Problems */

If you're having problems getting things to work with Monomodular, here are some typical blunders that can cause things to not work as expected.

=Installation Problems=

'''The installer says it ran into a bunch of errors.'''

This usually happens with the Win7 installer, and is due to permissions issues. I'm working on a fix, but in the meantime, the best thing to do is visit the [Manual Installation|Manual Installation] page and just copy the files to their proper locations on your system.

'''Pressing the SVN button doesn't do anything'''

If your using Windows, you will need to install SlikSVN in order to use the Subversion functionality, as no subversion support is included natively with Windows operating systems.

=Script Problems=
'''None of the Monomodular Control Surface Scripts show up in my MIDI Preferences'''

Did you restart Live? Restart Live.

'''My controller works with Live, but won't enter modMode'''

You probably have neglected to assign the Monomodular script to one of the Control Surface slots in Live's MIDI Preferences. It must be present in addition to the control surface that you're using.

'''Monomodular is installed in a control surface slot, but mods still won't connect'''

First, check to see if you have assigned compatible versions of Monomodular scripts in Live's MIDI Preferences. The version tags of all the scripts should be the same (e.g. r111312).

Make sure that you are using one of the frozen files from your m4l directory, and not the development version in the Frozen subfolder of the Monomodular installation (these will only be present if you installed Monomodular from the SVN source).

'''Uhmm....still no dice'''

Next, have a look at your Max status window to see if there are errors. That will give us an idea of what's going wrong. I'm easy to reach, drop me an email with a screenpic of your Max status window and a copy of your log.txt file from Live's preferences.

= mod Problems =

Certain mods (Plinko, Boiingg, and AumBoids) require Java externals that should have been installed in the /Cycling '74/java/classes folder of your Max directory (the installer should have done this for you). Make sure they are there. If you're using a Windows OS, you may need to install a JavaRuntime in order to get these to work (it's not installed by default). You will also need to perform this step on newer versions of MacOS (10.8). You can get JavaRuntime from here:
[[http://www.java.com/en/download/index.jsp|Java Runtime Download]]

Sometimes, placing the aumhaa_blocks folder in the Max patches directory doesn't work. I've had this occur on several machines, usually after upgrading max or cloning a drive on the machine out of necessity. You'll know this is the case if the "Number Block" design is missing from the top left of the mod. To remedy this, it may be necessary to open the Max editor in Live and manually select the aumhaa_blocks folder from Max's Options>File Preferences menu.

Polygome

2012-12-06T08:38:01Z

Amounra: Reverted edits by Amounra (talk) to last revision by Okyeron

==Video Tutorials==

[http://www.youtube.com/watch?v=W1O8c8vLVMY&list=UUffhayZv3WqTz2ZaEkIwR3w&index=3&feature=plcp Tutorial for Polygome with OhmRGB]

==Overview==

[[File:Polygome_pic.png]]

==Original Docs==

[http://docs.monome.org/doku.php?id=app:polygome monome patch]

Polygome isn't an easy concept...but I think its one of the best patches Stretta has made.

This port behaves mostly the same as his, but lives in Live and remembers its states. And you can run multiples.

The right hand buttons (scene launch) select which
mode the grid is in.
Mode 1 is play. The key pressed is the root of the sequence that is selected.
Mode 2 is record. You record the sequence by pressing up to 16 cells on the grid.
Mode 3 programs velocity for each step.
Mode 4 programs duration for each step.
The bottom row of Mode 4 allows for turning off or on each step.

You can send MIDI to polygome and change the the scale that is assigned.

The top right and left corner of the grid is the hold button.

Try the gomeizer if you're stumped...its instant gratification (after a wait of a few seconds to randomize everything)....

Then off to google, to find out whats really going on ;)

'''IMPORTANT TIP: Live's transport ''must'' be running in order for polygome to do ''anything''.'''

[[Category:Mods]]

Polygome

2012-12-06T08:35:12Z

Amounra:

==Overview==

[[File:Polygome_pic.png]]

==Video Tutorials==

[http://www.youtube.com/watch?v=W1O8c8vLVMY&list=UUffhayZv3WqTz2ZaEkIwR3w&index=3&feature=plcp Tutorial for Polygome with OhmRGB]

==Original Docs==

[http://docs.monome.org/doku.php?id=app:polygome monome patch]

Polygome isn't an easy concept...but I think its one of the best patches Stretta has made.

This port behaves mostly the same as his, but lives in Live and remembers its states. And you can run multiples.

The right hand buttons (scene launch) select which
mode the grid is in.
Mode 1 is play. The key pressed is the root of the sequence that is selected.
Mode 2 is record. You record the sequence by pressing up to 16 cells on the grid.
Mode 3 programs velocity for each step.
Mode 4 programs duration for each step.
The bottom row of Mode 4 allows for turning off or on each step.

You can send MIDI to polygome and change the the scale that is assigned.

The top right and left corner of the grid is the hold button.

Try the gomeizer if you're stumped...its instant gratification (after a wait of a few seconds to randomize everything)....

Then off to google, to find out whats really going on ;)

'''IMPORTANT TIP: Live's transport ''must'' be running in order for polygome to do ''anything''.'''

[[Category:Mods]]

Polygome

2012-12-06T08:34:45Z

Amounra:

Polygome

2012-12-06T08:30:07Z

Amounra:

=Test=

=='''Video Tutorials'''==

[http://www.youtube.com/watch?v=W1O8c8vLVMY&list=UUffhayZv3WqTz2ZaEkIwR3w&index=3&feature=plcp Tutorial for Polygome with OhmRGB]

=='''Overview'''==

[[File:Polygome_pic.png]]

=='''Original Docs'''==

[http://docs.monome.org/doku.php?id=app:polygome monome patch]

Polygome isn't an easy concept...but I think its one of the best patches Stretta has made.

This port behaves mostly the same as his, but lives in Live and remembers its states. And you can run multiples.

The right hand buttons (scene launch) select which
mode the grid is in.
Mode 1 is play. The key pressed is the root of the sequence that is selected.
Mode 2 is record. You record the sequence by pressing up to 16 cells on the grid.
Mode 3 programs velocity for each step.
Mode 4 programs duration for each step.
The bottom row of Mode 4 allows for turning off or on each step.

You can send MIDI to polygome and change the the scale that is assigned.

The top right and left corner of the grid is the hold button.

Try the gomeizer if you're stumped...its instant gratification (after a wait of a few seconds to randomize everything)....

Then off to google, to find out whats really going on ;)

'''IMPORTANT TIP: Live's transport ''must'' be running in order for polygome to do ''anything''.'''

[[Category:Mods]]