Difference between revisions of "Main Page"
(→How Monomodular Works) |
(→How?) |
||
| Line 26: | Line 26: | ||
Download the installer only, and use subversion to download the most current version: (placeholder) | Download the installer only, and use subversion to download the most current version: (placeholder) | ||
| − | |||
| + | If you are using Windows, you will need to install the command-line subversion tool, SlikSVN (or something else that takes compatible commands). | ||
| + | |||
| + | |||
| + | ==== 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. | ||
| + | |||
| + | ==== 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. | ||
| + | |||
| + | |||
| + | ==== Who? ==== | ||
| + | |||
| + | Some guy with nothing better to do, I guess. You should be nice to him ;) | ||
=='''How Monomodular Works'''== | =='''How Monomodular Works'''== | ||
Revision as of 22:51, 29 December 2011
MediaWiki has been successfully installed.
Consult the User's Guide for information on using the wiki software.
Contents
Monomodular
Monomodular 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!).
Monomodular is a Python control surface plugin, 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.
There are many client patches included with the suite. Most of the early patches were ports of popular monome patches, and I have released many of amounra's own creations since first publishing Monomodular. The majority are for MIDI generation and generative processes, but the capabilities for using Monomodular are only limited by the imagination of the scripter.
Installation
How?
Download either the last major build, with all dependent files frozen, here: (placeholder)
or
Download the installer only, and use subversion to download the most current version: (placeholder)
If you are using Windows, you will need to install the command-line subversion tool, SlikSVN (or something else that takes compatible commands).
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.
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.
Who?
Some guy with nothing better to do, I guess. You should be nice to him ;)
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 to use the BlockMod script
