MainStage User Guide
- Welcome
-
- Overview of Edit mode
-
- Select patches and sets in the Patch List
- Copy, paste, and delete patches
- Reorder and move patches in the Patch List
- Add and rename patches
- Create a patch from several patches
-
- Overview of the Patch Settings Inspector
- Select patch settings in the Patch Library
- 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
- Transpose the pitch of incoming notes for a patch
- Change the tuning for a patch
- Add text notes to a patch
-
- Overview of channel strips
- Add a channel strip
- Change a channel strip setting
- Configure channel strip components
- Show signal flow channel strips
- Hide the metronome channel strip
- Create an alias of a channel strip
- Add a patch bus
- Set channel strip pan or balance positions
- Set channel strip volume levels
- Mute and solo channel strips
- Use multiple instrument outputs
- Use external MIDI instruments
- Reorganize channel strips
- Delete channel strips
-
- Overview of the Channel Strip Inspector
- Choose channel strip settings
- Rename channel strips
- Change channel strip colors
- Change channel strip icons
- Use feedback protection with channel strips
- Set keyboard input for a software instrument channel strip
- Transpose individual software instruments
- Filter MIDI messages
- Scale channel strip velocity
- Set channel strips to ignore Hermode tuning
- Override concert- and set-level key ranges
- Add text notes to a channel strip in the Channel Strip Inspector
- Route audio via send effects
-
- Screen Control Inspector overview
- Replace parameter labels
- Choose custom colors for screen controls
- Change background or grouped screen control appearance
- 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
-
- Overview of mapping screen controls
- Map to channel strip and plug-in parameters
- Map screen controls to actions
- Map a screen control to multiple parameters
- Use screen controls to display PDF document pages
- Edit the saved value for a mapped parameter
- Set drum pads or buttons to use note velocity
- Map screen controls to all channel strips in a patch
- Undo screen control parameter mappings
- Remove screen control mappings
- Work with graphs
- Create controller transforms
- Share patches and sets between concerts
- Record the audio output of a concert
-
- Overview of concerts
- Create a concert
- Open and close concerts
- Save concerts
- How saving affects parameter values
- Clean up concerts
- Consolidate assets in a concert
- Rename the current concert
-
- Overview of the Concert Settings Inspector
- Set MIDI Routing to channel strips
- Transpose incoming note pitch for a concert
- Define the program change message source
- Send unused program changes to channel strips
- Set the time signature for a concert
- Change the tuning for a concert
- Set the pan law for a concert
- Add text notes to a concert
- Control the metronome
- Silence MIDI notes
- Mute audio output
-
- Layout mode overview
-
- Screen control parameter editing overview
- Lift and stamp screen control parameters
- Reset 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 and import layouts
- Change the aspect ratio of a layout
-
- Before performing live
- Use Perform mode
- Screen controls in performance
- Tempo changes during 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
-
- Overview of keyboard shortcuts and command sets
-
- Concerts and layouts keyboard shortcuts
- Patches and sets (Edit mode) keyboard shortcuts
- Editing keyboard shortcuts
- Actions keyboard shortcuts
- Parameter mapping (Edit mode) keyboard shortcuts
- Channel strips (Edit mode) keyboard shortcuts
- Screen controls (Layout mode) keyboard shortcuts
- Perform in Full Screen keyboard shortcuts
- Window and view keyboard shortcuts
- Help and support keyboard shortcuts
-
-
- Use MIDI plug-ins
-
- Arpeggiator overview
- Arpeggiator control parameters
- Note order parameters overview
- Note order variations
- Note order inversions
- Arpeggiator pattern parameters overview
- Use Live mode
- Use Grid mode
- Arpeggiator options parameters
- Arpeggiator keyboard parameters
- Use keyboard parameters
- Assign controllers
- Modifier controls
- Note Repeater controls
- Randomizer controls
-
- Use Scripter
- Use the Script Editor
- Scripter API overview
- MIDI processing functions overview
- HandleMIDI function
- ProcessMIDI function
- GetParameter function
- SetParameter function
- ParameterChanged function
- Reset function
- JavaScript objects overview
- Use the JavaScript Event object
- Use the JavaScript TimingInfo object
- Use the Trace object
- Use the MIDI event beatPos property
- Use the JavaScript MIDI object
- Create Scripter controls
- Transposer controls
-
-
- Alchemy overview
- Alchemy interface overview
- Alchemy Name bar
- Alchemy file locations
-
- Alchemy source overview
- Source master controls
- Import browser
- Source subpage controls
- Source filter controls
- Source filter use tips
- Source elements overview
- Additive element controls
- Additive element effects
- Spectral element controls
- Spectral element effects
- Pitch correction controls
- Formant filter controls
- Granular element controls
- Sampler element controls
- VA element controls
- Source modulations
- Morph controls
- Alchemy master voice section
- Alchemy Extended parameters
-
- Playback plug-in overview
- Add a Playback plug-in
- 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
-
- Sample Alchemy overview
- Interface overview
- Add source material
- Edit mode
- Play modes
- Source overview
- Synthesis modes
- Granular controls
- Additive effects
- Additive effect controls
- Spectral effect
- Spectral effect controls
- Filter module
- Low and highpass filter
- Comb PM filter
- Downsampler filter
- FM filter
- Envelope generators
- Mod Matrix
- Modulation routing
- Motion mode
- Trim mode
- More menu
-
- Sculpture overview
- Sculpture interface
- Global parameters
- Amplitude envelope parameters
- Use the Waveshaper
- Filter parameters
- Output parameters
- Define MIDI controllers
- Extended parameters
-
- Copyright
Use Noise Gate in MainStage
Set the Reduction knob to the lowest possible value to make sure that sounds below the Threshold value are completely suppressed. Set Reduction to a higher value to reduce low-level sounds but still allow them to pass. You can also use Reduction/Ducking to boost the signal by up to 20 dB, which is useful for ducking effects.
The Attack, Hold, and Release knobs modify the dynamic response of Noise Gate. If you want the gate to open extremely quickly for percussive signals such as drums, set the Attack knob to a lower value. For sounds with a slow attack phase, such as string pads, set Attack to a higher value. Similarly, when working with signals that fade out gradually or that have longer reverb tails, set a higher Release knob value that allows the signal to fade out naturally.
The Hold knob determines the minimum amount of time that the gate stays open. You can use the Hold knob to prevent abrupt level changes—known as chattering—caused by rapid opening or closing of the gate.
The Hysteresis slider provides another option for preventing chattering, without needing to define a minimum Hold time. Use it to set the range between the threshold values that open and close the gate. This is useful when the signal level hovers around the Threshold level, causing Noise Gate to switch on and off repeatedly, thus producing the undesirable chattering effect. The Hysteresis slider essentially sets the gate to open at the Threshold level and remain open until the level drops below another, lower, level. As long as the difference between these two values is large enough to accommodate the fluctuating level of the incoming signal, Noise Gate can function without creating chatter. This value is always negative. Generally, −6 dB is a good place to start.
In some situations, the level of the signal you want to keep and the level of the noise signal may be close, making it difficult to separate them. For example, when you are recording a drum kit and using Noise Gate to isolate the sound of the snare drum, the hi-hat may also open the gate in many cases. To remedy this, use the side chain controls to isolate the desired trigger signal with the High Cut and Low Cut filters.
Important: The side chain signal is used only as a detector/trigger in this situation. The filters are used to isolate particular trigger signals in the side chain source, but they have no influence on the actual gated signal—the audio being routed through Noise Gate.
Use the side chain filters
In MainStage, click the Monitor button to hear how the High Cut and Low Cut filters affect the incoming trigger signal.
Drag the High Cutoff slider to set the upper frequency.
Trigger signals above this are filtered.
Drag the Low Cutoff slider to set the lower frequency.
Trigger signals below this are filtered.
The filters allow only very high (loud) signal peaks to pass. In the drum kit example above, you could remove the hi-hat signal, which is higher in frequency, with the High Cut filter and allow the snare signal to pass. Turn off monitoring to set a suitable Threshold level more easily.
Use Noise Gate in Ducking mode
In MainStage, insert Noise Gate into an aux channel strip and click the Ducker button.
Assign all channel strip outputs that you want to “duck” (dynamically lower the volume of the mix) to a bus—the aux channel strip chosen in step 1.
In the Noise Gate plug-in window header, choose the bus that carries the ducking (vocal) signal from the Side Chain pop-up menu.
Note: The ducked side chain is mixed with the output signal after passing through the plug-in. This ensures that the ducking side chain signal—the voiceover—is heard at the output.
Adjust Noise Gate parameters as required.