Additional Transport Panel Items
Click

When this is activated, you will hear a click on each beat, with an accent on the downbeat of each bar. The click is played back during recording and playback. You can adjust the volume of the click by using the Level knob.

MIDI Sync and Focus

This section of the Transport Panel contains items relating to MIDI sync.

The "Enable" button puts Reason into MIDI sync mode.

The transport controls will be disabled, and Reason will not run unless MIDI sync data is provided from an external device.

The MIDI and Play Focus buttons relate to how incoming MIDI and MIDI sync should be handled if there are several open Song documents. If you have two or more Songs opened, and no MIDI sync is used, the currently selected Song (the document "on top") always has MIDI focus. If MIDI Sync is enabled (which is global for all currently open Song documents), this functionality changes in the following way:

If both "Play" and "MIDI" are activated for a Song, incoming MIDI data and MIDI sync will be sent to this Song, regardless of whether another Song is currently in focus.

If only "MIDI" is activated for Song, and another Song has "Play" focus, incoming MIDI will be sent to the former and MIDI sync to the latter (i.e this Song will play back), regardless of which Song is currently in focus.

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" indicator 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.

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 happens, you should reduce the output level, in one of the following ways:

If the signals are being sent to your Hardware Interface via a Mixer, 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 "offending" 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 possible 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 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.