ModWiki - User contributions [en]

NomeOut

2011-12-31T08:55:52Z

74.194.92.197: Created page with "Placeholder for Nomeout page"

Placeholder for Nomeout page

Talk:Main Page

2011-12-31T08:54:33Z

74.194.92.197: Blanked the page

Talk:Main Page

2011-12-31T08:53:45Z

74.194.92.197: Created page with "Testing"

Testing

How to use the Ohm64 script

2011-12-30T10:05:11Z

74.194.92.197: /* Mod Mode */

== Some Video Tutorials ==

[http://www.youtube.com/watch?v=9ypoR7JH1cY&list=UUffhayZv3WqTz2ZaEkIwR3w&index=8&feature=plcp Earliest tutorial with old help patcher and little commentary]

[http://www.youtube.com/watch?v=00mlz1DpUTY&list=UUffhayZv3WqTz2ZaEkIwR3w&index=7&feature=plcp b99 Release tutorial]

== Summary ==

The only component that is strictly necessary to get the Remote Script working in Ableton is the Script itself. It goes in the Live Application Bundle, in the "Remote Scripts" folder.

In order to use the Monomodular portion of the script, it is necessary to have Max5.18 installed, and the client plugins that are contained in the suite. I will cover the Monomodular's functionality in a seperate place.

Pete @Livid says this script melts peoples' brains. Really, its not all that complicated. I tried to fit as much functionality as I could into what was available on the controller, and I can understand why that's intimidating. But its very hard to get lost unless you insist on pressing more than one button at a time without knowing what the combination is going to do. Make this thine performance mantra: 'I shall not press two buttons at once until I understand....'

I highly recommend getting a copy of the Ohm64LCD patch; in addition to letting you know at all times what it is that you are controlling, it will also tell you precisely what the values of your parameters are (in plainspeak, not MIDIeze). Of course, you'll need m4l in order to use it.

There are three independent mixers available. Two of them control four channels at a time, the third uses all 8 faders to control 8 channels.

Each mixer is independent, and remembers the last tracks that were assigned to it. When the Ohm is first connected to Live, it will automatically be in split mixer mode. If there are more than four tracks in the project, the mixer will be assigned to the first 8 tracks, otherwise both sides of the mixer will be assigned to whatever tracks are present.

Since there are several different "shift modes" available within the script, the most important concept to grasp about this scheme is that there are two shift buttons: one left, and one right. They are on either side of the crossfader. By holding down the shift button, you gain access to a bunch of different alternative functions.

== The GRID ==

Rows 1-5: Fire Session Clips

Row 6: Mute

Row 7: Solo

Row 8: Arm

Exception: When in Right Mixer Mode 4, The right side of the Grid is mapped to DrumRacks (Pad Translation; see below**).

== The SHIFTED GRID ==

Rows 1-5(except for column 8): Session Zoom Navigation

Row 6: Record, Overdub, Loop, Stop All Clips, Zero All Sends 1-4

Row 7: Crossfader Assignment

Row 8: Stop Clip

Column 8 (Rows 1-5): Fire Scene

By holding down one of the shifts and pressing one of the channel select buttons on the same side of the controller, you can enter a different "Shift Mode".

== The MODES ==

=== For the Left Mixer, Modes 1-4 ===

'''Faders are always mapped to Track Volume (or MIDI Velocity...see below****).'''

Left Mode 1: Left Dials(top 8) control selected Device, Left Dials (bottom 4) control Selected Track's Sends.

Left Mode 2: Left Dials control Sends 1-3 for the corresponding Fader's Track.

Left Mode 3: Left Dials (top 8) control Track Filter for corresponding Fader, Left Dials (bottom 4) control Pan for corresponding Fader.

Left Mode 4: Left Dials are remapped to channel 2 so that they are User Mappable with Live.

=== For the Right Mixer, Modes 1-4 ===

Right Mode 1: Faders control Track Volume, Mixer offset at Track 5, Right Dials control Returns 1-4.

Right Mode 2: Faders control Track Volume, Mixer offset at Track 9, Right Dials control Returns 1-4.

Right Mode 3: Faders control Track Volume, Mixer offset at Track 13, Right Dials control Returns 1-4.

Right Mode 4: Faders control Return Volume, Right Dials control Return Pan

'''Buttons below the Faders select Track in all modes (except when shift is being held...see below*).'''

== The FUNCTIONS ==

Function Buttons (top right) have the following functions (top left to bottom right):

Session Nav up, Play, Stop, Session Nav down, Session Nav left, Session Nav right.

Function Buttons (top right) have the following Shifted functions (top left to bottom right):

Device Bank up, Device ON/OFF, Device Lock, Device Bank down, Device Nav left, Device Nav right.

'''WHILE LEFT SHIFT IS PRESSED, FADER 8 CONTROLS MASTER VOLUME.'''

'''WHILE LEFT SHIFT IS PRESSED, RIGHT DIAL 4 CONTROLS PREHEAR.'''

== MOD Mode ==

The Livid button switches the grid to Monomodular Mode. Most of the controls remain the same, but the grid is now used for controlling Monomodular patches.

When in Monomodular mode, the Function buttons (unShifted) control the following(top left to bottom right):

Grid Nav up, Lock (the bottom row of the grid remains 'Shifted'), Alt (access to Preset management in enabled patches...see below*****), Grid Nav down, Grid Nav right, Grid Nav left.

When in Monomodular mode, the Function buttons (Shifted) control the following(top left to bottom right).

Device Bank up, Play, Stop, Device Bank down, Device Nav left, Device Nav right.

Track selection and Mode navigation is identical in Monomodular Mode as in normal Session Mode.

By pressing either of the shift buttons, Zoom mode is invoked. In Zoom mode, the center lit square of buttons indicates the current selected quadrant. By pressing an area of that square, the grid changes assignment to the corresponding area.

In Zoom mode, the top row of buttons selects the current Monomodular plugin. The second row of buttons selects the channel that plugin transmits on (this is only useful when the plugins 'nomeout' is enabled...see below*****). The bottom row of buttons transmits 'Key' data (these buttons have special functionality specific to each Monomodular client...see the documenation with the client to find out what they do).

== LINKED MIXER MODE: ==

By holding one shift button and pressing the other, it is possible to Link the mixer as one. In linked mode, all mode changes correspond to the descriptions of the Left Mixer, and the right dials remain locked to the Returns. It is still possible to access the Master/Prehear levels by pressing Right Shift. The linked mixer's position (i.e. track assignment) will be recalled independently from the other two mixers, thus allowing easy navigation between 16 tracks by the press of two buttons.

<nowiki>*</nowiki> Channel Select buttons (buttons below the Faders) operate differently depending upon which Shift button is pressed. While the left-side Shift is pressed, or when the Mixer is LINKED, the left 4 buttons select a new 'Shift Mode', while the right 4 buttons select a preset Device 5-8 (see below***). When the right-side Shift is pressed, this behavior is reversed(i.e. preset Devices 1-4 on left, Mode on right).

<nowiki>**</nowiki> Pad Translation works by reassigning the Channel/Identifier of each button. In order to use it with Drum Racks, you must enable 'Track Input' for the Ohm64's MIDI Control Input, and assign that input as the source for the DrumRack's input. By default, Pad Translation transmits on MIDI Channel 10, but you can reassign this in the MonOhm_Map.py file to your liking.

<nowiki>***</nowiki> preset Device selection allows the user to select a predefined device instantly for editing with the Device knobs. In order for this functionality to work, the Device must be renamed so that its first two characters are p1 thru p8. Once named properly, the device may be selected by holding down a shift button and pressing one of the Channel Select buttons on the opposite side of the Ohm64 (e.g. a device named 'p3 Blahblah' can be selected by holding down the right shift button and pressing the channel select underneath the 3rd left side fader).

<nowiki>****</nowiki> when a Velocity plugin is inserted on a MIDI Track as the first plugin, any Fader currently controlling that Track will lock to its 'Out Hi' parameter. This allows the user to control the Volume of a MIDI only track.

<nowiki>*****</nowiki> the Key buttons have specific functionality for each Monomodular client. Generally, the first four control some aspect of the plugins operation, while the second four control the timing of the plugin. However, see the individual helpfile contained in the client to find out exactly what they do for each one. The Key buttons may be 'Locked', so that they are always accessible, by pressing the 'Lock' button (the top-center Function button when in Monomodular Mode).

phewww....I think that's about it.

How to use the Ohm64 script

2011-12-30T10:04:44Z

74.194.92.197: /* Monomodular Mode */

== Some Video Tutorials ==

[http://www.youtube.com/watch?v=9ypoR7JH1cY&list=UUffhayZv3WqTz2ZaEkIwR3w&index=8&feature=plcp Earliest tutorial with old help patcher and little commentary]

[http://www.youtube.com/watch?v=00mlz1DpUTY&list=UUffhayZv3WqTz2ZaEkIwR3w&index=7&feature=plcp b99 Release tutorial]

== Summary ==

The only component that is strictly necessary to get the Remote Script working in Ableton is the Script itself. It goes in the Live Application Bundle, in the "Remote Scripts" folder.

In order to use the Monomodular portion of the script, it is necessary to have Max5.18 installed, and the client plugins that are contained in the suite. I will cover the Monomodular's functionality in a seperate place.

Pete @Livid says this script melts peoples' brains. Really, its not all that complicated. I tried to fit as much functionality as I could into what was available on the controller, and I can understand why that's intimidating. But its very hard to get lost unless you insist on pressing more than one button at a time without knowing what the combination is going to do. Make this thine performance mantra: 'I shall not press two buttons at once until I understand....'

I highly recommend getting a copy of the Ohm64LCD patch; in addition to letting you know at all times what it is that you are controlling, it will also tell you precisely what the values of your parameters are (in plainspeak, not MIDIeze). Of course, you'll need m4l in order to use it.

There are three independent mixers available. Two of them control four channels at a time, the third uses all 8 faders to control 8 channels.

Each mixer is independent, and remembers the last tracks that were assigned to it. When the Ohm is first connected to Live, it will automatically be in split mixer mode. If there are more than four tracks in the project, the mixer will be assigned to the first 8 tracks, otherwise both sides of the mixer will be assigned to whatever tracks are present.

Since there are several different "shift modes" available within the script, the most important concept to grasp about this scheme is that there are two shift buttons: one left, and one right. They are on either side of the crossfader. By holding down the shift button, you gain access to a bunch of different alternative functions.

== The GRID ==

Rows 1-5: Fire Session Clips

Row 6: Mute

Row 7: Solo

Row 8: Arm

Exception: When in Right Mixer Mode 4, The right side of the Grid is mapped to DrumRacks (Pad Translation; see below**).

== The SHIFTED GRID ==

Rows 1-5(except for column 8): Session Zoom Navigation

Row 6: Record, Overdub, Loop, Stop All Clips, Zero All Sends 1-4

Row 7: Crossfader Assignment

Row 8: Stop Clip

Column 8 (Rows 1-5): Fire Scene

By holding down one of the shifts and pressing one of the channel select buttons on the same side of the controller, you can enter a different "Shift Mode".

== The MODES ==

=== For the Left Mixer, Modes 1-4 ===

'''Faders are always mapped to Track Volume (or MIDI Velocity...see below****).'''

Left Mode 1: Left Dials(top 8) control selected Device, Left Dials (bottom 4) control Selected Track's Sends.

Left Mode 2: Left Dials control Sends 1-3 for the corresponding Fader's Track.

Left Mode 3: Left Dials (top 8) control Track Filter for corresponding Fader, Left Dials (bottom 4) control Pan for corresponding Fader.

Left Mode 4: Left Dials are remapped to channel 2 so that they are User Mappable with Live.

=== For the Right Mixer, Modes 1-4 ===

Right Mode 1: Faders control Track Volume, Mixer offset at Track 5, Right Dials control Returns 1-4.

Right Mode 2: Faders control Track Volume, Mixer offset at Track 9, Right Dials control Returns 1-4.

Right Mode 3: Faders control Track Volume, Mixer offset at Track 13, Right Dials control Returns 1-4.

Right Mode 4: Faders control Return Volume, Right Dials control Return Pan

'''Buttons below the Faders select Track in all modes (except when shift is being held...see below*).'''

== The FUNCTIONS ==

Function Buttons (top right) have the following functions (top left to bottom right):

Session Nav up, Play, Stop, Session Nav down, Session Nav left, Session Nav right.

Function Buttons (top right) have the following Shifted functions (top left to bottom right):

Device Bank up, Device ON/OFF, Device Lock, Device Bank down, Device Nav left, Device Nav right.

'''WHILE LEFT SHIFT IS PRESSED, FADER 8 CONTROLS MASTER VOLUME.'''

'''WHILE LEFT SHIFT IS PRESSED, RIGHT DIAL 4 CONTROLS PREHEAR.'''

== Mod Mode ==

The Livid button switches the grid to Monomodular Mode. Most of the controls remain the same, but the grid is now used for controlling Monomodular patches.

When in Monomodular mode, the Function buttons (unShifted) control the following(top left to bottom right):

Grid Nav up, Lock (the bottom row of the grid remains 'Shifted'), Alt (access to Preset management in enabled patches...see below*****), Grid Nav down, Grid Nav right, Grid Nav left.

When in Monomodular mode, the Function buttons (Shifted) control the following(top left to bottom right).

Device Bank up, Play, Stop, Device Bank down, Device Nav left, Device Nav right.

Track selection and Mode navigation is identical in Monomodular Mode as in normal Session Mode.

By pressing either of the shift buttons, Zoom mode is invoked. In Zoom mode, the center lit square of buttons indicates the current selected quadrant. By pressing an area of that square, the grid changes assignment to the corresponding area.

In Zoom mode, the top row of buttons selects the current Monomodular plugin. The second row of buttons selects the channel that plugin transmits on (this is only useful when the plugins 'nomeout' is enabled...see below*****). The bottom row of buttons transmits 'Key' data (these buttons have special functionality specific to each Monomodular client...see the documenation with the client to find out what they do).

== LINKED MIXER MODE: ==

By holding one shift button and pressing the other, it is possible to Link the mixer as one. In linked mode, all mode changes correspond to the descriptions of the Left Mixer, and the right dials remain locked to the Returns. It is still possible to access the Master/Prehear levels by pressing Right Shift. The linked mixer's position (i.e. track assignment) will be recalled independently from the other two mixers, thus allowing easy navigation between 16 tracks by the press of two buttons.

<nowiki>*</nowiki> Channel Select buttons (buttons below the Faders) operate differently depending upon which Shift button is pressed. While the left-side Shift is pressed, or when the Mixer is LINKED, the left 4 buttons select a new 'Shift Mode', while the right 4 buttons select a preset Device 5-8 (see below***). When the right-side Shift is pressed, this behavior is reversed(i.e. preset Devices 1-4 on left, Mode on right).

<nowiki>**</nowiki> Pad Translation works by reassigning the Channel/Identifier of each button. In order to use it with Drum Racks, you must enable 'Track Input' for the Ohm64's MIDI Control Input, and assign that input as the source for the DrumRack's input. By default, Pad Translation transmits on MIDI Channel 10, but you can reassign this in the MonOhm_Map.py file to your liking.

<nowiki>***</nowiki> preset Device selection allows the user to select a predefined device instantly for editing with the Device knobs. In order for this functionality to work, the Device must be renamed so that its first two characters are p1 thru p8. Once named properly, the device may be selected by holding down a shift button and pressing one of the Channel Select buttons on the opposite side of the Ohm64 (e.g. a device named 'p3 Blahblah' can be selected by holding down the right shift button and pressing the channel select underneath the 3rd left side fader).

<nowiki>****</nowiki> when a Velocity plugin is inserted on a MIDI Track as the first plugin, any Fader currently controlling that Track will lock to its 'Out Hi' parameter. This allows the user to control the Volume of a MIDI only track.

<nowiki>*****</nowiki> the Key buttons have specific functionality for each Monomodular client. Generally, the first four control some aspect of the plugins operation, while the second four control the timing of the plugin. However, see the individual helpfile contained in the client to find out exactly what they do for each one. The Key buttons may be 'Locked', so that they are always accessible, by pressing the 'Lock' button (the top-center Function button when in Monomodular Mode).

phewww....I think that's about it.

Installation

2011-12-28T06:02:04Z

74.194.92.197:

Before installing Monomodular, make sure you have the most current versions of MaxMSP and Ableton Live installed on your computer. You will also need a license to use MaxforLive (although it is possible to use everything here in Demo Mode).

To install the entire Monomodular suite on OSX:

The installer is a single .amxd file, and can install all the necessary Monomodular files from within Live itself (the first m4l patch of its kind). The installer is able to place all the files in the Monodular package in their proper directories. It is also capable of downloading the most recent revision of the beta suite from SVN and installing it's tree to the correct directories (this is the recommended method).

The link to the Monodular installer file:

(placeholder)

You may also download the entire package (but it may not be as current):

(placeholder)

In order to use the installer, merely place it in Live's Library, under 'Presets/MIDI Effects/Max MIDI Effect/'. The easiest way to do this is to drag it from the Finder into Live's device browser.

Next, drag the 'Monomodular Installer" device from Live's device browser into a MIDI track.

If you plan on installing from SVN, click on the "Subversion" button. A dialog will appear asking you for a directory location so that the installer has a place to put the files its going to download from svn. You can either choose an existing directory or create a new one from the browser dialog.

The installer will now download all of the current files. The darwin's output will be displayed in the terminal window on the right as it makes progress. Any errors should show up there.

When it is finished, it is quite possible that everything is ready to go. The installer uses Live's log.txt file to try and decide where it should put the files it will install. However, if you have multiple Library's installed (which is a frequent occurence), it may get these locations wrong. No worries, the installer won't overwrite anything that is already on your computer, but it might get the locations wrong.

If you've already downloaded the package, just make sure to select it's location in the top path, next to the box that says 'Installation Package'. You can also drop the folder on that box.

Its a good idea to double check to make sure everything looks right. The proper locations should be as follows:

Installation package: this should point to the Monomodular files that are about to be installed. If you downloaded the current subversion revision, then the folder should automatically be chosen (it is the folder that you specified when you told the installer to download from svn). If you are installing from a downloaded package, just make sure this points to the folder containing the Monomodular package. If the package is in the same place as the installer, it should be automatically found.

Live.app: this is the Application bundle for Live. You can drag and drop Live's app onto the box to the right of the patch, or click on the path and choose it from the dialog. This should be the actual application, not the folder containing it.

MaxMSP Folder: this is the folder containing the MaxMSP application. It should be automatically chosen. If for some reason it wasn't, its possible that certain subfolders may be missing from it.

Live Library: this is the folder containing the MaxforLive patches in Live's current Library. It's generic location is '~/Library/Application Support/Ableton/Library', but it could be elsewhere if you've moved things around.

If all of the locations are valid installations, their paths should be colored white. Otherwise, they will be red and you need to choose them manually.

To install the files to the chosen locations, press the install button. The paths will be rechecked, and if valid, the installer will begin moving files. Progress is indicated by the bar on the bottom right.

After installation, it is necessary to restart Live in order for it to recognize the new Python files that were installed inside its application bundle.