Difference between revisions of "Getting Started"

From ModWiki
Jump to: navigation, search
(created)
 
(Installing Mods)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
Placeholder for getting started page.
+
== If you are upgrading from a previous version: ==
 +
 
 +
 
 +
The installer adds a suffix to all of the folders that it installs, so that you can tell what is new.  The highest suffix will be the most recent build.  The installer does not delete anything, and is incapable of overwriting your current filesystem, but will replace missing files if they've been deleted in the current revision, so you can always run it to fix an installation that has been broken by moving or deleting files accidentally.
 +
 
 +
In the future there may be an option to remove old versions, but its much safer for me to merely add new files.  I don't want to go mucking about with your harddrives.
 +
 
 +
The first thing you will want to do is replace the old versions of the Control Surface scripts in Live's MIDI preferences.  Just change each one to the most recent version, and as always, DON"T FORGET TO INSTALL THE MONOMODULAR SCRIPT.  Specifics about each CS script can be found with links on the main page.
 +
 
 +
The next thing to do is replace any Mods (monomodular m4l patches) that you may have in your songs.  As a general rule, it is most efficient to drop the new version directly on top of the title bar of the old patch from Live's browser.  In most cases, this is safe, and will maintain any presets you have generated with the old version (unless, for some reason, the preset system has completely changed since the last version was released...this is very rare, but in such an instance information will be made available on the Mod's wiki page about the particulars of the changes).
 +
 
 +
That's it.  Any other changes will have been made internally.  You might also want to check the Monomodular folder that was placed on your desktop, as it will have the most recent versions of the TouchOSC and Lemur scripts for use with the iPad (and soon iPod/iPhone).
 +
 
 +
 
 +
== If this is your first installation: ==
 +
 
 +
 
 +
 
 +
==== Selecting the correct Python Scripts ====
 +
 
 +
 
 +
It's a good idea to navigate to the Main Page of the wiki (from the left side of this page) to check out what Monomodular does, and how to install it.
 +
 
 +
The first thing you will want to do is install the Monomodular script.  If you haven't done so yet, you'll need to restart Live.  Then, navigate to Live's preferences (cmd+',' on Mac, ctrl+',' on Windows), go to the MIDI Sync tab, and select the Monomodular_bxxrxxx script (I add this as the last one, since the position of the script determines the color of Live's navigation box for that script, but you can put it in any of the available slots).  DO NOT select any inputs or outputs for it.  They should both say 'None'.  It should look like this:
 +
 
 +
[[File:Mod_cs_install.jpg]]
 +
 
 +
The Monomodular script is a hub that communicates with all of the Client controller scripts (e.g. a LaunchPad or an APC40) and links them to the Mods that are loaded in your Live set.  It's presence is always necessary for any communication to occur between your controllers and your Mods.  However, it is possible to use all of the control scripts without the presence of the Monomodular script if you are only planning on using the API functionality of the script (i.e. track control, effects switching, etc).  It may still, however, be necessary to use certain m4l patches to communicate via OSC to the controller (e.g. if you are using an iPad with TouchOSC or Lemur software).
 +
 
 +
Next, install the appropriate Control Surface Script for your particular controller.  Monomodular supports a variety of different control surfaces, and you can find the particulars of how to set each one up for use from the [[Main Page]].
 +
 
 +
Certain scripts also require a Mod (i.e. a m4l patch) to interact with the control surface if they are going to communicate through OSC.
 +
 
 +
Keep in mind that Monomodular is structured so that you can use multiple versions of the same Controller client script
 +
 
 +
==== Installing Mods ====
 +
 
 +
A Mod is a modular Max client patch built for use with Monomodular.  When talking about Monomodular, Mod is the basic client (you can use up to 16 of them in each Live project).
 +
 
 +
There are a variety of Mods that can be installed.  To install it, merely drag it from Live's browser and drop it on a track that is appropriate for its effect type.  Some of the Mods with the installation are actually Instruments or Audio Effects, but for ease of installation and to simplify finding them, they are all installed to the same folder in the Max MIDI Effects presets.
 +
 
 +
To learn what different Mods do, and how to use them, you can either use the help button in the patch (it will navigate to the appropriate Wiki page) or you can go to the [[Mods]] for a list of all of them.

Latest revision as of 20:35, 29 December 2011

If you are upgrading from a previous version:

The installer adds a suffix to all of the folders that it installs, so that you can tell what is new. The highest suffix will be the most recent build. The installer does not delete anything, and is incapable of overwriting your current filesystem, but will replace missing files if they've been deleted in the current revision, so you can always run it to fix an installation that has been broken by moving or deleting files accidentally.

In the future there may be an option to remove old versions, but its much safer for me to merely add new files. I don't want to go mucking about with your harddrives.

The first thing you will want to do is replace the old versions of the Control Surface scripts in Live's MIDI preferences. Just change each one to the most recent version, and as always, DON"T FORGET TO INSTALL THE MONOMODULAR SCRIPT. Specifics about each CS script can be found with links on the main page.

The next thing to do is replace any Mods (monomodular m4l patches) that you may have in your songs. As a general rule, it is most efficient to drop the new version directly on top of the title bar of the old patch from Live's browser. In most cases, this is safe, and will maintain any presets you have generated with the old version (unless, for some reason, the preset system has completely changed since the last version was released...this is very rare, but in such an instance information will be made available on the Mod's wiki page about the particulars of the changes).

That's it. Any other changes will have been made internally. You might also want to check the Monomodular folder that was placed on your desktop, as it will have the most recent versions of the TouchOSC and Lemur scripts for use with the iPad (and soon iPod/iPhone).


If this is your first installation:

Selecting the correct Python Scripts

It's a good idea to navigate to the Main Page of the wiki (from the left side of this page) to check out what Monomodular does, and how to install it.

The first thing you will want to do is install the Monomodular script. If you haven't done so yet, you'll need to restart Live. Then, navigate to Live's preferences (cmd+',' on Mac, ctrl+',' on Windows), go to the MIDI Sync tab, and select the Monomodular_bxxrxxx script (I add this as the last one, since the position of the script determines the color of Live's navigation box for that script, but you can put it in any of the available slots). DO NOT select any inputs or outputs for it. They should both say 'None'. It should look like this:

Mod cs install.jpg

The Monomodular script is a hub that communicates with all of the Client controller scripts (e.g. a LaunchPad or an APC40) and links them to the Mods that are loaded in your Live set. It's presence is always necessary for any communication to occur between your controllers and your Mods. However, it is possible to use all of the control scripts without the presence of the Monomodular script if you are only planning on using the API functionality of the script (i.e. track control, effects switching, etc). It may still, however, be necessary to use certain m4l patches to communicate via OSC to the controller (e.g. if you are using an iPad with TouchOSC or Lemur software).

Next, install the appropriate Control Surface Script for your particular controller. Monomodular supports a variety of different control surfaces, and you can find the particulars of how to set each one up for use from the Main Page.

Certain scripts also require a Mod (i.e. a m4l patch) to interact with the control surface if they are going to communicate through OSC.

Keep in mind that Monomodular is structured so that you can use multiple versions of the same Controller client script

Installing Mods

A Mod is a modular Max client patch built for use with Monomodular. When talking about Monomodular, Mod is the basic client (you can use up to 16 of them in each Live project).

There are a variety of Mods that can be installed. To install it, merely drag it from Live's browser and drop it on a track that is appropriate for its effect type. Some of the Mods with the installation are actually Instruments or Audio Effects, but for ease of installation and to simplify finding them, they are all installed to the same folder in the Max MIDI Effects presets.

To learn what different Mods do, and how to use them, you can either use the help button in the patch (it will navigate to the appropriate Wiki page) or you can go to the Mods for a list of all of them.