Difference between revisions of "Main Page"

From ModWiki
Jump to: navigation, search
m (there's already a Log.txt page! Who knew!)
(Supported controllers)
 
(31 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== 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]]. 
  
'''Monomodular''' is a modular environment for using grid-style controllers with Max For Live plugins, as well as a framework for M4L plugin development. 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 still under active development, and is being offered as beta, but is being used for both production and performance by its author and many others (you should, too!).
+
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 is roughly based on a server/client principle, with Monomodular acting as an intermediary between different plugins and grid controllers.
+
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.
 
 
[This should probably be simplified, with the bulk being moved to a more technical page] 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 which 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).
 
 
 
 
 
As of version b99, the core of Monomodular is a Python control surface plugin which runs in Ableton Live's proprietary Python environment, contains a basic framework for communicating with [[#Supported devices|several types of hardware]]. 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.
 
 
 
 
 
As of version b993, the Monomodular Python script also contains socket functionality which 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.
 
 
 
 
 
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.
 
 
 
 
 
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 which you've already built to be used with a grid controller.
 
  
 +
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 ==
 
== Installation ==
  
==== How? ====
+
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).
  
<strike>
+
For the details about how where everything goes, please visit the [[Installation]] page.
Download the installer and use its "Subversion" button to install the most recent version (recommended):
 
  
[http://www.aumhaa.com/Monomodular/Monomodular_Installer_OSX.amxd OSX Installer]
+
== How Mod Works ==
  
[http://www.aumhaa.com/Monomodular/Monomodular_Installer_Win.amxd Windows Installer]
+
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.
  
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).
+
You can read a description of the basic functionality of the Mod-enabled control scripts on the [[How Mod Works]] page.
</strike>
+
Each supported controller has its own page with further instructions and tips for usage.
  
SVN installation is not yet available in b993, so just download the complete [http://www.aumhaa.com/Monomodular/Monomodular_b993.zip Monomodular b993 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.
+
====== Supported controllers ======
  
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.
+
*[[How to use the Ohm64 script|Livid's Ohm64 and OhmRGB]]
  
==== What? ====
+
*[[How to use the BlockMod script|Livid's Block]]
  
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 a bit differently than most things. 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.
+
*[[How to use the Codec script|Livid's Code]]
  
If you have a persistent problem with installation, please contact amounra with the specifics, and a copy of Ableton's '''[[log.txt]]''', so that the installer can be improved.
+
*[[How to use the iOs scripts|Apple's iPad, using Lemur App]]
  
The installer installs three main categories of files:
+
*[[How to use the LaunchMod script|Novation's Launchpad]]
 
 
* '''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 ==
 
 
 
You can read a description of the basic functionality of every Monomodular-enabled control script on the [[How Monomodular Works]] page.
 
More detailed information is available at each controller's page.
 
 
 
====== Supported devices ======
 
  
 
*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]
 
*[[How to use the AumPC scripts|Akai's APC 20 and APC 40]]
  
*[[How to use the BlockMod script|Livid's Block]]
+
*[[How to use the Cntrlr script|Livid's CNTRL:R]]
 
 
*[[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 Base script|Livid's Base]]
  
*[[How to use the LaunchMod script|Novation's Launchpad]]
+
== What Comes with Mod ==
  
*[[How to use the Ohm64 script|Livid's Ohm64]]
+
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!? ==
  
[[Help|Building your own Mods]]
+
Check out the '''[[Troubleshooting|Troubleshooting Page]]'''.
  
 +
==Links==
 +
[https://www.youtube.com/user/amounra93 amounra93 YouTube Channel with Tutorials]
  
== What Comes with Monomodular ==
+
[http://animatek.net/2012/11/monomodular-el-emulador-para-launchpad-de-monome-definitivo/ Animatek Review & Tutorial (Spanish)]
  
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.
+
[http://www.youtube.com/watch?v=r770tr4lufc&feature=plcp Morphicfield's YouTube Channel with Tutorials]

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