Difference between revisions of "Main Page"

From ModWiki
Jump to: navigation, search
(How Monomodular Works)
(Supported controllers)
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
== 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.
+
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]].
  
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.
+
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 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.
+
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.  
  
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 Mod development framework allows developers to leverage the full power of Live + M4L + Max/MSP.
  
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]].
+
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).
 
 
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 ==
 
== 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).
+
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.
 
For the details about how where everything goes, please visit the  [[Installation]] page.
  
== How Monomodular Works ==
+
== 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.
+
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 Monomodular-enabled control scripts on the [[How Monomodular Works]] page.
+
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.
 
Each supported controller has its own page with further instructions and tips for usage.
  
Line 33: Line 31:
 
*[[How to use the Codec script|Livid's Code]]
 
*[[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 iOs scripts|Apple's iPad, using Lemur App]]
  
 
*[[How to use the LaunchMod script|Novation's Launchpad]]
 
*[[How to use the LaunchMod script|Novation's Launchpad]]
Line 43: Line 41:
 
*[[How to use the Base script|Livid's Base]]
 
*[[How to use the Base script|Livid's Base]]
  
== What Comes with Monomodular ==
+
== 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.
 
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.
Line 49: Line 47:
 
== Why doesn't anything work!? ==
 
== 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]]'''.
+
Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.
  
 
==Links==
 
==Links==

Latest revision as of 13:34, 5 April 2015

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 monome emulation experiment in 2008. It was designed with live music performance as its primary goal, and borrows heavily from the 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.

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

What Comes with Mod

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

Links

amounra93 YouTube Channel with Tutorials

Animatek Review & Tutorial (Spanish)

Morphicfield's YouTube Channel with Tutorials