Mobius Reference

January 2011


Contents

1Introduction
2Concepts
2.1    Display Names and Internal Names
2.2    Parameters
2.3    Controls
2.4    Variables
2.5    Modes
2.6    Functions
2.7    Function Quantization
2.8    Instant Functions
2.9    Modal Functions
2.10    Rounding Functions
2.11    Sustain Functions
2.12    Function Families
2.13    Mode Endings
2.14    Function Classes
2.14.1        Modal Edit Functions
2.14.2        Instant Edit Functions
2.14.3        Reset Functions
2.14.4        Instant Move Functions
2.14.5        Loop Switch Functions
2.14.6        Effect Functions
2.14.7        Mute Functions
2.14.8        Global Functions
3Major Modes
3.1    Confirm
3.2    Insert
3.3    Multiply
3.4    Mute
3.5    Overdub
3.6    Pause
3.7    Play
3.8    Record
3.9    Rehearse
3.10    Rehearse Record
3.11    Replace
3.12    Reset
3.13    Run
3.14    Solo
3.15    Solo Mute
3.16    Stutter
3.17    Substitute
3.18    Switch
3.19    Synchronize
3.20    Threshold
4Minor Modes
4.1    1/2 Speed
4.2    Capture
4.3    Master
4.4    MIDI Master
4.5    Mute
4.6    Overdub
4.7    Pitch
4.8    Rate
4.9    Reverse
4.10    Track Master
5Functions
5.1    Auto Record
5.2    Backward
5.3    Bounce
5.4    Checkpoint
5.5    Clear
5.6    Confirm
5.7    Divide
5.8    Focus Lock
5.9    Forward
5.10    Full Speed
5.11    Global Mute
5.12    Global Pause
5.13    Global Reset
5.14    Half Speed
5.15    Insert
5.16    Instant Multiply
5.17    Loop
5.18    Loop Copy
5.19    MIDI Out
5.20    MIDI Start
5.21    MIDI Stop
5.22    Move
5.23    Multiply
5.24    Mute
5.25    Mute MIDI Start
5.26    MuteOff
5.27    MuteOn
5.28    Mute Realign
5.29    Next Loop
5.30    Next Track
5.31    Overdub
5.32    OverdubOff
5.33    OverdubOn
5.34    Pause
5.35    Pitch Down
5.36    Pitch Next
5.37    Pitch Normal
5.38    Pitch Previous
5.39    Pitch Shift
5.40    Pitch Up
5.41    Play
5.42    Previous Loop
5.43    Previous Track
5.44    Rate Down
5.45    Rate Next
5.46    Rate Normal
5.47    Rate Previous
5.48    Rate Shift
5.49    Rate Up
5.50    Realign
5.51    Record
5.52    Redo
5.53    Rehearse
5.54    Replace
5.55    Reset
5.56    Retrigger
5.57    Retrigger Once
5.58    Reverse
5.59    Sample
5.60    Save Capture
5.61    Save Loop
5.62    Shuffle
5.63    Slip, Slip Backward, Slip Forward
5.64    Solo
5.65    Speed
5.66    Start Capture
5.67    Start Point
5.68    Stop Capture
5.69    Stutter
5.70    Substitute
5.71    Sustain Insert
5.72    Sustain Multiply
5.73    Sustain Mute
5.74    Sustain Mute Retrigger
5.75    Sustain Next Loop
5.76    Sustain Overdub
5.77    Sustain Pause
5.78    Sustain Previous Loop
5.79    Sustain Record
5.80    Sustain Replace
5.81    Sustain Reverse
5.82    Sustain Speed
5.83    Sustain Stutter
5.84    Sustain Substitute
5.85    Sustain Unrounded Insert
5.86    Sustain Unrounded Multiply
5.87    Sync Master Track
5.88    Sync Start Point
5.89    Time Copy
5.90    Track
5.91    Track Copy
5.92    Track Copy Timing
5.93    Track Group
5.94    Track Reset
5.95    Trim End
5.96    Trim Start
5.97    Undo
6User Interface Functions
6.1    UI Decrement Parameter
6.2    UI Increment Parameter
6.3    UI Next Parameter
6.4    UI Move Display Components
6.5    UI Previous Parameter
7Preset Parameters
7.1    Auto Record Bars
7.2    Auto Record Tempo
7.3    Bounce Quantize
7.4    Empty Loop Action
7.5    Empty Track Action
7.6    Enable Secondary Feedback
7.7    Loops Per Track
7.8    Maximum Redo
7.9    Maximum Tempo
7.10    Maximum Undo
7.11    Minimum Tempo
7.12    Multiply Mode
7.13    Mute Cancel
7.14    Mute Mode
7.15    Mute Sync Mode
7.16    No Feedback Undo
7.17    No Layer Flattening
7.18    Out Sync Realign Mode
7.19    Overdub Quantized
7.20    Overdub While Rounding
7.21    Overdub Transfer
7.22    Pitch Sequence
7.23    Pitch Shift Retrigger
7.24    Pitch Transfer
7.25    Quantize Mode
7.26    Rate Sequence
7.27    Rate Shift Retrigger
7.28    Rate Transfer
7.29    Realign Time
7.30    Record Beats/Bar
7.31    Record Resets Feedback
7.32    Record Speed Changes
7.33    Record Threshold
7.34    Record Transfer
7.35    Resize Sync Adjust
7.36    Return Location
7.37    Reverse Transfer
7.38    Shuffle Mode
7.39    Slip Mode
7.40    Slip Time
7.41    Sound Copy Mode
7.42    Speed Sync Adjust
7.43    Subcycles
7.44    Switch Duration
7.45    Switch Location
7.46    Switch Quantize
7.47    Switch Sync Adjust
7.48    Switch Velocity Sensitive
7.49    Sync Mode
7.50    Time Copy Mode
7.51    Track Sync Mode
8Track Parameters
8.1    Focus Lock
8.2    Group
8.3    Preset
8.4    Preset Number
9Track Controls
9.1    Feedback
9.2    Input Level
9.3    Output Level
9.4    Pan
9.5    Secondary Feedback
10Global Parameters
10.1    16 Bit Wave Files
10.2    Audio Input Device
10.3    Audio Output Device
10.4    Bindings
10.5    Confirmation Functions
10.6    Custom Message File
10.7    Drift Check Point
10.8    Drift Resync Frames
10.9    Dual Plugin Edit Window
10.10    Fade Frames
10.11    Focus Lock Functions
10.12    Groups Have Focus Lock
10.13    Host MIDI Status Export
10.14    Input Latency
10.15    Isolate Overdubs
10.16    Long Press Milliseconds
10.17    Max Loops Per Track
10.18    Message Duration
10.19    MIDI Input
10.20    MIDI Output
10.21    MIDI Record Pulsed
10.22    MIDI Status Export
10.23    MIDI Through
10.24    Modes Ignoring Secondary Feedback
10.25    Monitor Audio Input
10.26    Mute Cancel Functions
10.27    Noise Floor
10.28    Output Latency
10.29    Plugin MIDI Inputs
10.30    Plugin MIDI Outputs
10.31    Plugin MIDI Through
10.32    Plugin Ports
10.33    Quick Save File
10.34    Rate/Pitch Shift Range
10.35    Reduce Feedback During Overdub
10.36    Save Project Layers
10.37    Selected Track
10.38    Setup
10.39    Trace Debug Level
10.40    Trace Print Level
10.41    Track Groups
10.42    Tracks
11Menu Reference
11.1    File
11.1.1        Open Loop
11.1.2        Open Project
11.1.3        Save Loop
11.1.4        Save Project
11.1.5        Quick Save
11.1.6        Exit
11.2    Track Setups
11.3    Presets
11.4    Configuration
11.4.1        Presets
11.4.2        Track Setups
11.4.3        MIDI Control
11.4.4        Keyboard Control
11.4.5        Buttons
11.4.6        Plugin Parameters
11.4.7        Scripts
11.4.8        Samples
11.4.9        MIDI Devices
11.4.10        Audio Devices
11.4.11        Global Parameters
11.4.12        Display Components
11.4.13        Palette
11.5    Help Menu
11.5.1        Key Bindings
11.5.2        MIDI Bindings
11.5.3        Refresh UI
11.5.4        About

1 Introduction

In this manual we will provide complete but concise documentation for every mode, function, control, and parameter that exists in Mobius. This is intended for advanced users that are already somewhat familiar with what these items do, but may need clarification on how they behave and interact. If you are interested in tutorials that describe in detail how and why you might use these items, read the Mobius Techniques manual first. When an item in the reference manual has also been documented in any of the other manuals we will provide links to the other manuals. You can use the reference manual like an index to get a brief overview of a topic of interest, then follow links to more detailed documentation elsewhere.

Note that some of the items in the reference manual are accessible only in scripts so you will not see them in the binding windows or other parts of the user interface. We will provide brief script examples here, but for details on writing scripts read the Mobius Scripting manual.

The reference manual is not intended to be read from top to bottom. Most of the sections are arranged alphabetically to make it easier to locate something of interest. It is however recommended that you read the Concepts section first because these will clarify some of the terms used in this manual.

2 Concepts

Mobius has a lot of "things" in it that can be controlled by external triggers or used in scripts. In this introductory section we will review the major categories of things and define several important concepts that will be used throughout the reference manual.

It is recommended that you read this section completely before reading anything else in the reference manual.

2.1 Display Names and Internal Names

The various things you can see and use in Mobius will usually have both a "display name" and an "internal name". The display name is what you will see in the user interface and will be the title of the section in the reference manual that documents the thing. The internal name is the name you must use to refer to that thing in a script. Usually they are similar. If the display name contains spaces the spaces will be removed in the internal name. Display names always start with a capital letter, internal names for parameters always start with a lower case letter. A few internal names will use abbreviations or fewer words than the display name.

You don't need to care about internal names until you decide to write scripts.

For example, "Half Speed" is the display name for the function with the internal name "HalfSpeed" and "Switch Quantize" is the display name for the parameter with the internal name "switchQuantize".

2.2 Parameters

A parameter is named value that influences how Mobius behaves. There are three categories of parameters: global parameters, track parameters and preset parameters.

Global parameters control general operating characteristics such as whether input monitoring is enabled, or the amount of latency compensation. They are set in the Global Parameters popup window.

Track parameters control a few characteristics of each track such as the track name, group number, and input focus. These are relatively unusual and are used mostly in scripts. They are set in the Track Setups popup window.

Preset parameters control how functions behave, examples include Record Threshold, Quantize Mode, and Sync Mode. Most of the time when we talk about parameters we are talking about preset parameters. They are set in the Presets popup window.

Parameters have a type which determines how they are shown in the user interface and how they can be used in scripts.

Some parameters can be bound to triggers such as MIDI events but this is relatively unusual. More often parameters are set in scripts that are bound to MIDI triggers. If you do bind a MIDI trigger to a parameter, you should use a MIDI continuous controller. This is because unlike functions parameters have a ranged value and you need a trigger that can sweep over all the values in the range.

You cannot bind parameters of type String, those can only be changed from scripts. You can bind to parameters of type Integer though this is rarely useful. The integer range of a MIDI continuous controller is from 0 to 127, but it can be difficult to dial in an exact number. If you bind a non-ranged trigger such as a MIDI note to an integer parameter it will simply increment the current value by one each time it is triggered, wrapping back to zero when the maximum value is reached. Binding to parameters of type Enumeration is more useful, the 128 step range of a MIDI continuous controller is divided into regions for each value in the enumeration. For example the Shuffle Mode parameter has four possible values, so CC messages from 0 to 31 select the first value, CC messages from 32 to 63 select the second value and so on. If you bind a non-ranged trigger to an enumeration parameter it will cycle through the possible values. Binding to a parameter of type Boolean is similar to binding to an enumeration parameter. There are only two possible values, true and false, so a MIDI continuous controller will be divided into two regions and non-ranged triggers will simply toggle the value.

2.3 Controls

A control is a named value that controls how audio is recorded and played in a track. Controls are similar to track Parameters but their values are always integers and they have a larger range than most parameters. They are usually set by a MIDI device that sends continuous controller messages such as a rotating knob or a foot pedal.

There are five built-in controls:

The initial values for all track controls is set in the track setup . Controls may then be changed by binding them to triggers, or by turning knobs in the user interface.

2.4 Variables

A variable is similar to a parameter, it is a named value that holds information about the current Mobius state. Unlike parameters though, most variables cannot be changed. They can only be read in scripts and used to make decisions. Variables change as a side effect of normal Mobius operation. For example the variable loopFrame has the current record position in the current loop of the active track.

There are many variables, some are frequently used in scripts, others are esoteric and intended only for unit testing. Since variables can only be used in scripts they are documented in the Mobius Scripting manual.

2.5 Modes

A mode is a temporary state that a loop can be in. Modes have a name that will normally displayed in the center of the Mobius window. Modes are usually caused by the execution of a function but there are also a few system modes that are not associated with any particular function. There are two types of modes, major modes and minor modes.

A loop can only be in one major mode at a time. Examples of major modes are Reset, Record, Play and Multiply. When a function needs to change the major mode, the current mode must be ended before the new one begins. Ending a major mode can be a complex process that requires extra time, this may delay the change to the new mode. While a major mode is active, some functions may change their behavior.

A loop can be in any number of minor modes at the same time. Examples of minor modes include Reverse, 1/2 Speed, and Pitch. With a few exceptions minor modes do not alter the normal behavior of functions.

All major and minor modes are canceled when the loop is Reset

To understand what executing a function will do, you must therefore understand not only what Parameters will influence the function but also how the current modes will influence the function. In the user interface, the current major mode is displayed with the Mode Component and the active minor modes are displayed with the Minor Mode Component . It is recommended that you do not disable these components.

2.6 Functions

A function is a named action performed by Mobius at the request of the user. Examples include Record, Overdub, and Reset. Causing a function to be performed is called executing the function.

Functions are normally bound to a trigger that is a button of some kind such as a MIDI footswitch or a computer keyboard key. Functions do not have a numeric value so they are not normally bound to MIDI continuous control pedals, knobs, or faders. Some functions require that they be bound to a Sustainable Trigger that notifies Mobius both when the trigger is "pressed" and when it is "released". Typically this will be a MIDI Note message.

Functions operate in one of three ways: instant, sustain, and modal. Instant functions happen immediately. Sustain functions start when you press the trigger and end when you release the trigger. Modal functions start when you press the trigger the first time, and end when you press the trigger a second time.

2.7 Function Quantization

Quantization causes the execution of functions to happen at a precise time. When quantization is disabled functions are usually executed immediately. When quantization is enabled, the execution of the function will be delayed until the next quantization boundary. The three quantization boundaries are Loop, Cycle, and Subcycle. Quantization is frequently used to build loops that have a regular rhythmic quality.

You will see several phrases used in the documentation to describe the effects of quantization, such as "when quantizing", "during quantization", or "quantized function". All of these refer to the same concept.

For most functions quantization is controlled by the Quantize Mode parameter. For loop switch functions this is controlled by the Switch Quantize parameter. A few functions have their own dedicated quantization parameter.

The important thing to understand about quantization is that while we may say that a function happens "instantly" or that it "starts when you press a button", the actual execution of the function may happen sometime after you press a button if quantization is enabled. We will not usually say things like "function X starts when you press a button, or if quantization is enabled will be deferred until the next quantization point" as this gets tiresome to read (and write!) over and over. Instead you should assume that if a function obeys quantization that execution may be delayed even though we don't explicitly say it.

See Quantize Mode in the Getting Started With Mobius manual for more information.

2.8 Instant Functions

An instant function is one that does something to a loop or track and then stops. Note that when we say "instant" this does not necessarily means it will be executed immediately after it is triggered, the execution may be delayed if quantization is enabled. But when the function is eventually executed, what it does to the loop happens instantly. Some examples of this function type are Instant Multiply and Divide.

This is in contrast to Modal Functions where the function will have a start time and an end time and will have an effect on the loop over that span of time.

Since instant functions don't have a beginning or end, they will never be Sustain Functions.

2.9 Modal Functions

When some functions are executed they will continue to have an effect on the loop for a period of time. These are called modal functions. While the function is active the loop is said to be in the mode of that function. The name of the mode is usually but not always the same as the name of the function.

Both the beginning and ending of a modal function may be subject to quantization. A few functions will also do rounding which is similar to quantization but is not controlled by the Quantize Mode parameter.

Recall from the Modes section that a loop may be in only one major mode at a time but it may be in any number of minor modes at a time. Functions that change the major mode are major modal functions and functions that add or remove minor modes are minor modal functions. Examples of major modal functions are Record, Multiply, and Replace. Examples of minor modal functions are Reverse, Speed and Pitch Up.

The simplest way to start and end a major mode is to execute the function twice, the first execution starts the mode and the second ends it. But since there can be only one major mode active at a time, any major modal function will usually end the previous major modal function. Some minor modal functions will also end the current major mode, but others will let the current mode continue.

Minor modes are less consistent in how they start and end. Some belong to a function family that contain functions to toggle the mode, to force it on, to force it off, or to change characteristics of the mode rather than turn it off completely.

See Mode Endings for more details on ending modes.

2.10 Rounding Functions

The Multiply, Stutter and Insert functions all normally do rounding when their modes are ended. Rounding is similar to quantization, it defers the ending of a mode until a special time is reached. Unlike quantization, rounding is not influenced by the Quantize Mode parameter.

Rounding is done in order to preserve the current loop's cycle length. When you use functions that change the loop length, you usually want the new loop to be an exact multiple of the old loop's cycle length so that the new loop will play with the same tempo. When you end a rounding mode, an event will be scheduled to end the mode far enough in the future so that the cycle length will be preserved.

Rounding functions can also be ended immediately instead of waiting to preserve the cycle length. When this happens the cycle length of the loop will be recalculated and the new loop will contain only one cycle. If this loop is the MIDI Sync Master this may change the tempo of the generated MIDI clocks.

2.11 Sustain Functions

A Sustain Function is always a modal function that begins when you press a sustainable trigger and ends when you release the trigger. The most common sustainable trigger is a MIDI Note message, though MIDI Continuous Control messages and computer keyboard keys may also be used.

The function generally behaves the same as the non-sustain function with the same name, the main difference is how the ending is triggered. Sustain functions are usually ended when the trigger is released. If you execute another major modal function while a sustainable trigger is held down, the sustained mode is ended and the up transition of the sustainable trigger will be ignored.

Note that the ending of a sustain function is still subject to quantization. So if you quickly tap a sustain function trigger when quantization is enabled, the start of the mode will be delayed until the next quantization point and the end of the mode will be delayed until the quantization point after the point where the mode starts. For example if you are in a loop with the Subcycles parameter set to 4 and are currently in the middle of subcycle 1 then quickly tap the button for Speed you will enter 1/2 Speed mode at the beginning of subcycle 2 and end the mode at the beginning of subcycle 3.

2.12 Function Families

Some related functions may be grouped into families. These are usually minor modal functions where each function in the family can change characteristics of mode rather than simply ending it. One example is the Rate Shift function family which includes the functions Rate Up, Rate Down, Rate Normal and others.

2.13 Mode Endings

The simplest way to end a major modal function is to execute the same function again. But since there can be only one major mode active at a time, any major modal function will usually end the previous major modal function. For example if you are in Record mode you aren't required to trigger the Record function again to end it, you could trigger Overdub instead which will automatically end the Record mode and start Overdub mode.

If the current mode does rounding, the ending function will normally be delayed until the rounding period ends. If you execute more functions during the rounding period they will be "stacked" and all execute at the end of the rounding period.

Some functions may change their behavior during certain modes. Rather than simply executing after the current mode ends, they may change the way the mode is ended or even leave the current mode active. This is called modal behavior and is similar to what the EDP calls an "alternate ending".

The most common example of a modal behavior is the Record function when it is used during a rounding mode such as Multiply or Insert. When Record is executed in these modes, it will cancel the rounding period and end the mode immediately. The new loop will then return to Play or Overdub mode. When a function has modal behavior, it will be included in the documentation for that function, for the mode in which it is used, and for the function that started the mode.

Minor modal functions are not ended by other functions and they do not change the behavior of other functions. To end a minor mode you usually trigger the same function again or in some cases you trigger a function from the same Function Family. For example the function Rate Up will increase the playback rate by one semitone. Executing Rate Up again will not end the rate shift mode, it will increase the playback rate by another semitone. To return the rate to normal you must use either the Rate Down function or the Rate Normal function.

2.14 Function Classes

We can divide functions in to several classes. These classes are mostly just to help document the functions by showing those that have similar behavior. You don't need to know about function classes except for one special case: the Mute Cancel parameter.

2.14.1 Modal Edit Functions

The functions in this class all cause Mobius to enter a major mode which causes the function to execute over a span of time. Here you will find the two most common functions, Record and Overdub. All but one modal edit function has both a sustain and a non-sustain version. They are called "edit" functions because they can change the loop in some way.

2.14.2 Instant Edit Functions

The functions in this class all cause Mobius to modify the loop instantly, though some may be delayed due to quantization. They are "edit" functions because they all change the loop in some way and result in the generation of a new layer.

2.14.3 Reset Functions

The functions in this class cause loops to be reset and all their content discarded. In a way they are similar to Instant Edit Functions except they do not create new layers.

2.14.4 Instant Move Functions

The functions in this class happen instantly and cause Mobius to change the playback position of the loop. They do not modify the loops or layers.

2.14.5 Loop Switch Functions

The functions in this class select the loop within a track to play. Usually this is a different loop than the one currently playing but some simply retrigger the current loop. This class of function is very important because most of them have loop switch behavior which can be quite complex.

2.14.6 Effect Functions

The functions in this class apply a temporary non-destructive effect to the loop. These functions will not generate a new layer unless they are used in combination with another editing function.

2.14.7 Mute Functions

The functions in this class all perform some form of mute, temporarily silencing the loop. They are similar to Effect Functions in that they are temporary and non-destructive. But it is important that they have their own class because it is used to define the behavior of the Mute Cancel Functions parameter.

2.14.8 Global Functions

The functions on this class do not operate directly on loops. Instead they operate on tracks or the entire collection of tracks.

3 Major Modes

3.1 Confirm

Confirm mode is active while you are in the confirmation period of a loop switch. This happens when you have the Switch Quantize parameter set to Confirm, Confirm Subcycle, Confirm Cycle, or Confirm Loop.

While you are in the confirmation period you may "stack" functions to be executed after the switch. When you are ready to do the switch you must use a confirmation function such as Confirm or any other function defined in the Confirmation Functions parameter. By default, the Undo function will also operate as a switch confirmation function.

The loop is not being modified while in Confirm mode, though if Feedback is reduced the loop is allowed to decay.

See Loop Switching in the Mobius Techniques manual for more information on loop switching and using switch quantization.

3.2 Insert

Insert mode is active while you are executing the Insert, Sustain Insert, or Sustain Unrounded Insert functions. During Insert mode new empty space is being added to the loop and any sound being received by the track is overdubbed into that space.

Insert is a rounding mode unless it was started by the Sustain Unrounded Insert function. During Insert mode, the Record function will cancel the rounding period and end the insert immediately.

3.3 Multiply

Insert mode is active while you are executing the Multiply, Sustain Multiply, or Sustain Unrounded Multiply functions. During Multiply mode new space may be added to the loop by copying the original cycle and appending it to the end. Sound being received by the track will be merged with the current content of the loop in the same way as Overdub mode.

Multiply is a rounding mode unless it was started by the Sustain Unrounded Multiply function. During Multiply mode, the Record function will cancel the rounding period and end the multiply immediately.

3.4 Mute

Mute mode is unusual because it may be displayed as both a major and a minor mode. When the Mute minor mode is active, and no other major mode is active besides Play, we will display Mute as the major mode to make it easier to see. When the Mute minor mode is active, the loop will continue to advance but no sound will be sent out of the track.

Mute mode is toggled by the Mute and Global Mute functions. Sustain Mute and Sustain Mute Retrigger will force mute on when the function trigger is pressed and force it off when the trigger is released. Mute Realign and Mute MIDI Start will force mute on, then automatically turn it off when certain synchronization points are reached.

When you execute a function that wants to change the major mode, the loop may still remain muted during the new mode. Whether the mute continues or is canceled is determined by the Mute Cancel and Mute Cancel Functions parameters. If the mute is not canceled then the major mode will change and the loop may be modified, but it will still continue to be silent. You will continue to see Mute appear as a minor mode. This technique can be used to modify loops while the audience can't hear them creating a surprise when the loop is unmuted.

3.5 Overdub

Overdub mode is unusual because it may be displayed as both a major and a minor mode. When the Overdub minor mode is active and no other major mode is active besides Play, we will display Overdub as the major mode to make it easier to see.

When Overdub is the major mode any sound being received by the track will be merged with the current content of the loop. When Overdub is a minor mode but is not displayed as the major mode, overdubbing is suspended and will resume when the current major mode ends. Leaving overdub suspended is a useful technique to create "seamless" recordings when changing from one mode to another. For example, if overdub is on and the major mode is Replace, when leaving Replace mode we will immediately enable Overdub mode and can avoid a fade out of the end of the replaced section.

Overdub mode is toggled by the Overdub function. The Sustain Overdub function will force overdub on when the trigger is pressed and off when it is released.

3.6 Pause

Pause mode is active while you are executing the Pause or Global Pause functions. During Pause mode the loop freezes and does not advance. No would will be sent out from the track.

Pause mode is canceled by any major modal function.

3.7 Play

Play mode is the default system mode that is active when the loop is not empty and is not in any other major mode. During Play mode the loop will advance and the sound in the loop will be sent to the output device assigned to this track.

3.8 Record

Record mode is active while you are executing the Record, Auto Record, or Sustain Record functions. During Record mode, a new initial loop is being created and no sound will be sent out of the track.

3.9 Rehearse

Rehearse mode is active while you are executing the Rehearse function and you are in the rehearse phase, listening to what was just recorded. Rehearse is an unusual function because sets two major modes, Rehearse and Rehearse Record.

Rehearse mode is a special form of Play mode, you will hear the loop that was just recorded but if you let the loop play to the end you will return to Rehearse Record mode.

3.10 Rehearse Record

Rehearse Record mode is active while you are executing the Rehearse function and you are in the record phase, recording a new loop. Rehearse is an unusual function because sets two major modes, Rehearse and Rehearse Record.

Rehearse Record mode is a special form of Record mode, you are recording a new loop and no sound will be sent out of the track. Once you end the recording you will enter Rehearse mode where you can review what you just recorded and decide whether to keep it or make another recording.

3.11 Replace

Replace mode is active while you are executing the Replace or Sustain Replace functions. During Replace mode the current content of the loop is removed and replace with the sound being received by the track.

3.12 Reset

Reset mode is a default system mode that will be active whenever the loop is empty. All loops will be in Reset mode when Mobius is started for the first time. Loops may also be placed in Reset mode after loading a project that does not contain audio content for every loop. Once a loop has content, you can make it empty by executing the Reset, Track Reset, or Global Reset functions.

3.13 Run

Run mode is an internal system mode that you normally will never see. It is involved with latency compensation and usually lasts such a brief period of time that it won't be seen in the user interface. The loop is not being changed during Run mode, though it may be playing.

3.14 Solo

Solo mode is activated by the Solo function. The loop that is in Solo mode will be heard playing, but the loops in all other tracks will be muted. The other tracks will be in Solo Mute mode.

3.15 Solo Mute

Solo Mute mode is activated by the Solo function. The active loop in the active track will enter Solo mode and all other tracks will enter Solo Mute mode. While a track is in Solo Mute mode, no sound will be sent out from the track.

3.16 Stutter

Stutter mode is active when you are executing the Stutter or Sustain Stutter functions. During Stutter mode the loop is being extended by copying the contents previous cycle and inserting it after the end of that cycle. After a cycle has been inserted, sound being received by the track will be merged with content of the new cycle in the same way as Overdub mode.

3.17 Substitute

Substitute mode is active while you are executing the Substitute or Sustain Substitute functions. During Substitute mode the current content of the loop may be completely or partially removed and merged with the sound being received by the track.

3.18 Switch

Switch mode is active whenever you have used Next Loop or any of the other loop switching functions and the Switch Quantize parameter is set to something other than Off. The switch is being delayed until a quantization point. During Switch mode you can "stack" functions to be executed after the switch.

3.19 Synchronize

Synchronize mode is active when you have executed a Record, Auto Record, or Sustain Record function, and the loop is waiting for a synchronization pulse to begin recording. This can happen when Sync Mode or Track Sync Mode are set to something other than Off. During Synchronize mode the loop is not changing or playing.

3.20 Threshold

Threshold mode is active when you have executed a Record, Auto Record, or Sustain Record function, and the loop is waiting for an audio signal to be received by the track whose average volume exceeds a threshold. This happens when the Record Threshold parameter is set to a value greater than zero. During Threshold mode the loop is not changing or playing.

4 Minor Modes

4.1 1/2 Speed

1/2 Speed mode is active after executing the Speed or Half Speed functions. During 1/2 Speed mode the loop will playback at half the normal rate. 1/2 Speed is similar to the Rate mode but they operate independently. 1/2 Speed mode is ended by executing the Speed function again or by executing the Full Speed function.

4.2 Capture

Capture mode is active after executing the Start Capture function. While Capture mode is active, all audio being received by and sent from the tracks is captured and may be saved to a file. Capture mode is ended by the Stop Capture or Save Capture functions.

4.3 Master

Master mode is active after a loop has been recorded and the track containing it becomes both the MIDI Sync Master and the Track Sync Master track. When a track is the MIDI Sync Master it will send MIDI clocks to the configured output device at a tempo calculated from the loop length. When a track is the Track Sync Master other tracks will synchronize the start and end of the Record function to quantization points in the master track.

4.4 MIDI Master

MIDI Master mode is active after a loop has been recorded and the track containing the MIDI Sync Master track. When a track is the MIDI Sync Master it will send MIDI clocks to the configured output device at a tempo calculated from the loop length.

4.5 Mute

Mute mode is active after executing the Mute, Global Mute, Mute Realign, Mute MIDI Start, Sustain Mute, or Sustain Mute Retrigger functions. During Mute mode the loop will continue to advance but no sound will be sent out of the track.

Mute mode is unusual because it is both a major and a minor mode. When the Mute minor mode is active and no other major mode is active besides Play, we will display Mute as the major mode.

When you execute a function that wants to change the major mode, the loop may still remain muted during the new mode. Whether the mute continues or is canceled is determined by the Mute Cancel and Mute Cancel Functions parameters. If the mute is not canceled then the major mode will change and the loop may be modified, but it will still continue to be silent. You will continue to see Mute appear as a minor mode. This technique can be used to modify loops while the audience can't hear them creating a surprise when the loop is unmuted.

4.6 Overdub

Overdub mode is active after executing the Overdub or Sustain Overdub functions. During Overdub mode any sound being received by the track will be merged with the current content of the loop.

Overdub mode is unusual because it is both a major and a minor mode. When the Overdub minor mode is active and no other major mode is active besides Play, we will display Overdub as the major mode to make it easier to see.

4.7 Pitch

Pitch mode is active after executing Rate Shift or most of the other functions in the Pitch Shift function family. It indicates that the output of the loop is being passed through a pitch shifting effect. In the user interface the mode will be qualified with a positive or negative number to indicate the degree and direction of the shift. For example "Pitch 5" and "Pitch -7".

4.8 Rate

Rate mode is active after executing Rate Shift or most of the other functions in the Rate Shift function family. It indicates that the playback and record rate of the loop is being adjusted. The audible effect is that the loop changes pitch but also speeds up or slows down. In the user interface the mode will be qualified with a positive or negative number to indicate the degree and direction of the shift. For example "Rate 5" and "Rate -7".

4.9 Reverse

Reverse mode is active whenever the loop is playing backward from the end to the beginning. It may be activated by the Reverse or Backward functions.

4.10 Track Master

Track Master mode is active after a loop has been recorded and the track containing it becomes the Track Sync Master track. When a track is the Track Sync Master other tracks will synchronize the start and end of the Record function to quantization points in the master track.

5 Functions

5.1 Auto Record

Internal name: AutoRecord

Auto Record starts a loop recording that ends by itself automatically after a configured number of bars. The length of the recording is determined by the Sync Mode, Record Beats/Bar, Auto Record Bars, and Auto Record Tempo parameters. This is a modal function that sets the major mode to Record while it is active. Unlike most modal functions you do not have to execute another function to end Record mode, it will end by itself when the calculated number of bars has been recorded.

The function is not sensitive to the Quantize Mode parameter, it will cancel all major modes and execute immediately. Unlike Record this function does not cancel rounding modes.

The function is sensitive to the Record Threshold parameter which will defer the start of the recording until a loud enough signal is received. While waiting for a proper threshold the loop will be in Threshold mode.

If the Sync Mode parameter is set to MIDI Beat, MIDI Bar, Host Beat, or Host Bar, executing this function may enter Synchronize mode temporarily waiting for the next sync pulse.

To calculate the loop length the Record Beats/Bar parameter is multiplied by the Auto Record Bars parameter to get to the total number of beats to record. This is then combined with a tempo which determines the amount of time in each beat. How the tempo is determined depends on the Sync Mode parameter. When Sync Mode is MIDI Beat or MIDI Bar the tempo is calculated from incoming MIDI clock messages. When Sync Mode is Host Beat or Host Bar the tempo is given to the plugin by the host application. When Sync Mode is Out, Out Manual Start or Off and this track is not using Track Sync Mode to slave to another track, then the tempo is determined by the Auto Record Tempo parameter.

If the current track was recorded with Track Sync Mode then a tempo is not used to calculate the loop length. Instead the total number of beats from Record Beats/Bar and Auto Record Bars is multiplied by the length of the subcycle in the master track.

See Record in the Mobius Techniques manual for more information.

5.2 Backward

Internal name: Backward

Backward forces the loop direction into reverse and sets the Reverse minor mode. Unlike the Reverse function this does not toggle Reverse mode, if you are already in reverse the function has no effect.

This function will obey the Quantize Mode parameter.

Changing direction will end most major modes, see the documentation for Reverse for a full list. This function has no effect on minor modes besides Reverse.

See Changing Direction in the Mobius Techniques manual for more information.

5.3 Bounce

Internal name: Bounce

Bounce is used to merge the contents of one or more tracks and save the result to another track. This is similar to "bouncing" in traditional recording systems. Bounce is really just a special form of Capture. If the Capture minor mode is not active, Bounce behaves the same as Start Capture, it will begin mixing the output of all unmuted tracks and storing it in a temporary capture area. When the Bounce function is used during Capture mode it end Capture mode and stores the captured audio in an empty track loop. After creating the new loop all tracks that were unmuted at the time of the bounce will be muted, this mute is not quantized.

The bounced recording will be placed in the first track from the left that has an empty loop selected. If there are no tracks with an empty loop the bounce is discarded. This function does not obey the Quantize Mode parameter but it will obey the Bounce Quantize parameter. This may delay the start and end of the bounce if the active loop in the active track has content. If the active loop in the active track is empty then Bounce Quantize is ignored.

Bounce will not end any major modes in progress when the capture starts but muting the source tracks when the capture ends will cancel all major modes.

See Bounce Recording in the Mobius Techniques manual for more information.

5.4 Checkpoint

Internal name: Checkpoint

Checkpoint creates a new layer checkpoint and collapses the display of layers between the new checkpoint and the last checkpoint. When you use the Undo and Redo functions to move between layers, they will skip over any layers between two checkpoints.

If you use Checkpoint on a layer that is already a checkpoint, the checkpoint is removed and all the layers between they current layer and the previous checkpoint are restored.

This function is not considered to be a loop editing function, it is not quantized and will not end any major or minor modes.

See Managing Layers in the Mobius Techniques manual for more information.

5.5 Clear

Internal name: Clear

Clear erases the current contents of the loop, leaving a silent loop the same size as the original. A new layer is created so you can use Undo to return to the original loop.

See Reset, Empty, Clear, and Silent for a discussion about the difference between these similar terms.

This function is not quantized. It is considered an instant edit function so it will end the following modes.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See Replace in the Mobius Techniques manual for more information about techniques to replace parts of a loop.

5.6 Confirm

Internal name: Confirm

This function can be used to confirm a loop switch during Confirm and Switch modes. When the Switch Quantize parameter is set to one of the confirmation modes, this function will end the confirmation period and start the switch quantization period. If the loop is in the switch confirmation period it will cause the switch to happen immediately.

This function has no other purpose outside of Confirm and Switch modes. The EDP does not have this function, instead the Undo function has this behavior during the switch quantization period. This function is provided as an alternative in case you would Undo to behave normally and remove stacked functions during Confirm mode.

5.7 Divide

Internal names: Divide, Divide2, Divide3, Divide4

The Divide functions cause an immediate reduction in the loop size. The amount of the reduction is determined by the divisor which is the number in the name of the function. Divide 2 will divide the loop length in half, Divide 3 will divide the loop length by 3, and Divide 4 will divide the loop length by 4.

The division functions are similar to the Instant Multiply functions except they work in the other direction, cutting the loop into smaller pieces then selecting one of those pieces. The division happens immediately and a new layer is created with the shorter loop. You can use Undo to return to the original loop.

The new loop will contain the portion of the original loop that you were in at the time the function was executed. For example if a loop is 4 seconds long and you execute Divide 2 while the current loop location is at the end of second 1, the new loop will contain seconds 1 and 2 of the original loop. If instead you execute Divide 2 when the current loop location is at the end of second 3, the new loop will contain seconds 3 and 4 of the original loop.

The function named just Divide without a number is accessible only scripts. With this function the divisor is specified as an argument written after the function name. See Divide in the Mobius Scripting manual for usage examples.

This function is not quantized. It is considered an instant edit function so it will end the following modes.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See Shorting The Loop in the Mobius Techniques manual for more information.

5.8 Focus Lock

Internal name: FocusLock

Focus Lock toggles the focus lock track parameter.

This function has no effect on the loop, it simply changes the way future functions will behave. It is not quantized and does not have any effect on major or minor modes.

See Focus Lock in the Exploring Mobius manual for more information.

5.9 Forward

Internal name: Forward

Forward forces the loop into the normal forward direction. If the loop is already playing forward the function has no effect. Forward is a minor modal function in the Reverse function family that will end Reverse mode.

This function will obey the Quantize Mode parameter.

Changing direction will end most major modes, see the documentation for Reverse for a full list.

See Changing Direction in the Mobius Techniques manual for more information.

5.10 Full Speed

Internal name: FullSpeed

Full Speed forces the loop out of 1/2 Speed mode. If the loop is not in 1/2 Speed mode, the function will have no effect. Note that this function does not cancel a Rate Shift if one is also in effect. Rate Shift and Half Speed operate independently and can be combined.

This function will obey the Quantize Mode parameter.

This function will not cancel most major modes. You may continue modifying the loop while the rate is changing. See the Speed function for more information on how this function interacts with the major and minor modes.

See Rate Shift in the Mobius Techniques manual for more information.

5.11 Global Mute

Internal name: GlobalMute

Global Mute mutes all tracks that are currently playing, but does not unmute any tracks that are currently muted. If you use Global Mute again, it will unmute only those tracks that were originally playing when Global Mute was executed the first time.

Global Mute sets a special Global Mute major mode that all tracks will have. If you execute any function besides Global Mute while the tracks are in Global Mute mode, the mode is canceled and you will not be able to automatically restore the previous track mute states.

This function will obey the Quantize Mode parameter in the active track and will end the major modes in all tracks.

See Mute, Pause, and Solo in the Mobius Techniques manual for more information.

5.12 Global Pause

Internal name: GlobalPause

Global Pause will pause all tracks that are currently playing, but will not unpause any tracks that are currently paused. If you use Global Pause a second time, it will unpause only those tracks that were previously playing. Note that this is different than simply toggling the current pause state in all tracks.

Global Pause sets a special Global Pause major mode that all tracks will have. If you execute any function besides Global Pause while the tracks are in Global Pause mode, the mode is canceled and you will not be able to automatically restore the previous track pause states.

This function will obey the Quantize Mode parameter in the active track and will end the major modes in all tracks.

See Mute, Pause, and Solo in the Mobius Techniques manual for more information.

5.13 Global Reset

Internal name: GlobalReset

Global Reset performs the Track Reset function in all tracks, restores the settings from the current track setup to all tracks, cancels running scripts, resets global variables, and does other internal housekeeping to return Mobius to the state it has when it is first started.

This function does not obey the Quantize Mode parameter and will cancel all major and minor modes in all tracks.

See Reset in the Mobius Techniques manual for more information.

5.14 Half Speed

Internal name: HalfSpeed

Half Speed forces the loop into 1/2 Speed mode. If the loop is already in 1/2 Speed mode the function has no effect. Note that this function does not cancel a Rate Shift if one is also in effect. Rate Shift and Half Speed operate independently and can be combined.

This function will obey the Quantize Mode parameter.

This function will not cancel most major modes. You may continue modifying the loop while the rate is changing. See the Speed function for more information on how this function interacts with the major and minor modes.

See Rate Shift in the Mobius Techniques manual for more information.

5.15 Insert

Internal name: Insert

Insert inserts new clear space into a loop and allows you to overdub into the new space. This is a major modal function that sets the mode to Insert while it is active. Insert is a rounding mode that will preserve the loop's cycle length unless you force rounding off.

The Record function has modal behavior during Insert mode. It will cause an immediate termination of the insert without rounding and return the loop to Play or Overdub mode. This is called an "unrounded insert".

This function will obey the Quantize Mode parameter.

This function will end the following major modes.

This function is ignored in Reset, Threshold and Synchronize modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function changes behavior in Confirm and Switch modes. It will "stack" and be executed after the loop switch where it will perform a Time Copy from the current loop into the next loop.

See Extending The Loop With Insert in the Mobius Techniques manual for more information.

5.16 Instant Multiply

Internal names: InstantMultply, InstantMultiply2, InstantMultiply3, InstantMultiply4

Performs an immediate extension of the loop. This differs from the Multiply function in that the loop is not extended over time. The current loop is simply copied, then those copies are appended some number of times. The number of cycles will be multiplied by the same amount but the cycle length remains the same.

The amount the loop is extended is determined by the multiplier which is the number in the function name. Instant Multiply 2 will double the loop length, Instant Multiply 3 will triple the loop length, and Instant Multiply 4 will quadruple the loop length. The extension happens immediately and a new layer is created to hold the longer loop. You can use Undo to return to the original loop.

The function with internal name InstantMultiply without a number may only be used in scripts. The multiplier is specified as an argument to the function. See InstantMultiply in the Mobius Scripting manual for usage examples.

These functions are not quantized. They are considered to be instant edit functions so they will end the following modes.

This function is ignored in Reset, Threshold and Synchronize modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See Extending The Loop With Multiply in the Mobius Techniques manual for more information.

5.17 Loop

Internal names: Loop, Loop1, Loop2, Loop3,..., Loop8

The Loop family of functions switch directly to a numbered loop. If the track is already playing this loop the effect will be the same as the Retrigger function.

Since these are loop switch functions many options are available to control when the switch happens, and what happens after the switch. The following parameters may all influence the loop switch:

The timing of this function is controlled by the Switch Quantize parameter.

Using the numbered loop functions with Switch Duration set to Once, Switch Location set to Start, and Switch Velocity Sensitive set to true will make Mobius behave like a simple sample player.

The function named just Loop without a number is accessible only in scripts. With this function the loop you want to trigger is specified as a function argument. See Loop in the Mobius Scripting manual for usage examples.

These functions will end the following major modes.

These functions will cancel Threshold and Synchronize modes. If there is a pending recording in the current loop it will not be carried over to the next loop.

These functions will change the number of the next loop during Confirm and Switch modes.

These functions may end Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

See Loop Switching in the Mobius Techniques manual for more information.

5.18 Loop Copy

Internal name: LoopCopy

Loop Copy will copy the contents of the previously active loop into the currently active loop.

5.19 MIDI Out

Internal name: MidiOut

MIDIOut can send any MIDI message to the configured MIDI output device. This function is accessible only from scripts.

See MidiOut in the Mobius Scripting manual for more information.

This function does not change the current loop and has no effect on major or minor modes.

5.20 MIDI Start

Internal name: MidiStart

MIDI Start waits for the loop start point, then sends a MIDI Start message to the configured MIDI output device. See also Mute MIDI Start which will first mute the loop.

This function must be used to start the generation of MIDI clocks when Sync Mode is set to Out Manual Start. It is also useful to bring the Mobius loop and an external drum machine or pattern sequencer back into alignment after clocks have been started.

This is not a modal function, instead it schedules an event that will be executed at the loop start point. You can use the Undo function to cancel this event. Aside from the event it does not change the loop and has no effect on major or minor modes.

See Sync Mode = Out Manual Start and Realign Alternatives - MIDI Start and Mute MIDI Start in the Mobius Synchronization manual for examples of how to use MIDI Start

5.21 MIDI Stop

Internal name: MidiStop

MIDI Stop sends a MIDI Stop message immediately to the configured MIDI output devices. MIDI clocks will continue to be generated so that slaves devices can continue tracking the master clock tempo. This is typically used to temporarily stop a drum machine or pattern sequencer that is slaving to Mobius MIDI clocks. Use MIDI Start to restart the slave devices.

See Sending MIDI Messages in the Mobius Techniques manual for more information.

This function does not change the loop and has no effect on major or minor modes.

5.22 Move

Internal name: Move

Move will instantly move the loop playback position to a new location. This function is not quantized and is accessible only from scripts.

See Move in the Mobius Scripting manual for usage examples.

This function will end the following major modes and may be delayed due to rounding.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

5.23 Multiply

Internal name: Multiply

Multiply is a complex function that can be used to both make the loop longer and shorter. It is influenced by the Multiply Mode parameter. Multiply is a major modal function that sets the mode to Multiply while it is active. Multiply is a rounding mode that will preserve the loop's cycle length unless you force rounding off.

After a loop has been recorded and still has only one cycle, Multiply will make the loop larger by appending copies of the original for as long as multiply mode is active. Once a loop has more than one cycle, Multiply can both extend the loop and resize it to make it smaller.

The Record function has modal behavior during Multiply mode. It will cause an immediate termination of the multiply without rounding and return the loop to Play or Overdub mode. This is called an "unrounded multiply".

This function will obey the Quantize Mode parameter.

This function will end the following major modes.

This function is ignored in Reset, Threshold and Synchronize modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function changes behavior in Confirm and Switch modes. It will "stack" and be executed after the loop switch where it will perform a Loop Copy from the current loop into the next loop.

See Extending The Loop With Multiply and Shortening The Loop in the Mobius Techniques manual for more information.

5.24 Mute

Internal name: Mute

Mute will silence the loop. Mute is a minor modal function that will toggle Mute mode. During mute mode the loop will continue to play, you will see loop meter advancing in the user interface, but no sound will be sent out from that track.

There are several options for what happens when you exit mute mode, these are defined by the Mute Mode parameter.

You usually end mute mode by executing the Mute function again, but you can also cancel mute mode automatically when other functions are executed. The Mute Cancel preset parameter and Mute Cancel Functions global parameter control which functions will cancel mute mode.

When the track being muted is the MIDI Master Sync track, there are several options for what happens to the MIDI clocks being generated. This is controlled by the Mute Sync Mode parameter.

Mute is an unusual mode because while it is primarily a minor mode, it will also be displayed as a major mode if there are no other major modes active. If Mute minor mode is active and the loop enters the Play major mode, the major mode is set to Mute instead.

This function will obey the Quantize Mode parameter.

This function will end the following major modes and may be delayed due to rounding.

This function is ignored in these modes.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See also Pause, MuteOn, and MuteOff

See Mute, Pause, and Solo in the Mobius Techniques manual for more information.

5.25 Mute MIDI Start

Internal name: MuteMidiStart

Mute MIDI Start will first execute the Mute function, then it waits for the loop start point. At the loop start point it will send a MIDI Start message to the configured MIDI output device, then cancel Mute mode.

This function is similar to MIDI Start which does not mute the track before waiting for the start point.

Since this is a form of the Mute function it will cancel most major modes. See Mute for details. Unlike Mute, this function is not quantized, the mute will always begin immediately unless it is being delayed due to rounding.

After the mute, an event is scheduled for the loop start point to send the MIDI message. Undo can be used to cancel this event.

See Sync Mode = Out Manual Start and Realign Alternatives - MIDI Start and Mute MIDI Start in the Mobius Synchronization manual for examples of how to use MIDI Start

5.26 MuteOff

Internal name: MuteOff

MuteOff will cancel the Mute minor mode. If the loop is not in mute mode the function has no effect. This function is not quantized and is accessible only in scripts.

See MuteOff in the Mobius Scripting manual for usage examples.

The Mute Mode parameter determines what will happen when Mute mode is canceled.

5.27 MuteOn

Internal name: MuteOn

MuteOn will activate the Mute minor mode and immediately silence the loop. If the loop is already muted the function has no effect. This function is not quantized and is accessible only in scripts.

See MuteOn in the Mobius Scripting manual for usage examples.

Starting Mute mode will cancel most other major modes, see the Mute function for more information.

5.28 Mute Realign

Internal name: MuteRealign

Mute Realign is the same as the Realign function except that it first activates the Mute minor mode and silences the loop. Note that unlike the Mute function, Mute Realign is not quantized, the mute will always begin immediately.

When the realign point is reached Mute mode is canceled and the loop is restarted from the beginning. Mute Mode is not used.

Starting Mute mode will cancel most other major modes, see the Mute function for more information.

See Realign in the Mobius Synchronization manual for more information.

5.29 Next Loop

Internal name: NextLoop

Next Loop will switch to the loop whose number is one greater than the number of the current loop. If the current loop is the last one in the track, Next Loop will switch to the first loop.

Since this is a loop switch function many options are available to control when the switch happens, and what happens after the switch. The following parameters may all influence the loop switch:

This function will end the following major modes.

This function will cancel Threshold and Synchronize modes. If there is a pending recording in the current loop it will not be carried over to the next loop.

This function will change the number of the next loop during Confirm and Switch modes.

This function may end Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

See Loop Switching in the Mobius Techniques manual for more information.

5.30 Next Track

Internal name: NextTrack

Next Track will active the track whose number is one greater than the number of the current track. If the last track is active, Next Track will activate the first track.

If the next track is empty, the Empty Track Action parameter determines what actions will be taken.

Changing the track may cancel recording modes in the current track. See Track for details.

See also Previous Track.

See Track Sync in the Mobius Synchronization manual for more information on using Empty Track Action.

5.31 Overdub

Internal name: Overdub

Overdub will toggle the Overdub minor mode. If the current major mode is Play then Overdub will also become the major mode. While Overdub is the major mode, sound being received by the track will be combined with the current loop content creating a new layer with both the old and new sounds.

This function may obey the Quantize Mode parameter, but only if the Overdub Quantized parameter is checked.

Overdub will not cancel any major modes except Mute and Mute depending on the values of Mute Cancel and Mute Cancel Functions.

Overdub is an unusual mode because while it is primarily a minor mode, it will also become the major mode if no other major modes override it. If you execute another major modal function, the Overdub major mode will be canceled and overdubbing into the loop will stop. But the Overdub minor mode will still be active. When the current major mode ends and returns the loop to Play mode, if the Overdub minor mode is still active, then Overdub will once again become the major mode and overdubbing into the loop will be resumed.

See also OverdubOff and OverdubOn

See Overdub in the Mobius Techniques manual for more information.

5.32 OverdubOff

Internal name: OverdubOff

OverdubOff forces the Overdub minor mode off. If Overdub is also the major mode, the loop will return to Play mode. If Overdub mode is already off the function will have no effect. This function is not quantized and is accessible only in scripts.

See OverdubOff in the Mobius Scripting manual for usage examples.

See Overdub for more information on how the Overdub minor and major modes interact.

5.33 OverdubOn

Internal name: OverdubOn

OverdubOn activates the Overdub minor mode. If overdub mode is already active the function has no effect. If the current major mode is Play then Overdub also becomes the major mode and overdubbing will begin. This function is not quantized and is accessible only in scripts.

See OverdubOn in the Mobius Scripting manual for usage examples.

See Overdub for more information on how the Overdub minor and major modes interact.

5.34 Pause

Internal name: Pause

Pause is a special form of Mute that will both mute the track and also freeze the active loop's playback position. You will see the loop meter in the user interface stop advancing. When pause mode is canceled the loop begins playing from its previous location. The effect is similar to pressing the pause button on an audio recorder.

Unlike Mute, Pause is always a major modal function that will cancel the current mode and activate Pause mode. You usually end pause mode by executing the Pause function again, but you can also cancel pause mode by executing any other major modal function. Note that the Mute Cancel preset parameter does not apply to the Pause function.

This behavior is also available with the Mute function when you set Mute Mode to Pause.

When the track being paused is the MIDI Master Sync track, there are several options for what happens to the MIDI clocks being generated. This is controlled by the Mute Sync Mode parameter.

See Mute, Pause, and Solo in the Mobius Techniques manual for more information.

5.35 Pitch Down

Internal name: PitchDown

Pitch Down decreases the pitch of the loop by one semitone.

If the amount of pitch shift becomes non-zero, then the Pitch minor mode will become active and displayed in the user interface. If the pitch shift becomes zero (normal) then Pitch mode is canceled.

The pitch functions will obey the Quantize Mode parameter.

The pitch functions will not cancel any other major or minor modes.

See Pitch Shift in the Mobius Techniques manual for more information.

5.36 Pitch Next

Internal name: PitchNext

Pitch Next sets the loop to the next pitch in the Pitch Sequence and increments the sequence position. If you are currently at the end of the sequence, the first pitch in the sequence is chosen. See the Pitch Sequence parameter for more information on defining a pitch sequence.

If the amount of pitch shift becomes non-zero, then the Pitch minor mode will become active and displayed in the user interface. If the pitch shift becomes zero (normal) then Pitch mode is canceled.

The pitch functions will obey the Quantize Mode parameter.

The pitch functions will not cancel any other major or minor modes.

See Pitch Shift in the Mobius Techniques manual for more information.

5.37 Pitch Normal

Internal name: PitchNormal

Pitch Normal cancels the Pitch minor mode and removes any pitch shifting being applied to a loop.

The pitch functions will obey the Quantize Mode parameter.

The pitch functions will not cancel any other major or minor modes.

See Pitch Shift in the Mobius Techniques manual for more information.

Return the pitch to normal.

5.38 Pitch Previous

Internal name: PitchPrevious

Pitch Previous sets the loop to the previous pitch in the Pitch Sequence and decrements the sequence position. If you are currently at the first pitch in the sequence, the last pitch in the sequence is chosen. See the Pitch Sequence parameter for more information on defining a pitch sequence.

If the amount of pitch shift becomes non-zero, then the Pitch minor mode will become active and displayed in the user interface. If the pitch shift becomes zero (normal) then Pitch mode is canceled.

The pitch functions will obey the Quantize Mode parameter.

The pitch functions will not cancel any other major or minor modes.

See Pitch Shift in the Mobius Techniques manual for more information.

5.39 Pitch Shift

Internal name: PitchShift

Pitch Shift can change the pitch of the loop up or down by any number of semitones. It is a ranged function which means that it must be bound to a trigger that supports a continuous range of values such as MIDI notes or MIDI continuous controllers. It is almost always bound to a MIDI note from a keyboard so you can adjust pitch shift chromatically by playing the keyboard normally.

The value of the note in the binding becomes the center point of the shift range. If you press this note the pitch returns to normal. If you press notes on either side of the center note, the pitch will be raised or lowered by the corresponding number of semitones. The range of notes that will cause a pitch shift is determined by the Rate/Pitch Shift Range global parameter.

If the amount of pitch shift becomes non-zero, then the Pitch minor mode will become active and displayed in the user interface. If the pitch shift becomes zero (normal) then Pitch mode is canceled.

The pitch functions will obey the Quantize Mode parameter.

The pitch functions will not cancel any other major or minor modes.

Pitch Shift may also be used in scripts but it is not ranged. Instead the amount of shift is specified as an argument to the function. See PitchShift in the Mobius Scripting manual for usage examples.

See Pitch Shift in the Mobius Techniques manual for more information.

5.40 Pitch Up

Internal name: PitchUp

Pitch Up increases the pitch of the loop by one semitone.

If the amount of pitch shift becomes non-zero, then the Pitch minor mode will become active and displayed in the user interface. If the pitch shift becomes zero (normal) then Pitch mode is canceled.

The pitch functions will obey the Quantize Mode parameter.

The pitch functions will not cancel any other major or minor modes.

See Pitch Shift in the Mobius Techniques manual for more information.

5.41 Play

Internal name: Play

Play will end the current major mode and return to the loop to the default Play mode. If the loop is currently in Reset or Play mode the function is ignored. You can think of Play as a universal mode cancel function. It will get you out of modes like Insert, Multiply, Rehearse, Replace, Substitute, Overdub, and Mute and return to Play mode without having to remember to press right button for the current mode.

Play does not however cancel most minor modes. like Reverse or 1/2 Speed. Play will cancel the Overdub and Mute minor modes.

This function will end the following major modes and may be delayed due to rounding.

This function is ignored in these modes.

See Play in the Mobius Techniques manual for more information.

5.42 Previous Loop

Internal name: PrevLoop

Previous Loop will switch to the loop whose number is one less than the number of the current loop. If the current loop is the first one in the track, Previous Loop will switch to the last loop.

Since this is a loop switch function many options are available to control when the switch happens, and what happens after the switch. The following parameters may all influence the loop switch:

This function will end the following major modes.

This function will cancel Threshold and Synchronize modes. If there is a pending recording in the current loop it will not be carried over to the next loop.

This function will change the number of the next loop during Confirm and Switch modes.

This function may end Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

See Loop Switching in the Mobius Techniques manual for more information.

5.43 Previous Track

Internal name: PrevTrack

Previous Track will active the track whose number is one less than the number of the current track. If the first track is active, Previous Track will activate the last track.

If the previous track is empty, the Empty Track Action parameter determines what actions will be taken.

Changing tracks may cancel recording modes in the current track. See Track for details.

See also Next Track.

See Track Sync in the Mobius Synchronization manual for more information on using Empty Track Action.

5.44 Rate Down

Internal name: RateDown

Rate Down decreases the playback rate by an amount that will sound like a one semitone drop in pitch.

If the amount of rate shift becomes non-zero, then the Rate minor mode will become active and displayed in the user interface. If the rate shift becomes zero (normal) then Rate mode is canceled.

The rate functions will obey the Quantize Mode parameter.

The rate functions will not effect any other major or minor modes. Note that Rate mode is independent of 1/2 Speed mode.

See Rate Shift in the Mobius Techniques manual for more information.

5.45 Rate Next

Internal name: RateNext

Rate Next sets the loop to the next playback rate in the Rate Sequence and increments the sequence position. If you are currently at the end of the sequence, the first rate in the sequence is chosen. See the Rate Sequence parameter for more information on defining a rate sequence.

If the amount of rate shift becomes non-zero, then the Rate minor mode will become active and displayed in the user interface. If the rate shift becomes zero (normal) then Rate mode is canceled.

The rate functions will obey the Quantize Mode parameter.

The rate functions will not effect any other major or minor modes. Note that Rate mode is independent of 1/2 Speed mode.

See Rate Shift in the Mobius Techniques manual for more information.

5.46 Rate Normal

Internal name: RateNormal

Rate Normal cancels the Rate minor mode and removes any rate shift currently being applied to the loop. Note that this does not cancel 1/2 Speed mode that would be set by the Half Speed or Speed functions.

The rate functions will obey the Quantize Mode parameter.

The rate functions will not effect any other major or minor modes. Note that Rate mode is independent of 1/2 Speed mode.

See Rate Shift in the Mobius Techniques manual for more information.

5.47 Rate Previous

Internal name: RatePrevious

Rate Previous sets the loop to the previous playback rate in the Rate Sequence and decrements the sequence position. If you are currently at the beginning of the sequence, the last rate in the sequence is chosen. See the Rate Sequence parameter for more information on defining a rate sequence.

If the amount of rate shift becomes non-zero, then the Rate minor mode will become active and displayed in the user interface. If the rate shift becomes zero (normal) then Rate mode is canceled.

The rate functions will obey the Quantize Mode parameter.

The rate functions will not effect any other major or minor modes. Note that Rate mode is independent of 1/2 Speed mode.

See Rate Shift in the Mobius Techniques manual for more information.

5.48 Rate Shift

Internal name: RateShift

Rate Shift can change the playback rate of the loop up or down to achieve a pitch change in any number of semitones. It is a ranged function which means that it must be bound to a trigger that supports a continuous range of values such as MIDI notes or MIDI continuous controllers. It is almost always bound to a MIDI note from a keyboard so you can adjust rate shift chromatically by playing the keyboard normally.

The value of the note in the binding becomes the center point of the shift range. If you press this note the rate returns to normal. If you press notes on either side of the center note, the rate will be raised or lowered by the corresponding number of semitones. The range of notes that will cause a rate shift is determined by the Rate/Pitch Shift Range global parameter.

If the amount of rate shift becomes non-zero, then the Rate minor mode will become active and displayed in the user interface. If the rate shift becomes zero (normal) then Rate mode is canceled.

The rate functions will obey the Quantize Mode parameter.

The rate functions will not effect any other major or minor modes. Note that Rate mode is independent of 1/2 Speed mode.

Rate Shift may also be used in scripts but it is not ranged. Instead the amount of shift is specified as an argument to the function. See RateShift in the Mobius Scripting manual for usage examples.

See Rate Shift in the Mobius Techniques manual for more information.

5.49 Rate Up

Internal name: RateUp

Rate Up Increase the playback rate by an amount that will sound like a one semitone rise in pitch.

If the amount of rate shift becomes non-zero, then the Rate minor mode will become active and displayed in the user interface. If the rate shift becomes zero (normal) then Rate mode is canceled.

The rate functions will obey the Quantize Mode parameter.

The rate functions will not effect any other major or minor modes. Note that Rate mode is independent of 1/2 Speed mode.

See Rate Shift in the Mobius Techniques manual for more information.

5.50 Realign

Internal name: Realign

Realign will bring the Mobius loop back into alignment with the external loop. For all sync modes except MIDI Master Sync, realign will move the Mobius loop playback position so that it aligns with the external loop. For MIDI Master Sync the realign behavior is determined by the Out Sync Realign Mode parameter. When the realign adjustment happens is controlled by the Realign Time parameter.

This function is not quantized. This function is not modal, it will schedule an event for the desired realign time. The realign event may be canceled with Undo.

This function will end the following major modes and may be subject to rounding.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See The External Loop in the Mobius Synchronization manual for more information on what "external start point" means.

See Realign in the Mobius Synchronization manual for more information on the Realign function.

5.51 Record

Internal name: Record

Record begins and ends a new loop recording. This is a major modal function that will toggle Record mode. Usually Record mode is ended by executing the Record function a second time, though most other functions will also end the recording. Record will cancel all major and minor modes and throw away the layer history.

The Record Threshold parameter can be used to delay the start of the recording until an audio signal of sufficient loudness is received.

The Record Speed Changes parameter determines whether rate shifting functions such as Rate Shift and Speed will end the recording, or whether the shifting alters how the recording is made.

The Record Resets Feedback parameter can be used to reset the feedback control to the level specified in the track setup whenever a recording is started.

During all rounding modes (Multiply, Insert, Stutter) the Record function has special modal behavior. Instead of canceling the mode and starting a new recording it will instead cancel the rounding period and end the current mode immediately. The loop will then return to either Play or Overdub modes.

See Record in the Mobius Techniques manual for more information.

5.52 Redo

Internal name: Redo

Redo moves the loop to the next layer on the redo list. If the redo list is empty, this function will have no effect. In order to have layers on the redo list, you must use the Undo function one or more times, and you must have the Maximum Redo parameter set to a number greater than zero.

If the loop is the MIDI Sync Master, changing layers may require adjustments to the generated MIDI clocks if the cycle size in the new layer is different that the current cycle size. This is controlled by the Resize Sync Adjust parameter.

This function will end all of the following editing modes.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See Managing Layers in the Mobius Techniques manual for more information.

5.53 Rehearse

Internal name: Rehearse

Rehearse begins and ends a special recording mode where you can listen what you recorded then decide if you want to keep it or try another recording.

When you execute Rehearse the first time it begins recording a new loop just like the Record function except that the major mode is set to Rehearse Record. When you execute Rehearse a second time it ends the recording and begins playing it. The major mode is set to Rehearse. While you are in Rehearse mode you are reviewing the loop to determine if you want to keep it. If you let the new loop play to the end, the mode will automatically change back to Rehearse Record and you can record a different loop. When you have recorded a loop that you want to keep, execute the Play or Undo functions to cancel Rehearse mode and return to Play mode.

See Rehearse in the Mobius Techniques manual for more information.

5.54 Replace

Internal name: Replace

Replace allows you to replace a section of a loop with new sounds, in a way similar to what traditional recording systems call "punch in". Replace is a major modal function that will toggle Replace mode. During Replace mode, the current content of the loop is erased and the sound coming into the track is saved in this empty space. You usually cancel Replace mode by executing the Replace function a second time, but all other major modal functions will also cancel the replace.

During Replace mode the loop is muted so the current contents of the loop being replaced will not be heard. This is the only difference between Replace and Substitute which may let you hear the current loop contents.

This function obeys the Quantize Mode parameter.

This function will end all of the following editing modes.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See also Substitute.

See Replacing Loop Content in the Mobius Techniques manual for more information.

5.55 Reset

Internal name: Reset

Reset deletes all layers in the current loop and makes it "empty". Reset does not create a new layer and cannot be reverted with Undo.

See Reset, Empty, Clear, and Silent for a discussion about the difference between these similar terms.

This function is not quantized and all major and minor modes will be canceled. Track parameters will be restored to the values specified in the track setup .

See Reset in the Mobius Techniques manual for more information.

5.56 Retrigger

Internal name: Retrigger

Retrigger will restart the loop over from the beginning. It is a loop switch function so it will obey the Switch Quantize parameter which controls when the retrigger will happen. The Switch Velocity Sensitive parameter can be used to adjust the output level.

Unlike most loop switch functions, Retrigger ignores the Switch Location, Switch Duration, and Return Location parameters because the loop is not being changed, it is just moving the playback position of the loop.

See also Retrigger Once which will retrigger and also automatically mute the loop after it plays to the end.

This function will end the following major modes.

This function will cancel Threshold and Synchronize modes.

This function will be ignored during Confirm and Switch modes.

This function may end Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

See Loop Switching in the Mobius Techniques manual for more information.

5.57 Retrigger Once

Internal name: RetriggerOnce

Retrigger Once will restart the loop over from the beginning, let it play to the end, and then automatically execute the Mute function. Retrigger Once is a loop switch function so it will obey the Switch Quantize parameter which controls when the retrigger will happen. The Switch Velocity Sensitive parameter can be used to adjust the output level.

Unlike most loop switch functions, Retrigger ignores the Switch Location, Switch Duration, and Return Location parameters because the loop is not being changed, it is just moving the playback position of the loop.

See also Retrigger.

This function will end the following major modes.

This function will cancel Threshold and Synchronize modes.

This function will be ignored during Confirm and Switch modes.

This function may end Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

See Loop Switching in the Mobius Techniques manual for more information.

5.58 Reverse

Internal name: Reverse

Reverse toggles the Reverse minor mode, which changes the playback direction of the loop. While Reverse mode is active the loop will play from the end to the beginning, in the user interface you will see the loop meter moving from the right to the left. Reverse mode is canceled by executing the Reverse function a second time or by executing the Forward function.

This function will obey the Quantize Mode parameter.

The functions that change direction will end the following major modes.

This function may be used in Reset, Threshold and Synchronize modes to toggle playback direction before a recording starts.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See also Backward and Forward.

See Changing Direction in the Mobius Techniques manual for more information.

5.59 Sample

Internal names: Sample, Sample1 through Sample8

The Sample family of functions will play one of the loaded samples. When triggered, a sample plays from beginning to end without interruption and then stops. If you trigger it again before the last sample playback finishes, another overlapping playback of the sample will start. Samples are not part of a loop or track, it is like having a very primitive built-in sample player. The sample functions are not quantized.

The function named just Sample without a number may only be used in scripts. The sample to trigger is specified as a function argument that may be a number or an expression. See Sample in the Mobius Scripting manual for usage examples.

The sample functions are not quantized and they have no effect on major or minor modes. If a loop is in one of the following recording modes, the sample will be recorded into the loop as it plays.

See Samples in the Exploring Mobius manual for more information.

5.60 Save Capture

Internal name: SaveCapture

Save Capture will save the audio captured by the internal performance recorder to a file. You must first have started the performance recorder with the Start Capture or Bounce functions.

The recording will be saved in a file whose name begins with "capture" followed by an automatically generated number to make the name unique. The files will be saved in the directory specified in the Quick Save File parameter.

This function is not quantized and it has no effect on the current loop.

See Capturing a Performance in the Mobius Techniques manual for more information.

5.61 Save Loop

Internal name: SaveLoop

Save Loop will perform a "quick save" of the active loop in the active track. This is the same as the "Quick Save" item from the "File" menu.

The loop will be saved in a file whose name begins with the value of the Quick Save File parameter followed by an automatically generated number to make the name unique.

This function is not quantized and has no effect on the active loop. If the loop is being modified, the layer being played is saved, not the new layer being created.

See Quick Save in the Exploring Mobius manual for more information.

5.62 Shuffle

Internal name: Shuffle

Shuffle will instantly cut the loop into several slices then reorder the slices. A new layer is created so you can Undo to return to the original loop. The number of slices the loop is cut into is determined by the Subcycles parameter. The new ordering of the slices is determined by the Shuffle Mode parameter.

When used in scripts, Shuffle is much more powerful. Script expressions can be used to define complex patterns of slices. See Shuffle in the Mobius Scripting manual for usage examples.

This function will obey the Quantize Mode parameter. It is considered an instant edit function so it will end the following modes.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See Shuffle in the Mobius Techniques manual for more information on using the basic Shuffle function.

5.63 Slip, Slip Backward, Slip Forward

Internal names: Slip, SlipBackward, SlipForward

The Slip family of functions will instantly move the loop playback position forward or backward by a fixed amount. Slip Forward Slip Backward can be bound to function triggers, Slip can only be used in scripts. The effect is similar to the Move function but more limited. The amount of slippage is determined the parameters Slip Mode and Slip Time.

This function will obey the Quantize Mode parameter. It is considered an instant edit function so it will end the following modes.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

The function named just Slip can only be used in scripts where the amount of slippage is specified as a function argument. See Slip in the Mobius Reference manual for usage examples.

See Changing Playback Position in the Mobius Techniques manual for more information.

5.64 Solo

Internal name: Solo

Solo mutes all tracks that are currently playing except for the active track. The active track enters the Solo major mode and all other tracks enter the Solo Mute major mode. When solo mode is canceled, all the muted tracks that were playing at the time of the Solo are unmuted, but tracks that were muted at the time of the Solo are left muted.

Solo mode is canceled if you execute the Solo function a second time, or you execute any of the mute cancel functions. The set of functions that cancel mute is defined by the Mute Cancel and Mute Cancel Functions parameters.

See Mute, Pause, and Solo in the Mobius Techniques manual for more information.

5.65 Speed

Internal name: Speed

Speed toggles 1/2 Speed minor mode. While 1/2 Speed mode is active, a rate shift will be applied to the loop to make it play at half the normal speed. The loop will sound one octave lower than normal, and will take twice as long to play from start to finish. If you are already in 1/2 Speed mode, the mode is canceled and the loop speed is doubled.

Note that this function does not cancel the Rate minor mode if that is also in effect. Rate shift and halfspeed modes operate independently and can be combined.

This function will obey the Quantize Mode parameter.

This function will not cancel most major modes. You may continue modifying the loop while the rate is changing.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See also Full Speed and Half Speed.

See Rate Shifting in the Mobius Techniques manual for more information.

5.66 Start Capture

Internal name: StartCapture

Start Capture starts an internal performance recorder that captures all audio being sent to the audio output device. This can be used to create a single audio file containing a looping performance as it happened in real-time. Once you have captured some amount of audio, you can use the Stop Capture function to stop capturing and the Save Capture function to save the last capture to a file.

Though capture can be used by anyone, it was designed for testing Mobius so the user interface is crude and you need to be careful with it. The captured audio accumulates in memory and is not written to a file until you call Save Capture. If you let capture run for a long period of time without saving you can run out of memory.

This function is not quantized and it has no effect on the active loop.

See Capturing a Performance in the Mobius Techniques manual for more information.

5.67 Start Point

Internal name: StartPoint

Start Point instantly restructures the loop so that the current loop position becomes the start point. You can think of it like having the loop content before the current playback position sliced off, and then appended to the end.

Start Point is not quantized.

This function is considered to be an instant edit function so it will end the following modes.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See Changing the Start Point in the Mobius Techniques manual for more information.

5.68 Stop Capture

Internal name: StopCapture

Stop Capture turns off the internal performance recorder. The last captured performance is held in memory until you execute Save Capture. If you execute Start Capture or Bounce without saving, the previous capture will be discarded and the memory freed.

This function is not quantized and has no effect on the active loop.

See Capturing a Performance in the Mobius Techniques manual for more information.

5.69 Stutter

Internal name: Stutter

Stutter is a variation of the Multiply function that will extend the loop by inserting copies of the current cycle. When Stutter is executed for the first time the major mode Stutter is activated and the cycle the loop playback position is currently in becomes the stutter cycle. While Stutter mode is active, each time the playback position reaches the end of a cycle, another copy of the stutter cycle is inserted. While this is happening the sound being received by the track will be merged with the stutter cycles as it is during Overdub mode.

Stutter mode is canceled when the Stutter function is executed a second time, or when any other major modal function is executed.

This function will obey the Quantize Mode parameter.

This function will end the following major modes.

This function is ignored in Reset, Threshold and Synchronize modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function changes behavior in Confirm and Switch modes. It will "stack" and be executed after the loop switch where it will perform a Loop Copy from the current loop into the next loop.

See Extending The Loop With Multiply in the Mobius Techniques manual for more information.

5.70 Substitute

Internal name: Substitute

Substitute allows you to replace a section of a loop with new sounds, in a way similar to what traditional recording systems call "punch in". This is a major modal function that toggles Substitute mode. Substitute is very similar to the Replace function but it gives you more control over how new sound is combined with the current contents of the loop.

Substitute differs from Replace in two ways. First, during Substitute mode you will continue to hear the contents of the loop that you are replacing. During Replace mode the current loop contents are always muted. Second, Replace will always completely replace the current contents of the loop, Substitute allows you to blend the new sounds with the old sounds by adjusting the Secondary Feedback control.

To use Substitute with Secondary Feedback you must check the Enable Secondary Feedback parameter. When Secondary Feedback is all the way up, then Substitute behaves like Overdub. When Secondary Feedback is all the way down, Substitute behaves like Replace. If you bind the Secondary Feedback control to a MIDI continuous controller, you can sweep secondary feedback up and down during the substitute to "sculpt" the loop.

This function obeys the Quantize Mode parameter.

This function will end all of the following editing modes.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See Replacing Loop Content in the Mobius Techniques manual for more information.

5.71 Sustain Insert

Internal name: SUSInsert

Sustain Insert is the same as the Insert function except that the request to end Insert mode is made when the sustainable function trigger is released.

See Sustain Functions for more information on how sustain functions behave.

See Insert for more information on insert mode.

5.72 Sustain Multiply

Internal name: SUSMultiply

Sustain Multiply is the same as the Multiply function except that the request to end Multiply mode is made when the sustainable function trigger is released.

See Sustain Functions for more information on how sustain functions behave.

See Multiply for more information on multiply mode.

5.73 Sustain Mute

Internal name: SUSMute

Sustain Mute is the same as the Mute function except that the request to end Mute mode is made when the sustainable function trigger is released.

See Sustain Functions for more information on how sustain functions behave.

See Mute for more information on mute mode.

5.74 Sustain Mute Retrigger

Internal name: SUSMuteRetrigger

Sustain Mute Retrigger is similar to a combination of the Mute function and the Retrigger function. When the function trigger is pressed the loop is forced into the Mute major mode. When the function trigger is released Mute mode is canceled and the loop is retriggered to play from the beginning.

Note that this function does not use the Mute Mode parameter to determine where to start the unmuted loop, the loop is always restarted from the beginning.

This function will obey the Quantize Mode parameter.

See Sustain Functions for more information on how sustain functions behave.

While this is similar to the Retrigger function, Sustain Mute Retrigger is not considered to be a loop switch function so it will not obey the Switch Quantize parameter or any of the other parameters that influence how loop switching behaves.

5.75 Sustain Next Loop

Internal name: SUSNextLoop

Sustain Next Loop is similar to the Next Loop function except that when the sustainable function trigger is released we will return to the original loop.

See Next Loop for more information on loop switching, the parameters that influence this function, and how this function effects the major and minor modes.

See Sustain Functions for more information on how sustain functions behave.

5.76 Sustain Overdub

Internal name: SUSOverdub

Sustain Overdub is similar to the Overdub function except that Overdub mode is toggled when you both press and release a sustainable function trigger. Note that this does not necessarily mean that Overdub mode begins when press the trigger. If you are already in Overdub mode, then the Sustain Overdub function will turn off Overdub mode when the trigger is pressed then turn it back on when the trigger is released.

This function may obey the Quantize Mode parameter but only if the Overdub Quantized parameter is checked.

See Sustain Functions for more information on how sustain functions behave.

See Overdub for more information on overdub mode, and how this function interacts with other major and minor modes.

5.77 Sustain Pause

Internal name: SUSPause

Sustain Pause is the same as the Pause function except that the request to end Pause mode is made when the sustainable function trigger is released.

See Sustain Functions for more information on how sustain functions behave.

See Pause for more information on pause mode.

5.78 Sustain Previous Loop

Internal name: SUSPrevLoop

Sustain Previous Loop is similar to the Previous Loop function except that when the sustainable function trigger is released we will return to the original loop.

See Next Loop for more information on loop switching, the parameters that influence this function, and how this function effects the major and minor modes.

See Sustain Functions for more information on how sustain functions behave.

5.79 Sustain Record

Internal name: SUSRecord

Sustain Record is similar to the Record function except that Record mode will end immediately after the sustainable function trigger is released. This is a useful function if you want to make very short loops, where pressing a trigger twice to start and end the recording would take too long.

The Record Threshold parameter can be used to delay the start of the recording until an audio signal of sufficient loudness is received.

The Record Speed Changes parameter determines whether rate shifting functions such as Rate Shift and Speed will end the recording, or whether the shifting alters how the recording is made.

The Record Resets Feedback parameter can be used to reset the feedback control to the level specified in the track setup whenever a recording is started.

Note that unlike Record, this function will not have special modal behavior during rounding modes. The current mode is always canceled, the layers are freed, and a new recording is begun.

See Sustain Functions for more information on how sustain functions behave.

5.80 Sustain Replace

Internal name: SUSReplace

Sustain Replace is the same as the Replace function except that Replace mode will end immediately after the sustainable function trigger is released.

See Sustain Functions for more information on how sustain functions behave.

5.81 Sustain Reverse

Internal name: SUSReverse

Sustain Reverse toggles the Reverse minor mode when the function trigger is pressed and again when it is released. Both the start and end may be quantized. Note that this does not mean that you will always go into Reverse mode when the function trigger is pressed. If you are already in Reverse mode, you will return to a normal forward direction when the trigger is pressed and return to Reverse mode when the trigger is released.

See Reverse for more information on changing direction, and how this function will interact with the current major and minor modes.

See Sustain Functions for more information on how sustain functions behave.

5.82 Sustain Speed

Internal name: SUSSpeed

Sustain Speed toggles the 1/2 Speed minor mode when the function trigger is pressed and again when it is released. Both the start and end may be quantized. Note that this does not mean that you will always go into 1/2 Speed mode when the function trigger is pressed. If you are already in 1/2 Speed mode, 1/2 Speed will be canceled when the trigger is pressed and then resumed when the trigger is released.

See Speed for more information on 1/2 Speed mode.

See Sustain Functions for more information on how sustain functions behave.

5.83 Sustain Stutter

Internal name: SUSStutter

Sustain Replace is the same as the Stutter function except that Stutter mode will end immediately after the sustainable function trigger is released.

See Sustain Functions for more information on how sustain functions behave.

5.84 Sustain Substitute

Internal name: SUSSubstitute

Sustain Substitute is the same as the Substitute function except that Substitute mode will end immediately after the sustainable function trigger is released.

See Sustain Functions for more information on how sustain functions behave.

5.85 Sustain Unrounded Insert

Internal name: SUSUnroundedInsert

Sustain Unrounded Insert is the same as the Sustain Insert function except that the ending of Insert mode will not be rounded. Recall that rounding is similar to quantization, it will delay the ending of modes that add new space to a loop until the space added is an even multiple of the cycle length. This keeps the loop content at a consistent tempo. Sustain Unrounded Insert will not do rounding so you can insert space of any size. This is typically used when you are creating "glitchy" or non-rhythmic loops.

Note that while rounding is not performed the start and end of the Insert mode may be quantized. If Quantize Mode is set to Subcycle for example, a quick tap of the Sustain Unrounded Insert button will insert exactly one subcycle at the next subcycle boundary.

See Sustain Functions for more information on how sustain functions behave.

See Insert for more information on insert mode, and how this function interacts with the current major and minor modes.

5.86 Sustain Unrounded Multiply

Internal name: SUSUnroundedMultiply

Sustain Unrounded Multiply is a variant of the Multiply function that can be used to cut a section of any size out of the loop. Multiply mode is activated when the function trigger is pressed, and it is canceled when the function trigger is released. When Multiply mode ends a new layer is created containing only the loop content between the start and end of the mode. Both the beginning and ending of the multiply may be quantized but the end will not be rounded.

Recall that rounding is similar to quantization, it will delay the ending of modes that add or remove loop space until the space added or removed is an even multiple of the cycle length. This keeps the loop content at a consistent tempo. Sustain Unrounded Multiply will not do rounding so you can cut out space of any size. This is typically used when you are creating "glitchy" or non-rhythmic loops, or you want to cut out a rhythmic section of a non-rhythmic loop.

See Sustain Functions for more information on how sustain functions behave.

See Multiply for more information on multiply mode, and how this function interacts with the current major and minor modes.

5.87 Sync Master Track

Internal name: SyncMasterTrack

Sync Master Track will change the track that is considered to be the track sync master to the active track. If the active track is already the track sync master the function has no effect.

This function is not quantized and host no effect on the active loop.

See Track Sync in the Mobius Synchronization manual for more information.

5.88 Sync Start Point

Internal name: SyncStartPoint

Sync Start Point will wait until the next external start point, then perform the Start Point function to align the loop start point with the external start point. This is only relevant when using MIDI Slave Sync or Host Slave Sync. It is ignored for other sync modes.

This function is not quantized.

This function is considered to be an instant edit function so it will end the following modes.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See The External Loop in the Mobius Synchronization manual for more information on what "external start point" means.

See Sync Start Point in the Mobius Synchronization manual for more information on how Sync Start Point is used.

5.89 Time Copy

Internal name: TimeCopy

5.90 Track

Internal names: Track, Track1 through Track8

The Track family of functions will activate one of the numbered tracks. If the track is already active, the function will have no effect. If the new track is empty, the Empty Track Action parameter determines what actions will be taken.

The track select functions are not quantized.

The function named just Track can only be used in scripts where the track to select is specified as a function argument. See Track in the Mobius Reference manual for usage examples.

Changing the selected track will cancel the following recording modes in the current track.

This function will not cancel Mute and Pause modes in the current track.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See Track Sync in the Mobius Synchronization manual for more information on using Empty Track Action.

5.91 Track Copy

Internal name: TrackCopy

Track Copy will copy the loop content from the active loop in the track to the left of the active track into the active loop of the active track. If the active loop in the active track is not empty, its contents will be lost and replaced with the copy. If the source loop is empty, the destination loop will also become empty. If the active track is track number 1, the copy is taken from the highest numbered track.

The effect is similar to selecting an empty track when Empty Track Action is set to Copy except the track doesn't have to be empty.

This function cancels all major and minor modes in the current loop.

See Track Sync in the Mobius Synchronization manual for more information on creating synchronized tracks.

5.92 Track Copy Timing

Internal name: TrackCopyTiming

Track Copy Timing will create an clear loop in the active track that is the same length as the active loop in the track to the immediate left of the active track. If the active loop in the active track is not empty its contents will be lost and replaced with the copy. If the source loop is empty, then the destination loop will also become empty. If the active track is track number 1, the copy is taken from the highest numbered track.

The effect is similar to selecting an empty track when Empty Track Action is set to Copy Timing except the track doesn't have to be empty.

This function cancels all major and minor modes in the current loop.

See Track Sync in the Mobius Synchronization manual for more information on creating synchronized tracks.

5.93 Track Group

Internal name: TrackGroup

Track Group will set the Group track parameter. Each time the Track Group function is executed the track is assigned to the next track group. If the track is already in the highest track group, the group assignment is removed. So you may need to execute Track Group several times in order to select the group you want, or track the track out of all groups.

Groups are identified by capital letters beginning with 'A'. The maximum number of track groups is set by the Track Groups global parameter which defaults to 2. So assuming this default the group assignment pattern when executing the Track Group function would be:


   none -> Group A -> Group B -> none -> Group A -> Group B -> ...

Track groups are primarily useful when creating complex function bindings that target only the tracks in a group. They can also be used in scripts to identify sets of tracks the script should operate on.

This function is not quantized and has no effect on the active loop.

See Binding Scopes and Track Groups in the Exploring Mobius manual for more information on using track groups in bindings.

5.94 Track Reset

Internal name: TrackReset

Track Reset will execute Reset function for every loop in the track. All of the track parameters and controls will then be reset to the values defined in the current track setup .

Prior to version 1.43 this was called General Reset.

See Track Setups in the Exploring Mobius manual for more information on how to define track setups.

5.95 Trim End

Internal name: TrimEnd

Trim End removes the content of the loop from the current playback position to the end. This is similar to doing an unrounded multiply to the end, but it requires only one button press and it happens immediately.

This function will obey the Quantize Mode parameter.

This function is considered to be an instant edit function so it will end the following modes.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See Shortening The Loop in the Mobius Techniques manual for more information.

5.96 Trim Start

Internal name: TrimStart

Trim Start removes the content of the loop from the beginning up to the current playback position. This is similar to doing an unrounded multiply from the beginning but it requires only one button press and it happens immediately.

This function will obey the Quantize Mode parameter.

This function is considered to be an instant edit function so it will end the following modes.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will be "stacked" in Confirm and Switch modes and will be executed immediately after the loop switch.

See Shortening The Loop in the Mobius Techniques manual for more information.

5.97 Undo

Internal name: Undo

Undo will cancel scheduled events and move the loop to the previous layer in the layer list. If there are scheduled events, Undo will remove them one at a time. Once all of the events have been removed, Undo will move to the previous layer. If the first layer in the layer list is already active this function will have no effect. If the Maximum Redo parameter is set to a number greater than zero, the current layer will be moved to the redo list. Using Undo and Redo you can freely travel back and forth in the layer history.

If the loop is the MIDI Sync Master, changing layers may require adjustments to the generated MIDI clocks if the cycle size in the new layer is different that the current cycle size. This is controlled by the Resize Sync Adjust parameter.

This function will end all of the following editing modes.

This function is ignored in these modes.

This function may cancel Mute and Pause modes depending on the values of Mute Cancel and Mute Cancel Functions.

This function will cancel the loop switch when in Confirm and Switch modes once all stacked events have been removed.

See Managing Layers in the Mobius Techniques manual for more information.

6 User Interface Functions

Functions beginning with the letters "UI" apply to the Mobius user interface. Most of these have no effect on how Mobius behaves, they just change things in the user interface. They are most commonly bound to computer keyboard keys since you are usually not playing an instrument when you use them.

These functions will not modify the loop in any way and will not change any major or minor modes.

6.1 UI Decrement Parameter

Internal name: decParameter

UI Decrement Parameter will decrease the value of the parameter currently selected in the Instant Parameters display component by one. If the parameter is already set to its lowest value the function has no effect. This can only be used with parameters of type Integer or Enumeration.

The default binding for this function is the '4' (left) key on the number pad.

6.2 UI Increment Parameter

Internal name: incParameter

UI Increment Parameter will increase the value of the parameter currently selected in the Instant Parameters display component by one. If the parameter is already set to its highest value the function has no effect. This can only be used with parameters of type Integer or Enumeration.

The default binding for this function is the '6' (right) key on the number pad.

6.3 UI Next Parameter

Internal name: nextParameter

UI Next Parameter will select the next (lower) parameter in the Instant Parameters display component.

The default binding for this function is the '2' (down) key on the number pad.

6.4 UI Move Display Components

Internal name: spaceDrag

UI Move Display Components is used to reposition components in the Status Area . It is an modal UI function which means it will be in effect over a period of time and it must be bound to a sustainable trigger, typically a computer keyboard key.

While the function trigger is held down, the components in the status area are drawn with outline borders so you can see where they are. You can then use the left mouse button to click and drag them to new locations.

See Customizing the Status Area in the Exploring Mobius manual for more information.

6.5 UI Previous Parameter

Internal name: prevParameter

UI Previous Parameter will select the previous (higher) parameter in the Instant Parameters display component.

The default binding for this function is the '8' (up) key on the number pad.

7 Preset Parameters

A preset is a named collection of parameters that effect how looping functions will be performed. While you can change parameters individually using MIDI or scripts, you will usually change parameters in bulk by selecting presets.

You may need only one preset, or you may define several with parameters chosen for different looping styles. Each track has an active preset that may be changed at any time, even while a loop is playing. Each track may have a different active preset.

All preset parameters can be changed in scripts but these changes are not permanent. Parameters changed in scripts will only live until a new preset is selected, or until the Track Reset or Global Reset functions are executed.

Some parameters are available for binding in the binding windows. You would normally bind them to a trigger that can generate a range of values such as a MIDI expression pedal.

7.1 Auto Record Bars

Internal name: recordBars

Internal value: an integer from 1 to infinity

This parameter determines the number of "bars" that will be recorded by the Auto Record function. The actual length of the recording is determined by a combination of the Auto Record Bars, Auto Record Tempo and Record Beats/Bar parameters.

See Auto Record in the Mobius Techniques manual for more information on how this parameter is used with the Auto Record function.

7.2 Auto Record Tempo

Internal name: recordTempo

Internal name: an integer from 10 to 500

This parameter influences the length of the loop recorded by the Auto Record function. The actual length of the recording is determined by a combination of the Auto Record Tempo, Auto Record Bars and Record Beats/Bar parameters.

See Auto Record in the Mobius Techniques manual for more information on how this parameter is used with the Auto Record function.

7.3 Bounce Quantize

Internal name: bounceQuantize

Internal values: off, subCycle, cycle, loop

This parameter determines the amount of quantization to apply to the Bounce function. Bounce does not use the Quantize Mode parameter.

See Bounce Recording in the Mobius Techniques manual for more information.

7.4 Empty Loop Action

Internal name: emptyLoopAction

Internal values: none, record, copy, copyTiming

This parameter determines the action that will be performed whenever an empty loop is activated. The possible values are:

When set to None, no automatic action will be performed. The loop will be left in Reset mode.

When set to Record, the loop will immediately enter Record mode after the switch. You can record as long as you like but you must remember to execute the Record function to end the recording.

When set to Copy a Loop Copy will be made from the original loop into the new loop.

When set to Copy Timing a Time Copy will be made from the original loop into the new loop.

See Loop Sync in the Mobius Synchronization manual and Empty Loop Action in the Mobius Techniques manual for more information.

7.5 Empty Track Action

Internal name: emptyTrackAction

Internal values: none, record, copy, copyTiming

This parameter determines the action that will be performed whenever a track is selected whose active loop is empty.

When set to None, no automatic action will be performed. The loop will be left in Reset mode.

When set to Record, the loop will immediately enter Record mode after the switch. You can record as long as you like but you must remember to execute the Record function to end the recording.

When set to Copy a Loop Copy will be made from the original loop into the new loop.

When set to Copy Timing a Time Copy will be made from the original loop into the new loop.

See Track Sync in the Mobius Synchronization manual for more information.

7.6 Enable Secondary Feedback

Internal name: altFeedbackEnable

Internal values: true, false

This parameter determines whether the Secondary Feedback track control is used instead of the normal Feedback control when the loop is in certain editing modes. By default the modes obeying secondary feedback are:

You can control which modes obey secondary feedback with the global parameter Modes Ignoring Secondary Feedback

See Using Feedback in the Getting Started With Mobius manual for more information.

7.7 Loops Per Track

Internal name: loopCount

Internal value: an integer between 1 and 8

This parameter determines the number of loops in a track. The default is 4, the minimum number is 1 and the maximum is 8.

See Loops Per Track in the Getting Started With Mobius manual for more information.

7.8 Maximum Redo

Internal name: maxRedo

Internal value: an integer from 0 to infinity

This parameter controls how may layers will be kept for use by the Redo function. It is unset or set to zero, there will be no redo layers. The default value is 1.

See Managing Layers in the Mobius Techniques manual for more information.

7.9 Maximum Tempo

Internal name: maxTempo

Internal value: an integer from 10 to 500

This parameter sets the upper bound of tempos calculated for MIDI clocks generated when a track is the MIDI Sync Master. The value is an integer beats per minute (BPM). The default value is 300. This value should be greater than the value for Minimum Tempo.

See Controlling The Tempo in the Mobius Synchronization manual for more information on how this parameter is used with MIDI Master Sync.

7.10 Maximum Undo

Internal name: maxUndo

Internal value: an integer from 0 to infinity

This parameter controls how may old layers will be kept for use with the Undo function. It is unset or set to zero, there is no limit on the number of layers. The parameter is normally left at zero but if you often create loops with many layers you should consider setting it to a small number to reduce memory requirements.

See Managing Layers in the Mobius Techniques manual for more information.

7.11 Minimum Tempo

Internal name: minTempo

Internal value: an integer from 10 to 500

This parameter sets the lower bound of tempos calculated for MIDI clocks generated when a track is the MIDI Sync Master. The value is an integer beats per minute (BPM). The default value is 20. This value should be less then the value for Maximum Tempo.

See Controlling The Tempo in the Mobius Synchronization manual for more information on how this parameter is used with MIDI Master Sync.

7.12 Multiply Mode

Internal name: multiplyMode

Internal values: normal, simple

This parameter determines how the Multiply function will behave. The possible values are:

The default value is Normal which will make Multiply behave similar to the multiply function in the EDP. When the value is Simple, multiply will only add cycles when you reach the end of the loop and otherwise will behave like the Overdub function.

See Extending The Loop With Multiply in the Mobius Techniques manual for more information on how this parameter effects the Multiply function.

7.13 Mute Cancel

Internal name: muteCancel

Internal values: never, edit, trigger, effect, custom, always

This parameter controls whether mute mode is automatically canceled when executing other functions. The value may be the name of a function class or it may be an explicit list of function names. See the Function Classes section for more information on classes. The possible values are:

NeverMute mode is not canceled until you use another Mute function. Note that mute may still be temporarily canceled with global functions such as Solo.
EditsMute mode is canceled whenever a function that modifies the loop is used. This includes both the Modal Edit and Instant Edit functions.
TriggersMute mode is canceled by the Modal Edit and Instant Edit functions as well as the Trigger functions such as Next Loop, Retrigger, etc.
EffectsMute mode is canceled by the Modal Edit, Instant Edit, and Trigger functions as well as the Effect functions such as Reverse, Half Speed, etc.
CustomThe functions that cancel mute mode may be individually selected.

When this parameter is set to Custom the functions that cancel mute mode are defined by the global parameter named Mute Cancel Functions. Since this is a global parameter it cannot have a different value in each preset.

See Mute, Pause, and Solo in the Mobius Techniques manual for more information.

7.14 Mute Mode

Internal name: muteMode

Internal values: continue, start, pause

Mute Mode determines how the loop behaves when it is taken out of Mute mode. The possible values are:

When this is set to Pause the Mute function will behave the same as the Pause function.

See Mute, Pause, and Solo in the Mobius Techniques manual for more information.

7.15 Mute Sync Mode

Internal name: muteSyncMode

Internal values: transport, transportClocks, clocks, none

This parameter determines how the MIDI master clock changes when the master loop is muted or paused. The clocks may continue or be suspended, and additional MIDI realtime messages such as Start, Stop and Continue. may be sent. This parameter is only relevant when Sync Mode is set to Out or Out Manual Start and the track is acting as the MIDI Sync Master.

See Mute and Pause During MIDI Master Sync in the Mobius Synchronization manual for more information.

7.16 No Feedback Undo

Internal name: noFeedbackUndo

Internal values: true, false

This parameter determines whether feedback reduction alone will cause the creation of a new layer for undo. A layer is created whenever the loop is changed with functions such as Overdub or Replace. When feedback is reduced the loop is also being edited, each pass through the loop the level is reduced slightly until it decays to nothing.

When this parameter is false, every time the loop plays with feedback reduced a new layer is created, even if no other changes were made to the loop. This allows you to use the Undo function to undo the feedback effect. If you let the loop play for a long time with reduced feedback this can result in the creation of many layers.

When this parameter is true, a new layer will not be created if the only change to the loop during the last pass was caused by feedback. This can significantly reduce the amount of memory required for your loops.

See Managing Layers in the Mobius Techniques manual for more information.

7.17 No Layer Flattening

Internal name: noLayerFlattening

Internal values: true, false

This parameter determines whether "flattening" of layers will be disabled. This is an experimental parameter you should not enable unless you understand the consequences.

See Layer Flattening in the Exploring Mobius manual for more information.

7.18 Out Sync Realign Mode

Internal name: outRealignMode

Internal values: midiStart, retrigger

This parameter determines how the Realign function will behave in the MIDI sync master loop. It may either retrigger the Mobius loop from the beginning, or it may send a MIDI Start message to retrigger the external loop from the beginning.

See Realign with MIDI Master Sync in the Mobius Synchronization manual for more information.

7.19 Overdub Quantized

Internal name: overdubQuantized

Internal values: true, false

This parameter determines whether the Overdub function will obey the Quantize Mode parameter. Normally Overdub is not quantized.

See Overdub Quantized fin the Mobius Techniques manual for more information.

7.20 Overdub While Rounding

Internal name: overdubWhileRounding

Internal values: true, false

This parameter determines whether the Multiply and Insert functions will continue to overdub new sound into the loop during the rounding period.

See Extending The Loop With Multiply in the Mobius Techniques manual for more information on how this parameter effects the Multiply function.

7.21 Overdub Transfer

Internal name: overdubTransfer

Internal values: off, follow, restore

This parameter determines whether the Overdub minor mode will be carried over from the current loop to the next loop during a loop switch. The possible values are:

See Overdub Transfer in the Mobius Techniques manual for more information.

7.22 Pitch Sequence

Internal name: pitchSequence

This parameter may be set to a space-delimited list of numbers that represents positive or negative pitch shifts in semitone increments. For example "1" is one semitone above normal, and "-7" is 7 semitones below normal (or a perfect fifth lower). Once a pitch sequence has been set, the pitch may be changed using the Pitch Next and Pitch Previous functions.

See Pitch Shift in the Mobius Techniques manual for more information.

7.23 Pitch Shift Retrigger

Internal name: pitchShiftRetrigger

Internal value: true, false

When this boolean parameter is true, the current loop will be retriggered from the beginning whenever the pitch shift is changed by the Pitch Up, Pitch Down, Pitch Normal, Pitch Next, Pitch Previous, and Pitch Shift functions.

See Pitch Shift in the Mobius Techniques manual for more information.

7.24 Pitch Transfer

Internal name: pitchTransfer

Internal values: off, follow, restore

This parameter determines whether the Pitch Shift minor mode will be carried over from the current loop to the next loop during a loop switch. The possible values are:

See Pitch Transfer in the Mobius Techniques manual for more information.

7.25 Quantize Mode

Internal name: quantize

Internal values: off, subcycle, cycle, loop

This parameter determines whether some functions will be delayed until the next quantization point rather than executing immediately. The possible values are:

Not all functions obey quantization and some use a different parameter to control quantization. See Overdub Quantized Switch Quantize, and Bounce Quantize for other parameters related to quantization.

See Quantize Mode in the Getting Started With Mobius manual for more information on using quantization.

7.26 Rate Sequence

Internal name: rateSequence

Internal value: a space delimited list of integers

This parameter may be set to a space-delimited list of numbers that represents positive or negative rate shifts in semitone increments. For example a rate of "1" is one semitone above normal, a rate of "-7" is 7 semitones below normal (or a perfect fifth lower). Once a rate sequence has been set, the rate may be changed using the Rate Next and Rate Previous functions.

See Rate Shift in the Mobius Techniques manual for more information.

7.27 Rate Shift Retrigger

Internal name: rateShiftRetrigger

Internal value: true, false

When this boolean parameter is true, the current loop will be retriggered from the beginning whenever the playback rate is changed by the Rate Up, Rate Down, Rate Normal, Rate Next, Rate Previous, and Rate Shift functions.

See Rate Shift in the Mobius Techniques manual for more information.

7.28 Rate Transfer

Internal name: autoRecord

Internal values: off, follow, restore

This parameter determines whether the Rate Shift minor mode will be carried over from the current loop to the next loop. This applies to shift applied by the various Rate functions as well as the Half Speed function. The possible values are:

See Rate Transfer in the Mobius Techniques manual for more information.

7.29 Realign Time

Internal name: realignTime

Internal values: immediate, subcycle, cycle, loop, external

This parameter determines when the Realign will be performed. Realign is typically delayed until either the Mobius loop or the external loop reach their start points (loop or external).

See Realign in the Mobius Synchronization manual for more information.

7.30 Record Beats/Bar

Internal name: recordBeats

Internal value: an integer from 1 to 512

This parameter specifies the number of synchronization beats in one bar of music. What a "bar" actually represents is flexible, often it represents a "measure" in standard music notation but it may represent something larger. If this parameter is not set or set to zero, then the Subcycles parameter is used instead. It is recommended that you set the Record Beats/Bar to a non-zero value so that Subcycles may be used for quantization without impacting the bar size.

The parameter is used in three places.

See Setting the Slave Sync Mode in the Mobius Synchronization manual for more information on how this parameter is used with MIDI Slave Sync.

See Controlling The Tempo in the Mobius Synchronization manual for more information on how this parameter is used with MIDI Master Sync.

See Auto Record in the Mobius Techniques manual for more information on how this parameter is used with the Auto Record function.

7.31 Record Resets Feedback

Internal name: recordResetsFeedback

Internal values: true, false

This parameter determines whether the Feedback control will be returned to the level specified in the Track Setup whenever the Record function is executed.

This is convenient if you like to lower feedback once a loop has been recorded but you don't want to manually return it to its default level if you decide to re-record the loop.

7.32 Record Speed Changes

Internal name: rateRecord

Internal values: true, false

This parameter determines whether using the rate shift functions will end a recording in progress or whether they will adjust the rate of the audio being recorded. When true, you can use rate shift functions at any time during Record mode. When the loop is played back you will hear the effects of these changes.

If this parameter is false, using any rate shift functions will cause the recording to be stopped, and the shift will then be applied to the new loop when it begins playing. The default value is false.

See Rate Shifted Recording in the Mobius Techniques manual for more information.

7.33 Record Threshold

Internal name: recordThreshold

Internal value: an integer from 0 to 8

This parameter determines the minimum audio signal level that must be received by a track before the Record function will start. If the parameter is not set or set to zero, there is no threshold and recording starts immediately. You will need to experiment to determine the optimal value for your instrument, a typical value is between 3 and 5.

See Threshold Recording in the Mobius Techniques manual for more information.

7.34 Record Transfer

Internal name: recordTransfer

Internal values: off, follow

This parameter determines whether the Record major mode will be carried over from the previous loop to the next loop during a loop switch. The possible values are:

If set to Off what happens after the switch is determined by the Empty Loop Action parameter. If set to Follow and the current loop is in Record mode, the next loop will always be reset and a new recording will begin immediately.

See Record Transfer in the Mobius Techniques manual for more information.

7.35 Resize Sync Adjust

Internal name: resizeSyncAdjust

Internal values: none, tempo

This parameter determines how the MIDI master clock changes when the master loop size is changed. The clock tempo may either change to match the new size of the loop or it may be held constant. This parameter is only relevant when Sync Mode is set to Out or Out Manual Start and the track is acting as the MIDI Sync Master.

See Adjusting The Tempo in the Mobius Synchronization manual for more information.

7.36 Return Location

Internal name: returnLocation

Internal values: follow, restore, start, random

This parameter determines the playback location of the loop after you have returned from a loop switch when the Switch Duration parameter was set to Once Return or Sustain Return. The possible values are:

See Return Location in the Mobius Techniques manual for more information.

7.37 Reverse Transfer

Internal name: reverseTransfer

Internal values: off, follow, restore

This parameter determines whether the Reverse minor will be carried over from the current loop to the next loop during a loop switch. The possible values are:.

See Reverse Transfer in the Mobius Techniques manual for more information.

7.38 Shuffle Mode

Internal name: shuffleMode

Internal values: reverse, shift, swap, random

This parameter determines how the Shuffle function will behave. The possible values are:

See Shuffle in the Mobius Techniques manual for more information.

7.39 Slip Mode

Internal name: slipMode

Internal values: subCycle, cycle, loop, relSubCycle, relCycle, time

This parameter determines how far the Slip Functions will move. The possible values are:

See Changing Playback Position in the Mobius Techniques manual for more information.

7.40 Slip Time

Internal name: slipTime

Internal value: an integer from 0 to infinity

This parameter determines how far the Slip Functions will move when the Slip Mode parameter is set to Milliseconds. The value is a positive integer number of milliseconds so a slip time of 1000 would cause the Slip Forward function to jump forward 1 second.

See Changing Playback Position in the Mobius Techniques manual for more information.

7.41 Sound Copy Mode

Internal name: soundCopyMode

Internal values: play, overdub, multiply, insert

When performing a Loop Copy because Empty Loop Action was set to Copy, this parameter specifies the mode you will be in after the copy. The possible values are:

The default value is Multiply.

See Sound Copy in the Mobius Techniques manual for more information.

7.42 Speed Sync Adjust

Internal name: speedSyncAdjust

Internal values: none, tempo

This parameter determines how the MIDI master clock changes when the master loop playback rate is changed. The clock tempo may either change to match the new playback rate of the loop or it may be held constant. This parameter is only relevant when Sync Mode is set to Out or Out Manual Start and the track is acting as the MIDI Sync Master.

See Adjusting The Tempo in the Mobius Synchronization manual for more information.

7.43 Subcycles

Internal names: subcycles, 8thsPerCycle

Internal value: an integer between 1 and 512

This parameter sets the number of subdivisions in each cycle. This is used most often with the Quantize Mode parameter to define quantization points. You can see subcycles in the Loop Meter as the shorter tick marks.

While the number of cycles in a loop stays the same until you extend or shorten it, you can change the number of subcycle divisions at any time just by changing the Subcycles parameter. You will see the subcycle tick marks in the Loop Meter change but otherwise the loop is unaffected.

The Subcycles parameter is used by the Shuffle function to define the number of loop slices that will be reordered.

Subcycles may be used to calculate the tempo of the MIDI clocks generated when Sync Mode is Out or Out Manual Start. It will be used only if the value of Record Beats/Bar is not set.

7.44 Switch Duration

Internal name: switchDuration

Internal values: permanent, once, onceReturn, sustain, sustainReturn

This parameter determines how long you will stay in the new loop after a loop switch. It is used by all loop switching functions except Sustain Next Loop, Sustain Previous Loop, Retrigger, and Retrigger Once. The possible values are:

See Switch Duration in the Mobius Techniques manual for more information.

7.45 Switch Location

Internal name: switchLocation

Internal values: follow, restore, start, random

This parameter determines where the playback position will be after you switch to another loop. The possible values are:

See Switch Location in the Mobius Techniques manual for more information.

7.46 Switch Quantize

Internal name: switchQuantize

Internal values: off, subcycle, cycle, loop, confirm, confirmSubcycle, confirmCycle, confirmLoop

This parameter determines when the loop switch functions will be performed. Unlike most other functions, loop switch functions do not obey the Quantize Mode parameter. The loop switch functions are:

The possible values for the Switch Quantize parameter are:

See Switch Quantize in the Mobius Techniques manual for more information.

7.47 Switch Sync Adjust

Internal name: switchSyncAdjust

Internal values: none, tempo

This parameter determines how the MIDI master clock changes when switching between loops in the master track. The clock tempo may either change to match the new loop size or it may be held constant. This parameter is only relevant when Sync Mode is set to Out or Out Manual Start and the track is acting as the MIDI Sync Master.

See Adjusting The Tempo in the Mobius Synchronization manual for more information.

7.48 Switch Velocity Sensitive

Internal name: switchVelocity

Internal values: true, false

This parameter can be used to automatically adjust the track output level during a loop switch. it can only be used if the loop switch function is bound to a MIDI Note message that can carry velocity information. When this parameter is true, the output level of the track will be set to the velocity value of the MIDI note that triggered the loop switch function.

See Switch Velocity Sensitive in the Mobius Techniques manual for more information.

7.49 Sync Mode

Internal name: syncMode

Internal values: off, out, outManual, midiBeat, midiBar, hostBeat, hostBar

This parameter sets the type of external synchronization to be used in the track. It has these values in the UI:

When set to Off the track will not do any external synchronization but it may still do track synchronization defined by the Track Sync Mode parameter.

When set to Out or Out Manual Start the track will attempt to become the MIDI Sync Master and generate an outbound MIDI clock for other slave devices to use. If the track cannot become the MIDI sync master, it may still do track synchronization.

When set to MIDI Beat or MIDI Bar the track will use MIDI Slave Sync and attempt to follow a MIDI clock being generated by an external device.

When set to Host Beat or Host Bar the track will use Host Sync and attempt to follow synchronization pulses generated by the VST or Audio Units host application. This sync mode is only meaningful if Mobius is running as a plugin.

For a thorough discussion of all of the options available for synchronization read the Mobius Synchronization manual.

7.50 Time Copy Mode

Internal name: timeCopyMode

Internal values: play, overdub, multiply, insert

When performing a Time Copy because Empty Loop Action was set to Copy Timing, this parameter specifies the mode you will be in after the copy. The possible values are:

The default value is Insert.

See Time Copy in the Mobius Techniques manual for more information.

7.51 Track Sync Mode

Internal name: trackSyncMode

Internal values: off, subCycle, cycle, loop

This parameter sets the internal track synchronization mode that will be used by the track. This parameter is only relevant if the Sync Mode parameter is set to Off, Out, or Out Manual Start.

For a thorough discussion of all of the options available for synchronization read the Mobius Synchronization manual.

8 Track Parameters

Each track has a few parameters that are set in the Track Setup. These will have their initial values specified in the Track Setup but they may be changed in scripts.

8.1 Focus Lock

Internal name: focus

Internal value: true, false

This parameter determines whether the track has focus lock. The parameter may be set with the Focus Lock function or by clicking on the Track Number in the track strip.

Script example:


    set focus true

    FocusLock 

See Focus Lock in the Exploring Mobius manual for more information.

8.2 Group

Internal name: group

Internal value: an integer from 1 to 8

This parameter determines whether the track is a member of a track group. The value is an integer parameter that has the number of the track group in the current track. If the value is zero there is no track group. Positive group numbers are displayed as letters in the user interface. Group 1 is displayed as A group 2 is displayed as B etc. When setting this parameter from a script you may use either numbers staring from 1 or letters starting from A.

Script example:


    set group 1

    set group A

See Track Groups in the Exploring Mobius manual for more information.

8.3 Preset

Internal name: preset

Internal value: a preset name

This parameter has the name of the preset that is active in the track. This is intended for use only in scripts, in the user interface you select presets from the preset menu or from the preset window.

When setting this from scripts you may use either the preset name or the preset number from 1. While setting this parameter in scripts is allowed, it is preferable in scripts to use the Preset built-in script function.

Script example:


    set preset 1

    set preset "My Preset"

    Preset 1

    Preset "My Preset"

8.4 Preset Number

Internal name: presetNumber

Internal value: an integer from 1 to infinity

This parameter has the number of the preset that is active in the track. This is intended for use only in scripts, in the user interface you select presets from the preset menu or from the preset window.

When setting this from scripts you may use either the preset name or the preset number from 1. While setting this parameter in scripts is allowed, it is preferable in scripts to use the Preset built-in script function.

Script example:


    set presetNumber 1

    Preset 1

The parameter is functionally the same as Preset but using it makes it clearer in the script that the value will be a number rather than a name.

9 Track Controls

Track controls are really just Track Parameters but we call them controls because the values of these parameters is different than the others. A control value ranges from 0 to 127 and is almost always bound to a MIDI expression pedal.

9.1 Feedback

Internal name: feedback

Internal value: 0 to 127

Feedback controls how the loop decays over time. With feedback set at 127 the loop does not decay, it will play that way forever or until you change it with looping functions. With feedback reduced the loop will gradually become softer every time it plays until it eventually decays to silence. A common looping technique is to use Overdub with feedback reduced. You can keep adding new layers to the loop but old layers will decay. In this way you can create evolving loops that change gradually over time.

See Using Feedback in the Getting Started With Mobius manual for more information.

9.2 Input Level

Internal name: input

Internal value: 0 to 127

Input Level controls the amount of attenuation (volume reduction) applied to the audio stream coming in from the audio interface or the plugin host. A value of 127 means that the audio is unmodified. Lowering the value attenuates the audio using an approximate logarithmic curve. Usually input level is left all the way up, but you may want to reduce it if you have different instruments routed to each track and you want to balance their input levels.

9.3 Output Level

Internal name: output

Internal value: 0 to 127

Output Level controls the amount of attenuation applied to the track output as it is sent to the audio device or plugin host. Like Input Level a value of 127 means the is passed unmodified. Output levels are frequently changed to balance the track mix. Functions that add new material to a loop such as Overdub can cause a loop to become progressively louder. After several overdubs it may be necessary to reduce the output level to match the other tracks. Output levels are also commonly changed as an effect, such as temporarily muting tracks or performing a gradual fade in or fade out.

9.4 Pan

Internal name: pan

Internal value: 0 to 127, center 64

Pan adjusts the relative output levels of the left and right channels of the track.

9.5 Secondary Feedback

Internal name: altFeedback

Internal value: 0 to 127

Secondary Feedback is like Feedback except that it is active at different times. It must be enabled by selecting the Enable Secondary Feedback preset parameter.

See Using Feedback in the Getting Started With Mobius manual for more information.

10 Global Parameters

Global parameters affect the operation of Mobius regardless of which setup, preset, or binding configuration is active. There is only one set of global parameters and they are always active. To edit most global parameters open the Configuration menu and select the Global Parameters item.

10.1 16 Bit Wave Files

Internal name: 16BitWaveFile

Internal value: true, false

When this boolean parameter is true, Mobius will save all audio samples as 16-bit integers when writing .wav files. It is found under the Miscellaneous tab of the Global Parameters window.

If this is not enabled, samples are stored as 32-bit floating point numbers. 32-bit is usually preferred because it provides greater dynamic range, but not all audio applications are able to open 32-bit files. If you have trouble loading a file that Mobius saves try saving it in 16-bit mode.

See also Save Loop in the Exploring Mobius manual.

Script example:


    set 16BitWaveFile true

10.2 Audio Input Device

Internal name: audioInput

Internal value: device name

This parameter has the name of the audio device Mobius will open for input when running in standalone mode. Unlike most global parameters this is edited in the Audio Devices window. If you are using an ASIO device the value of this parameter must be the same as the Audio Output Device parameter.

In a script, this parameter may only be read, setting the value will have no effect. One possible script application is to use the parameter in a conditional expression to change the behavior of the script depending on which device is selected.

10.3 Audio Output Device

Internal name: audioOutput

Internal value: device name

This parameter has the name of the audio device Mobius will open for output when running in standalone mode. Unlike most global parameters this is edited in the Audio Devices window. If you are using an ASIO device the value of this parameter must be the same as the Audio Input Device parameter.

In a script, this parameter may only be read, setting the value will have no effect. One possible script application is to use the parameter in a conditional expression to change the behavior of the script depending on which device is selected.

10.4 Bindings

Internal name: bindings

Internal value: binding set name

This parameter has the name of the MIDI binding set that will be merged with the default binding set. Unlike most global parameters this one is set in the MIDI Control window, if you leave a binding set selected other than the first one.

In scripts, the value will be a string containing the name of the binding set. Since binding set names often contain spaces you must remember to surround the name in quotes.

Script example:


    set bindings "Ground Control Pro Bank 1"

10.5 Confirmation Functions

Internal name: confirmationFunctions

Internal value: comma separated list of function names

This parameter contains the names of functions that will cause a loop switch to be confirmed when in Confirm mode. By default the Undo function is in this list for consistency with the EDP.

The Confirm function does not need to be on this list, it is always a switch confirmation function.

In scripts the value of this parameter will be a string containing a comma separated list of function names.

Script example:


    set confirmationFunctions Undo,Redo

10.6 Custom Message File

Internal name: customMessageFile

Internal value: message file name

This parameter is used to specify a alternative file containing the text that Mobius uses in the user interface. It is found under the Miscellaneous tab of the Global Parameters window. The default message file is Catalog_USEnglish.txt.

Creating custom message files can be used if you need to shorten or otherwise change some of the text seen in the user interface. It can also be used if you want to translate the text into another language. This is recommended only for advanced users since the contents of the message file can change at every Mobius release and it can become difficult to synchronize the custom files. If you have a change you think should be in the default message files contact us.

This parameter cannot be set from scripts.

10.7 Drift Check Point

Internal name: driftCheckPoint

Internal value: loop, external

NOTE: This is an experimental parameter that is not visible in the user interface. If you feel you need to use this parameter please contact us.

This parameter determines when Mobius will check to see if synchronized loops have drifted away from the master clock. The possible values are:

When set to external we check for sync drift every time the external loop reaches the start point. The external start point is defined by the number of "pulses" counted when the loop was first recorded. When syncing to MIDI clocks a pulse is a MIDI clock, when syncing to VST beats a pulse is a VST beat, when syncing to a VST bar a pulse is a VST bar, etc.

Every time we receive this number of pulses we are at the external loop start point. For example, when syncing from MIDI clocks, a loop is recorded for 96 clocks. After recording we continue to count MIDI clocks wrapping back to zero every time we count up to 96. When we wrap back to zero, this is the external start point.

Script example:


    set driftCheckPoint external

See Drift Correction in the Mobius Synchronization manual for more information.

10.8 Drift Resync Frames

Internal name: maxSyncDrift

Internal value: an integer from 256 to infinity

This parameter has the number of frames Mobius will allow a loop to drift out of sync with a master clock before it is retriggered to bring it back into alignment. It is found under the Advanced tab of the Global Parameters window.

This parameter may be set from scripts though there is never a need to do so. This is something you normally set once when tuning a new installation, then you leave it that way until something significant changes, like getting a new MIDI interface.

The useful range is between 1000 and 10000. The default value is 2048. Some amount of drift is unavoidable due to clock jitter and tends to correct itself over time. It is not recommended that you set this value below 1000 or excessive and unnecessary retriggering may occur. If you set the value too high drift will not be corrected.

See Drift Correction in the Mobius Synchronization manual for more information.

10.9 Dual Plugin Edit Window

Internal name: dualPluginWindow

Internal value: true, false

This parameter controls the number of windows that will be opened when using Mobius as a VST plugin. It is found under the Miscellaneous tab of the Global Parameters window.

Most plugins open an single "edit" window to change the plugin parameters. But this window is controlled by the host application and it has several important restrictions. The host's window can't be resized which is often desirable after customizing the Mobius user interface. Events from the computer keyboard are also passed inconsistently which means you might not be able to use all of key and shift combinations as Mobius function triggers.

When this option is enabled, Mobius will open two edit windows, the first is the window controlled by the host application, which will be small and contain only the Mobius icon. The second will be an independent window containing the Mobius user interface. Because this window is not controlled by the host, it can be resized and will receive all keyboard events.

This option is only available for VST plugins under Windows. It is not available for either VST or Audio Unit plugins on the Mac.

This parameter cannot be set from scripts.

10.10 Fade Frames

Internal name: fadeFrames

Internal name: an integer from 0 to infinity

NOTE: This is an experimental parameter that is not accessible from the user interface. If you feel you have a need for this parameter please contact us.

Mobius performs a cross fade whenever playback must change abruptly such as when performing an unquantized loop switch, a loop retrigger, or a replace. The value of this parameter is the length of this fade in frames.

This is necessary to prevent "snapping" or "clicking" sounds during playback caused by sudden changes in sample level. The default value is 128 and there is rarely a need to change it. The value cannot be set below 16 because this would increase the chance of audible artifacts. It cannot be set higher than 256 because the size is used in the allocation of stack buffers which must be limited.

Originally this could be set from the Global Parameters window with the intent that users could set it to a very high value to get "pumping" and "breathing" effects. With the introduction of the 256 maximum size, this is no longer possible and since 256 doesn't sound much different than 128 the parameter is no longer exposed.

We may restore the ability to set long fade times, if you have used this in the past please contact us.

Script example:


    set fadeFrames 16

10.11 Focus Lock Functions

Internal name: focusLockFunctions

Internal value: a comma separated list of function names

This parameter specifies which functions will be sensitive to focus lock. It is found under the Functions tab of the Global Parameters window.

In XML this is represented by the FocusLockFunctions element.

In scripts the value is a string containing a comma separated list of internal function names.

Script example:


    set focusLockFunctions Record,Overdub,Multiply

10.12 Groups Have Focus Lock

Internal name: groupFocusLock

Internal value: true, false

This boolean parameter determines whether track groups are to have focus lock behavior. It is found in the Miscellaneous tab of the Global Parameters window. The default value is false.

See Focus Lock and Track Groups and Focus Lock in the Exploring Mobius manual for more information on focus lock behavior and track groups.

10.13 Host MIDI Status Export

Internal name: hostMidiExport

Internal value: true, false

This parameter causes MIDI messages to be sent to the plugin host whenever certain Mobius controls or parameters are changed from the user interface or from scripts. It is found under the Miscellaneous tab of the Global Parameters window. This parameter is only relevant when running Mobius as a plugin. The purpose of this parameter is to keep bi-directional MIDI control surfaces in sync with the actual Mobius state.

Script example:


    set hostMidiExport true

See MIDI Status Export in the Exploring Mobius manual for more information.

10.14 Input Latency

Internal name: inputLatency

Internal value: an integer from 0 to infinity

This parameter has the number of frames of input latency used for latency compensation. Unlike most global parameters this is not set in the Global Parameters window. Instead it is set in the Audio Devices window when you select an audio device. If you entered a value in the Override Input Latency Frames field that will be the initial value of the inputLatency parameter. If you did not specify an override the parameter will have a value returned by the device driver for the audio interface.

You can set this parameter from a script but this is not recommended. If you read some of the Mobius test scripts you will see the latency being set but that is only done so the tests can run with the same latency compensation levels for any audio device. We have never heard of a legitimate reason for users to set this parameter.

10.15 Isolate Overdubs

Internal name: isolateOverdubs

Internal value: true, false

NOTE: This is an experimental parameter that is not accessible from the user interface. This is no longer exposed in the user interface because it is hard to explain, it isn't obvious when it has been enabled, and it can up to double the amount of memory required for each layer. If you feel you have a need for this parameter please contact us.

This is a boolean parameter that when true will cause Mobius to save an independent copy of the new audio content added to each layer. This copy will be saved as a .wav file when you save a project. Normally, new content that is overdubbed in a layer is merged with content carried over from the previous layer in a process called "flattening". When a project is saved the .wav file for the layer contains both the new content and the content from previous layers. When the Isolate Overdubs option is on, the project saves two .wav files for each layer, one containing the flattened content, and one containing only the new content overdubbed during the recording of the layer.

10.16 Long Press Milliseconds

Internal name: longPress

Internal value: an integer from 100 to infinity

This parameter has the number of milliseconds that Mobius will wait while a sustainable trigger is held in its "down" state before performing the long press behavior. It is found under the Miscellaneous tab of the Global Parameters window.

Several functions have long press behavior, the Record function for example will convert to the Reset function if the trigger is held down. Scripts will also receive notification if the long press time has been reached and may take special action. IF a function has long press behavior it will be mentioned in the reference section for that function.

The default value is 500 (1/2 second) which is acceptable to most people. Normally you do not set the value lower than this because it becomes easier to cause the long press behavior accidentally just by lingering a little on the switch. Setting it higher will give you more time to release the switch.

Script example:


    set longPress 1000

10.17 Max Loops Per Track

Internal name: maxLoops

Internal value: an integer from 1 to 16

This parameter has the maximum number of loops that are allowed in each track. It is found under the Limits tab of the Global Parameters window. The default is 4. Note that this does not by itself specify how many loops will be in a track, that is done by the preset parameter Loop Count. For example, Max Loops Per Track may be 8 but if Loop Count is 4 the track will only have 4 loops.

Setting this parameter is important if you have chosen to add the Loop Status component to the track strip. This component displays a vertical column of rectangles representing the loops in a track. Because the actual number of loops is determined by the Loop Count preset parameter, each track may contain a different number of loops. But while tracks can have different numbers of loops, the height of this component must be the same in all tracks. The Max Loops Per Track determines the height of the Loop Status component. If the track has fewer than this number of loops, the component will just display empty space at the bottom.

Because people usually want the track strip to be as short as possible, you should think about the number of loops you will actually need in each track so you don't waste space in the track strip. If you don't use the Loop Status component then this parameter is ignored.

It is not meaningful to set this parameter from a script because changing will not cause the user interface to be redrawn. The value can only be set from the Global Parameters window, and it will only take effect when you restart Mobius.

10.18 Message Duration

Internal name: messageDuration

Internal value: an integer from 0 to infinity

This has the number of seconds that messages generated by the Message script function will appear in the user interface. This is found under the Miscellaneous tab of the Global Parameters window.

The default value is 2. If you set this to 0, messages will be shown continuously until they are changed.

To see messages you must also have the Messages component enabled in the status area. See Components in the Exploring Mobius manual for more information on customizing the user interface.

Script examples:


     set messageDuration 10

10.19 MIDI Input

Internal name: midiInput

Internal value: a comma separated list of device names

This parameter has the names of the MIDI devices that have been selected for input when running in standalone mode. This is not set in the Global Parameters window, it is set from the Input Devices panel in the MIDI Devices window.

When used in a script the value will be a string containing a comma separated list of device names. Setting this value in a script will have no effect until Mobius is restarted.

This is a relatively useless parameter, but you could use it in a script to take different actions depending on the MIDI devices being used.

10.20 MIDI Output

Internal name: midiOutput

Internal name: a device name

This parameter has the name of the MIDI device that has been selected for output when running in standalone mode. This is not set in the Global Parameters window, it is set from the Output Devices panel in the MIDI Devices window.

When used in a script the value will be a string containing the device name. Setting this value in a script will have no effect until Mobius is restarted.

This is a relatively useless parameter, but you could use it in a script to take different actions depending on the MIDI devices being used.

10.21 MIDI Record Pulsed

Internal name: midiRecordPulsed

Internal value: true, false

This parameter determines whether the end of a MIDI slave synchronized recording will be performed exactly on a MIDI clock pulse rather than being calculated based on the average tempo and adjusted for clock jitter. It is found under the Advanced tab of the Global Parameters window. The default is false.

This is an advanced parameter that should only be set after consulting with the Mobius developers. Normally it is better to let Mobius derive the actual loop length by smoothing the MIDI clocks and guessing at the tempo rather than blindly following MIDI clocks which may have significant jitter and arrive at the "wrong" times.

See MIDI Record Pulsed in the Mobius Synchronization manual for more information.

10.22 MIDI Status Export

Internal name: midiExport

Internal value: true, false

This parameter causes MIDI messages to be sent to the selected MIDI output devices whenever certain Mobius controls or parameters are changed from the user interface or from scripts. It is found under the Miscellaneous tab of the Global Parameters window.

The purpose of this parameter is to keep bi-directional MIDI control surfaces in sync with the actual Mobius state. It is relevant for both standalone and plugin modes, but if you want status exports from the plugin you will need to select plugin MIDI devices in the MIDI Devices window.

Script example:


    set midiExport true

See MIDI Status Export in the Exploring Mobius manual for more information.

10.23 MIDI Through

Internal name: midiThrough

Internal value: a device name

This parameter holds the name of the MIDI device that have been selected as a "through" device when running in standalone mode. This is not set in the Global Parameters window, it is set from the Through Device panel in the MIDI Devices window.

A "through" device will immediately receive a copy of every MIDI message that comes in on all the selected input devices. There is rarely a need to select a MIDI through device. Unlike the parameters for input and output devices, there can only be one through device.

When used in a script the value will be a string containing the device name. Setting this value in a script will have no effect until Mobius is restarted.

This is a relatively useless parameter, but you could use it in a script to take different actions depending on the MIDI devices being used.

10.24 Modes Ignoring Secondary Feedback

Internal name: altFeedbackDisable

Internal value: a comma separated list of mode names

This parameter has the names of the recording modes that will not respond to the Secondary Feedback control. It is found under the Modes tab of the Global Parameters window.

Secondary feedback must first be enabled with the Enable Secondary Feedback preset parameter. When this is enabled, the following recording modes will by default use secondary feedback rather than primary feedback.

If you do not want these modes to use secondary feedback, add the mode name to the Modes Ignoring Secondary Feedback parameter using the item selector.

In Replace mode, the feedback level is always zero.

In Insert mode, there is no background content so feedback is not relevant.

In all other modes recording is not active so feedback is not relevant.

The parameter is stored in the mobius.xml file as the AltFeedbackDisables element.

In scripts, the value is a string containing a comma separated list of mode names.

Script example:


    set altFeedbackDisable Multiply,Overdub

10.25 Monitor Audio Input

Internal name: monitorAudioInput

Internal value: true, false

This parameter causes the audio input for the active track to be sent immediately to the audio output device without modification. It is found under the Miscellaneous tab of the Global Parameters window.

This is used if you want to hear the signal being sent into Mobius when you are not monitoring using an external mixer or the "zero latency monitoring" feature of your audio interface.

See Audio Input Monitoring in the Installation Guide for more information on monitoring techniques.

10.26 Mute Cancel Functions

Internal name: muteCancelFunctions

Internal value: comma separated list of function names

This parameter contains the names of functions that will cause an immediate cancellation of Mute or Pause mode. It is found under the Functions tab of the Global Parameters window.

By default, mute mode is only canceled by executing the Mute function a second time, or by executing the Play, Record or Reset functions. Other loop editing functions like Overdub will not cancel Mute mode. This can be used in advanced looping techniques where a loop is muted and then modified without the audience hearing it while it is being modified. Then the loop is unmuted and the audience hears the result.

In scripts the value of this parameter will be a string containing a comma separated list of function names.

Script example:


    set muteCancelFunctions Overdub,Multiply

See Mute, Pause, and Solo in the Mobius Techniques manual for more information.

10.27 Noise Floor

Internal name: noiseFloor

Internal value: an integer from 0 to 65535

This parameter determines the minimum signal level that is considered to be "significant" enough when overdubbing to cause the generation of a new layer. It is found under the Miscellaneous tab of the Global Parameters window.

When Overdub mode is active and new content is added to the loop, a new layer is usually generated at the end of each pass over the loop. If the new audio content is below the noise floor however, a new layer is not generated. This allows you to leave overdub on and listen to the loop a few times without having unnecessary layers generated on each pass.

The EDP calls this feature "auto undo".

If the value is too low, a new layer will be generated every pass through the loop because string noise, AC buzz, or crowd noise is enough to make Mobius think that something important has been recorded. If the value is too high, Mobius may decide not to keep an overdub even if you were playing your heart out.

Script example:


    set noiseFloor 50

See Noise Floor in the Mobius Techniques manual for more information.

10.28 Output Latency

Internal name: outputLatency

Internal value: an integer from 0 to infinity

This parameter has the number of frames of output latency used for latency compensation. Unlike most global parameters this is not set in the Global Parameters window. Instead it is set in the Audio Devices window when you select an audio device. If you entered a value in the Override Output Latency Frames field that will be the initial value of the outputLatency parameter. If you did not specify an override the parameter will have a value returned by the device driver for the audio interface.

You can set this parameter from a script but this is not recommended. If you read some of the Mobius test scripts you will see the latency being set but that is only done so the tests can run with the same latency compensation levels for any audio device. We have never heard of a legitimate reason for users to set this parameter.

10.29 Plugin MIDI Inputs

Internal name: pluginMidiInput

Internal value: a comma separated list of device names

This parameter has the names of the MIDI devices that have been selected for input when running in plugin mode. This is not set in the Global Parameters window, it is set from the Plugin Input Devices panel in the MIDI Devices window.

When used in a script the value will be a string containing a comma separated list of device names. Setting this value in a script will have no effect until Mobius is restarted.

This is a relatively useless parameter, but you could use it in a script to take different actions depending on the MIDI devices being used.

10.30 Plugin MIDI Outputs

Internal name: pluginMidiOutput

Internal name: a comma separated list of device names

This parameter has the names of the MIDI devices that have been selected for output when running in plugin mode. This is set in the Plugin Output Devices panel in the MIDI Devices window.

When used in a script the value will be a string containing a comma separated list of device names. Setting this value in a script will have no effect until Mobius is restarted.

10.31 Plugin MIDI Through

Internal name: pluginMidiThrough

Internal value: a device name

This parameter has the name of the MIDI devices that has been selected for "through" when running in plugin mode. It is set in the Plugin Through Device panel in the MIDI Devices window.

If a through device is selected, any MIDI messages received from all the input devices will be immediately echoed to the through device. Unlike the parameters for input and output devices, you can only select one through device.

When used in a script the value will be a string containing the device name. Setting this value in a script will have no effect until Mobius is restarted.

10.32 Plugin Ports

Internal name: pluginPorts

Internal value: an integer from 2 to 64

This parameter specifies the number of input and output pins we will expose to the VST or Audio Units plugin host. It is set under the Limits tab of the Global Parameters window. The default is 8 ports which corresponds to 16 pins.

Some hosts may refuse to load plugins that have more than one pair of stereo input and output channels. If you have a host that will not the insert the Mobius plugin, try reducing the number of channels.

This is discussed in more detail in the Plugin Pins section of the Installation Guide.

10.33 Quick Save File

Internal name: quickSave

Internal value: file name

This parameter has the file system path to the file where the current loop is saved when selecting the Save Quick menu item or using the Save Loop function. It is found under the Miscellaneous tab of the Global Parameters window.

The name must not include the .wav extension. The actual name of the file will be derived from the specified path plus a number to make the name unique. This allows you to use the Save Quick item several times without overwriting the previous file that was saved.

Script example:


    set quickSave c:\temp\mobiusloop

    set quickSave /Users/Jeff/loops/mobiusloop

See Quick Save in the Exploring Mobius manual for more information.

10.34 Rate/Pitch Shift Range

Internal name: shiftRange

Internal value: an integer from 1 to 128

This parameter defines the range of MIDI notes or controller values that will be automatically bound to the Rate Shift or Pitch Shift functions. The center of the range is defined by the note or control selected in the binding window. The parameter is found under the Miscellaneous tab of the Global Parameters window.

For example, if you bind MIDI note number 60 (middle C) to the Rate Shift function and the Rate/Pitch Shift Range parameter is 12, you will have a two octave range of rate shift available. The center note 60 will be normal, 61 will be one semitone higher, 59 will be one semitone lower, etc. Note that the number defines the number of semitones in one direction, so 12 means 12 semitones up and 12 semitones down for a total range of 24.

This allows you to play loops chromatically without having to manually bind every note in the range, you just bind the center note and Mobius automatically takes care of the rest of the note range.

If you select a wide range, the bindings may conflict with other binding you made in the MIDI Control window. If there is a conflict, the explicit binding seen in the MIDI Control will have priority. For example if you have Rate Shift bound to note 60 with a range of 12 and you have Record bound to note 50, notes 49 and 51 will do a rate shift but 50 will do a record. These "holes" in the shift range make shift hard to use so if you need a wide range it is recommended that you select a single MIDI channel just for rate or pitch shift notes and put all your other MIDI bindings on another channel.

Script example:


    set shiftRange 48

10.35 Reduce Feedback During Overdub

Internal name: autoFeedbackReduction

Internal value: true, false

This is a boolean parameter that when true will cause an automatic 5% reduction in feedback during Overdub, Multiply, and Stutter modes when the Feedback control is set to the maximum value of 127. It is found under the Miscellaneous tab of the Global Parameters window.

Enabling this parameter can reduce the chance of harsh digital clipping when overdubbing because a small amount of feedback will always be applied. Even when enabled though it is still possible to reach clipping if your overdubs are very loud.

Script examples:


     set altFeedbackReduction true

     set altFeedbackReduction false

See Reduce Feedback During Overdub in the Mobius Techniques manual for more information.

10.36 Save Project Layers

Internal name: saveLayers

Internal value: true, false

This is a boolean parameter that when true will cause the complete layer history to be saved with a project. It is found under the Advanced tab of the Global Parameters window.

Normally when a project is saved, only one .wav file is created for each loop that contains the most recent layer. When this parameter is set, we will save one .wav file for every layer in the loop. There are two reasons you might want to set this. First you can use the layer history as raw material when creating audio files in a traditional DAW or audio editor. Second, you can reload the layer history in Mobius so that you can use the Undo function as a performance technique even after saving and loading a project.

Usually this is disabled because it requires extra disk space for the project.

BUG ALERT: There are problems restoring projects saved with layers, we recommend you do not use this parameter if you intend to load the projects back into Mobius.

See Projects in the Exploring Mobius manual for more information.

10.37 Selected Track

Internal name: selectedTrack

Internal value: an integer from 1 to 32

This parameter has the number of the currently selected track and is intended for use only in scripts. This is not set in the Global Parameters window, you select tracks by clicking on them in the main window or by using one of the track selection functions.

The number of the first track is 1. In a script this parameter may be both read and set, when set it will change the selected track. You can also change the selected track with the Track function which is the preferred way to change tracks.

Script example:


    set selectedTrack 2

NOTE: Use of this parameter is not recommended, the parameter may be removed in a future release. Use the Track functions instead to select tracks.

10.38 Setup

Internal name: setup

Internal value: setup number

This parameter has the number of the currently selected track setup. This is not set in the Global Parameters window, instead setups are selected in the Track Setups window.

The value of this parameter is always an integer. The first setup will be number 1, the second number 2, and so on. You can set this parameter from a script to change setups. The value in a script may either be the number or the name.

You can also change setups in a script by using the Setup statement. The behavior is the same, we prefer using the Setup statement. Because of this the setup parameter is relatively useless, you can change it with a function and scripts almost never need to know the number of the currently selected setup.

Script example:


    set setup 2

    set setup "My Setup"

See Track Setups in the Exploring Mobius manual for more information.

10.39 Trace Debug Level

Internal name: traceDebugLevel

Internal value: an integer from 0 to 4

This parameter determines how much information Mobius will be sent to the Windows debug output stream as it runs. It is found under the Advanced tab of the Global Parameters window. This parameter is only meaningful when running on Windows.

The default value is 2 which means both serious errors and operational status messages are sent.

See Trace in the Exploring Mobius manual for more information on trace and the debug output stream.

10.40 Trace Print Level

Internal name: tracePrintLevel

Internal value: an integer from 0 to 4

This parameter determines how much information Mobius will be sent to the console as it runs. It is found under the Advanced tab of the Global Parameters window. This parameter is only meaningful when running on Windows.

The default value is 1 which means only serious errors are sent.

See Trace in the Exploring Mobius manual for more information on trace and what the "console" means for Windows and Mac.

10.41 Track Groups

Internal name: trackGroups

Internal value: an integer from 0 to 8

This parameter has the maximum number of track groups that can be used as a binding scope.. It is found under the Limits tab in the Global Parameters window. The default value is 2.

Setting this to 1 makes track groups behave exactly like Focus Lock so that is not usually done. Setting it to a number higher than the number of tracks may be done but is not recommended since you can't make effective use of all the groups. Typically the number is 2, 3, or 4.

See Track Groups in the Exploring Mobius manual for more information.

10.42 Tracks

Internal name: tracks

Internal value: an integer from 1 to 16

This parameter has the number of tracks that will be shown in the main window. It is found under the Limits tab of the Global Parameters window. The default value is 8.

You can set this number lower to save space in the user interface if you don't need 8 tracks. You can also set it higher if you need more, but there are problems drawing the user interface if you have too many tracks. Changing the parameter will not take effect until you restart Mobius.

Because changes do not take effect until a restart, it is meaningless to set this parameter in a script. You might reference it in a script if you need to know how many tracks there are.

11 Menu Reference

11.1 File

11.1.1 Open Loop

Loads a single loop from a file. A standard file selection dialog window will be displayed to select the loop file. You can only load files stored in the Windows .wav format. The current loop will be reset before loading. After the loop has been read, Mobius will enter Pause mode.

See the Open Loop section of the Exploring Mobius manual for more information.

11.1.2 Open Project

Loads a project from files. A standard file selection dialog window will be displayed to select the project file. Project files must have the .mob extension. All current track content will be lost.

See the Open Project section of the Exploring Mobius manual for more information.

11.1.3 Save Loop

Saves the current loop to a file. A standard file save dialog window will be displayed to select the location of the file. The loop is stored in the Windows .wav format.

See the Save Loop section of the Exploring Mobius manual for more information.

11.1.4 Save Project

Saves a project to files. A standard file selection dialog window will be displayed to select the project file. Audio content for the project will be saved in other files in the same directory as the project file.

See the Save Project section of the Exploring Mobius manual for more information.

11.1.5 Quick Save

Saves the current loop to the file system without prompting you for a location. The location will be determined by the global parameter Quick Save File.

See the Quick Save section of the Exploring Mobius manual for more information.

11.1.6 Exit

In standalone Mobius, this will close the window and halt the application. All track content will be lost if it has not been saved.

In the Mobius plugin this will close the plugin editor window but the plugin remains active.

11.2 Track Setups

This is a dynamic menu whose items will have the same names as the currently configured track setups. Selecting a menu item will activate that setup.

See the Track Setups section in Exploring Mobius for more information on track setups.

11.3 Presets

This is a dynamic menu whose items will have the same names as the currently configured presets. Selecting a menu item will activate that preset.

See the Using Presets section in Getting Started With Mobius for more information on presets.

11.4 Configuration

11.4.1 Presets

Displays a dialog window for managing presets.

See the Using Presets section in Getting Started With Mobius for more information on presets.

11.4.2 Track Setups

Displays a dialog for managing track setups.

See the Track Setups section in Exploring Mobius for more information on track setups.

11.4.3 MIDI Control

Displays a dialog window to manage MIDI bindings.

See the MIDI Bindings section in Getting Started With Mobius for more information on MIDI bindings.

11.4.4 Keyboard Control

Displays a dialog window to manage computer keyboard bindings.

See the Keyboard Bindings section in Getting Started With Mobius for more information on keyboard bindings.

11.4.5 Buttons

Displays a dialog window to select buttons to be displayed at the top of the main Mobius window.

See the Customizing Buttons section in Exploring Mobius for more information on buttons.

11.4.6 Plugin Parameters

Displays a dialog window to manage plugin parameter bindings for VST and Audio Unit hosts.

See the Plugin Parameter Bindings section in Exploring Mobius for more information on plugin parameters.

11.4.7 Scripts

Displays a dialog window to register scripts to be loaded into Mobius. Once registered scripts may be bound to buttons, keys, MIDI events, and any other trigger.

See the Using Scripts section in Getting Started With Mobius for an introduction to scripts.

See the Mobius Scripting manual for a thorough discussion of scripting.

11.4.8 Samples

Displays a dialog window to register a list of audio .wav files that can be played as samples.

See the Samples section in Exploring Mobius for more information on samples.

11.4.9 MIDI Devices

Displays a dialog window to select MIDI input, output, and through devices. There are two sets of devices, one used when Mobius runs as a standalone application, and one when it runs as a plugin.

See the MIDI Device Configuration section in the Mobius Installation Guide for more information on selecting MIDI devices.

11.4.10 Audio Devices

Displays a dialog window to select audio input and output devices when running Mobius as a standalone application.

See the Audio Device Configuration section in the Mobius Installation Guide for more information on selecting audio devices.

11.4.11 Global Parameters

Displays a dialog window to set miscellaneous parameters that affect the operation of Mobius.

See the Global Parameters section for detailed information on each global parameter.

11.4.12 Display Components

Displays a dialog window to specify the loop status components that are displayed in the main Mobius window.

See the Customizing the User Interface section in Exploring Mobius for more information on changing the user interface.

11.4.13 Palette

Displays a dialog window to specify the colors that are used when drawing the graphics in the main Mobius window.

See the Changing Colors section in Exploring Mobius for more information on changing colors.

11.5 Help Menu

11.5.1 Key Bindings

Displays a dialog window that summarizes the functions that are bound to computer keyboard keys. This is a non modal dialog, meaning that you can leave it open and still interact with the main Mobius window.

See the Showing Keyboard Bindings section in Getting Started With Mobius for more information.

11.5.2 MIDI Bindings

Displays a dialog window that summarizes the functions that are bound to MIDI events. This is a non modal dialog, meaning that you can leave it open and still interact with the main Mobius window.

See the Showing MIDI Bindings section in Getting Started With Mobius for more information.

11.5.3 Refresh UI

This will cause the entire Mobius window to be redrawn. Use of this menu item is not usually necessary but it you notice areas in the window that are blank white rectangles, or that don't seem to be displaying properly, try selecting this menu item. This was added to address a problem with the way some plugin hosts open the plugin editor window.

11.5.4 About

Displays ubiquitous about dialog window. There is nothing really interesting here besides the version number which you should include when reporting problems.