3
Table Of Contents
- MainStage 3 User Manual
- Contents
- Chapter 1: Introducing MainStage
- Chapter 2: Set up your system
- Chapter 3: The MainStage interface
- Chapter 4: Get started with MainStage
- Chapter 5: Work in Edit mode
- Edit mode overview
- Work with patches in Edit mode
- Select items in the Patch List
- Copy, paste, and delete patches
- Reorder and move patches in the Patch List
- Create a patch from several patches
- Set the time signature for patches
- Change the tempo when you select a patch
- Set program change and bank numbers
- Defer patch changes
- Instantly silence the previous patch
- Change patch icons
- Change the tuning for a patch
- Work with channel strips in Edit mode
- Channel strips overview
- Show signal flow channel strips
- Show the metronome channel strip
- Create an alias of a channel strip
- Add a patch bus
- Channel Strip Inspector
- Choose channel strip settings
- Rename channel strips
- Change channel strip colors
- Change channel strip icons
- Use feedback protection with channel strips
- Work with software instrument channel strips
- Use the EXS24 mkII Instrument Editor in MainStage
- Use multiple instrument outputs
- Use external MIDI instruments in MainStage
- Delete channel strips
- Create keyboard layers and splits
- Work with graphs
- Create controller transforms
- Work with plug-ins in Edit mode
- Map screen controls
- Screen controls overview
- Map screen controls to channel strip and plug-in parameters
- Map screen controls to actions
- Map a screen control to multiple parameters
- Edit the saved value for a mapped parameter
- Set drum pads or buttons to use note velocity
- Use parameter mapping graphs
- Map screen controls to all channel strips in a patch
- Undo screen control parameter mappings
- Remove screen control mappings
- Work in the Assignments and Mappings tab
- Edit screen control parameters in Edit mode
- Screen control parameters in Edit mode overview
- Replace parameter labels
- Choose custom colors for screen controls
- Change the appearance of a background or grouped screen control
- Set screen controls to show the hardware value
- Set parameter change behavior for screen controls
- Set hardware matching behavior for screen controls
- Reset and compare changes to a patch
- Override concert- and set-level mappings
- Work with sets in Edit mode
- Share patches and sets between concerts
- Record the audio output of a concert
- Chapter 6: Work with concerts
- Open and close concerts
- Save concerts
- How saving affects parameter values
- Set the time signature for a concert
- Use tempo in a MainStage concert
- Define the source for program change messages
- Set the pan law for a concert
- Change the tuning for a concert
- Silence MIDI notes
- Mute audio output
- Work at the concert level
- Control the metronome
- Chapter 7: Work in Layout mode
- Layout mode overview
- Work with screen controls in Layout mode
- Assign hardware controls to screen controls
- Edit screen control parameters
- Screen control parameter editing overview
- Lift and stamp screen control parameters
- Common screen control parameters
- Keyboard screen control parameters
- MIDI activity screen control parameters
- Drum pad screen control parameters
- Waveform screen control parameters
- Selector screen control parameters
- Text screen control parameters
- Background screen control parameters
- How MainStage passes through MIDI messages
- Export layouts
- Import a layout
- Change the aspect ratio of a layout
- Chapter 8: Perform live with MainStage
- Before the performance
- Use Perform mode
- Select patches in performance
- Screen controls in performance
- Tempo changes in performance
- Tips for performing with keyboard controllers
- Tips for performing with guitars and other instruments
- Tune guitars and other instruments with the Tuner
- The Playback plug-in in performance
- Record your performances
- After the performance
- Tips for complex hardware setups
- Appendix A: The Playback plug-in
- Playback plug-in overview
- The Playback interface
- Use the Playback waveform display
- Playback transport and function buttons
- Playback information display
- Playback Sync, Snap To, and Play From parameters
- Use the Playback group functions
- Use the Playback Action menu and File field
- Use markers with the Playback plug-in
- Use the Playback plug-in in a concert
- Appendix B: The Loopback plug-in
- Appendix C: MainStage preferences
- Appendix D: Key commands
- Appendix E: MainStage actions
Chapter 6 Work with concerts 99
The MainStage clock
Some plug-ins, including the Playback and Ultrabeat plug-ins, require a time source, and use beat
and tempo information in order to play in time.
Additionally, some third-party applications and plug-ins using their own sequencer or playback
engine may behave dierently than the included plug-ins. These applications (which include
Reason and other ReWire applications, and Reaktor) require a play message from the host
application to begin playback and require a stop message to end playback. They may also
require a continue (also sometimes called “resume”) message to continue playback from their
current time position.
MainStage includes an internal beat clock or “time base” that you can use to control the playback
of these plug-ins. The MainStage clock generates beat, time position, and tempo information
so sequencer-oriented plug-ins can start, stop, and play in time. The MainStage clock operates
similarly to the song position in Logic Pro or other DAW applications.
You can send play and stop messages in the following ways:
•
Using the Play/Stop button in the toolbar, if it is visible
•
Using the Metronome button in the toolbar, if it is visible (turning on the metronome also
starts the MainStage clock, if it is not already running)
•
Using a screen control mapped to the Play/Stop, Play, or Stop action
•
Using a screen control mapped to the Continue action to resume playback of a third-party
plug-in (but not a Playback plug-in)
Dierent plug-ins can make use of the MainStage clock in dierent ways, depending on what
information they require and what mode they are set to. Some plug-ins may only make use of
the beat information, while others may only make use of tempo information. For example:
•
The Playback plug-in can start immediately (if Snap To is set to O), at the beginning of the
next bar (if Snap To is set to Bar), or at the next beat (if Snap To is set to Beat). It can also
start when you start the MainStage clock (if Start with Play Action is chosen from the Action
pop-up menu).
•
UltraBeat starts when you start the MainStage clock if its sequencer is turned on, except in
Pattern mode.
•
Reason and other ReWire applications start when you start the MainStage clock, and stop
when you stop the MainStage clock.
•
For plug-ins with synchronizable LFOs, the LFO can oscillate at the tempo set by the
MainStage clock (you can also send MIDI beat clock to synchronize external MIDI devices).
You can view the beat information of the MainStage clock using a Parameter Text screen control
mapped to the Beat Count action. When the MainStage clock is running, the current bar and
beat are displayed in the screen control.










