Operation Manual
Table Of Contents
- Table of Contents
- The Sequencer
- Routing Audio and CV
- Remote - Playing and controlling Reason devices
- Using Reason as a ReWire Slave
- Advanced MIDI - the External Control Bus inputs
- Synchronization
- Optimizing Performance
- Transport Panel
- Reason Hardware Interface
- The Combinator
- The Mixer
- The Line Mixer 6:2
- Redrum
- Subtractor Synthesizer
- Malström Synthesizer
- NN-19 Sampler
- NN-XT Sampler
- Introduction
- Panel Overview
- Loading Complete Patches and REX Files
- Using the Main Panel
- Overview of the Remote Editor panel
- About Samples and Zones
- Selections and Edit Focus
- Adjusting Parameters
- Managing Zones and Samples
- Working with Grouping
- Working with Key Ranges
- Setting Root Notes and Tuning
- Using Automap
- Layered, Crossfaded and Velocity Switched Sounds
- Using Alternate
- Sample Parameters
- Group Parameters
- Synth parameters
- Connections
- Dr. Rex Loop Player
- Matrix Pattern Sequencer
- ReBirth Input Machine
- BV512 Vocoder
- The Effect Devices
- Common Device Features
- The MClass effects
- The MClass Equalizer
- The MClass Stereo Imager
- The MClass Compressor
- The MClass Maximizer
- Scream 4 Sound Destruction Unit
- RV7000 Advanced Reverb
- RV-7 Digital Reverb
- DDL-1 Digital Delay Line
- D-11 Foldback Distortion
- ECF-42 Envelope Controlled Filter
- CF-101 Chorus/Flanger
- PH-90 Phaser
- UN-16 Unison
- COMP-01 Auto Make-up Gain Compressor
- PEQ-2 Two Band Parametric EQ
- Spider Audio Merger & Splitter
- Spider CV Merger & Splitter
- Menu and Dialog Reference
- About Audio on Computers
- MIDI Implementation
- Index
TRANSPORT PANEL
72
Automation Override
Automation override is activated when you manually “grab” a parameter that is being
automated. If you change the setting of an automated parameter, the “Punched In” in-
dicator lights up, and the automation data is temporarily overridden, until you either
click the “Reset” button or press stop on the transport. As soon as you click Reset,
the automation regains control.
See also page 7.
Audio Out Clipping Indicator
All signals that are being fed into the Hardware Interface (to your audio hardware’s
physical outputs) are monitored for clipping (signal overload) at the output stage.
If clipping occurs this indicator will light up, and stay lit for several seconds. If this hap-
pens, you should reduce the output level, in one of the following ways:
D If the signals are being sent to your Hardware Interface via a mixer de-
vice, you should reduce the master output level from the mixer.
This will ensure that the relative levels of the mix are kept intact. Alternatively, if the
current mix doesn’t represent a “final balance”, and the clipping seems to be
caused by individual channels in the mixer, you could also try reducing the output
of the connected device(s), or pulling down the channel faders a bit for the “of-
fending” channels.
! Clipping can only occur in the output stage of the Hardware Interface,
not in the Reason mixer or in any other Reason device. However, it is
good practice to keep all mixer channel and master levels as high as pos-
sible within the normal range, for best results. For example, having to
compensate channel levels by drastically reducing the Master output to
avoid clipping is indicative of the mixer channel levels being set too high.
✪ If you connect an MClass Maximizer effect (or an MClass Mastering
Suite Combi) between the final mixed output and the hardware interface,
you can maximize the loudness of your mix without risking hard clipping
distortion. See “The MClass effects” for details.
D If the Audio Out Clipping indicator lights up, and the signals are being
sent directly (not via a Mixer) to your Hardware Interface, you can check
the meters in the Hardware Interface. If the red segment of any of these
meters are momentarily lit, this indicates at which output(s) the clipping
is occurring.
Reduce the output level of all devices connected to outputs whose meters show
red.
CPU Meter
This bar graph shows the current CPU (processor) load. Note that this measures how
much of the total processor power the Reason “audio engine” currently is using up.
Graphics, MIDI and the “rest” of the Reason program is allotted the CPU power not
used by the audio engine, so audio always has priority. See “Optimizing Performance”
for more information.