Difference between revisions of "Main Page"

From ModWiki
Jump to: navigation, search
(Installation)
(Supported controllers)
 
(33 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''MediaWiki has been successfully installed.'''
+
== 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]].
  
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.
+
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.
  
== '''Monomodular''' ==
+
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.
  
Monomodular as a whole is a modular environment for plugin control and development for use with grid-based controllers in Max for Live. It began as a multi-color Monome experiment over two years ago. It was designed with live musical performance as its most important goal. It is currently still in development, and is being offered as beta, but is being used for both production and performance by its author and many others (so you should, too!).
+
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 ==
  
Monomodular is roughly based on a server/client principle, where Monomodular is an intermediary between different plugins and controllers.  The basic idea is that Monomodular offers multiple simultaneous controllers access to multiple simultaneous plugins, and does so in a seamless and transparent fashion.  Monomodular stores the states of all its clients, and is capable of interpreting a library of standard functions that are called from each individual control surface type in such a manner so that it does not need to be aware of what kind of control surface is connected to it in order to interpret its calls or correctly format its returns to the receiving component.  The type of data its stores is fairly generic and conforms to the monome standard in some ways, but is also fairly arbitrary in that the core can be easily modified to store different types of data to suit the situation (for instance, it has been easily adapted to handle data types and addresses for both the Livid Code and CNTRL:R hardware devices).
+
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.
  
As of version b99, the core of Monomodular is a Python control surface plugin that runs in Ableton Live's proprietary Python environment, containing a basic framework for communicating with several types of hardware (currently Launchpad, APC20, APC40, Livid's Ohm64, Block, Code, and iPad via a custom interface built both TouchOSC and Lemur). It allows communication between up to 5 grid controllers with up to 16 client patches directly from the surface of the controller. It gives basic functionality of navigating and displaying a Monome256 workspace, and provides the base functionality for quickly writing or converting new plugins to work with its format.
+
== 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.
  
As of version b993, the Monomodular Python script also contains socket functionality that allows it to natively communicate with devices designed to work with monome hardware without any further component needs.  It publishes via  Bonjour its address and ports, and communicates directly from the Python workings within Live.
+
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 ======
  
There are many client patches included with the suite.  Most of the early patches were ports of popular monome patches, but now the release includes many of amounra's own creations.  The majority are for MIDI generation and generative processes, but the capabilities for using Monomodular are only limited by the imagination of the scripter.
+
*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]
  
 +
*[[How to use the BlockMod script|Livid's Block]]
  
On the MaxMSP side of things, the Monomodular format is largely dependent upon a single javascript object, which can be manipulated in many different ways.  In addition to using the prebuilt mods, it offers the capability of creating one's own custom patches easily in MaxforLive and using them within the framework of Monomodular, or adapting patches that you've already built to be used with a grid controller.
+
*[[How to use the Codec script|Livid's Code]]
  
== '''Installation''' ==
+
*[[How to use the iOs scripts|Apple's iPad, using Lemur App]]
  
You can view a more detailed explanation of how the installer works by visiting the [[Installation]] page.
+
*[[How to use the LaunchMod script|Novation's Launchpad]]
  
==== How? ====
+
*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]
--------
 
  
Download the installer only, and use its "Subversion" button to download the most current version (recommended):
+
*[[How to use the Cntrlr script|Livid's CNTRL:R]]
  
[http://www.aumhaa.com/Monomodular/Monomodular_Installer_OSX.amxd  OSX Installer]
+
*[[How to use the Base script|Livid's Base]]
  
[http://www.aumhaa.com/Monomodular/Monomodular_Installer_Win.amxd Windows Installer]
+
== What Comes with Mod ==
  
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 that takes compatible commands).
+
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.
  
or
+
== Why doesn't anything work!? ==
  
Download the last major build, with all dependent files frozen, here:  [http://www.aumhaa.com/Monomodular/Monomodular_b993.zip Monomodular b993 Content]
+
Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.
  
 +
==Links==
 +
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]
  
==== Where? ====
+
[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]
---------
 
  
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.
+
[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]
 
 
 
 
==== What? ====
 
----------
 
 
 
The Installer patch is a fairly simple utility that parses information about your Live and Max installations and tries to determine where files should be located on your system.  Because Monomodular is not an application in itself, but instead a collection of scripts and Max patches, it is somewhat exempt from the normal routines of the average installer.  The installer patch gets what information it can from Ableton's log.txt file in its preferences folder and parses the locations from your currently running instance of Live.  This process is, however, not perfect, and under certain circumstances you will have to locate the correct installation paths manually.
 
 
 
If this is a persistent problem, please contact amounra with the specifics, and a copy of your log.txt file, so that the installer can be improved.
 
 
 
The installer installs three main categories of files:
 
 
 
'''Mods'''
 
 
 
MaxforLive patches that do 'something' in conjunction with a grid controller.  The list is growing, but you can go to the [[Mods]] page to see what they are about.  You can also access their information page from within the plugin itself by hitting the help button and linking to this wiki.
 
 
 
'''_Framework Scripts'''
 
 
 
These are the Python scripts that allow your controller to make things happen in live and link to the Monomodular hub (also a Python script). 
 
 
 
'''Other Stuff'''
 
 
 
Miscellaneous files that need to be here or there in order for things to work right.
 
 
 
=='''How Monomodular Works'''==
 
 
 
You can read a description of the basic functionality of every Monomodular enabled control script on the [[How Monomodular Works]] page.  For a detailed description of the rest of a control scripts functionality, please refer to the links below:
 
 
 
[[How Monomodular Works|A Basic description of how Monomodular works]]
 
 
 
[[How to use the Ohm64 script]]
 
 
 
[[How to use the BlockMod script]]
 
 
 
[[How to use the LaunchMod script]]
 
 
 
[[How to use the Codec script]]
 
 
 
[[How to use the AumPC scripts]]
 
 
 
[[How to use the iOs scripts]]
 
 
 
[[Help|Building your own Mods]]
 
 
 
=='''What Comes with Monomodular'''==
 
 
 
There is a listing of all the current content with an explanation of how they work on the [[Mods]] page.  This is an evolving instruction and commentary on each plugin, so its a good idea to check back from time to time to find new information.
 
 
 
[[Mods|The Mods Listing Page]]
 

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