Getting Started Guide
Table Of Contents
- Table of Contents
- Installation
- Setting Up
- Guided Tour
- About this Chapter
- Guided Tour
- The Rack
- The Back
- The Transport Panel
- The Sequencer
- The Tool window
- The Devices
- Reason Hardware Interface
- Combinator
- Mixer 14:2
- Line Mixer 6:2
- Subtractor Analog Synthesizer
- Thor Polysonic Synthesizer
- Malström Synthesizer
- NN-19 Digital Sampler
- NN-XT Digital Sampler
- Dr. Octo Rex Loop Player
- Redrum Drum Computer
- Kong Drum Designer
- MClass Mastering effects
- BV512 Vocoder
- Scream 4 Sound Destruction Unit
- RV7000 Advanced Reverb
- RV-7 Digital Reverb
- DDL Digital Delay Line
- D-11 Foldback Distortion
- ECF-42 Envelope Controlled Filter
- CF-101 Chorus/Flanger
- PH-90 Phaser
- UN-16 Unison
- COMP-01 Compressor
- PEQ2 Two Band Parametric EQ
- Spider Audio Merger & Splitter
- Spider CV Merger & Splitter
- The Matrix Pattern Sequencer
- RPG-8 Monophonic Arpeggiator
- ReBirth Input Machine
- Tutorial 1 - Playing a Song
- Tutorial 2 - Playing devices and selecting sounds
- Tutorial 3 - Creating a drum pattern
- Tutorial 4 - Recording a bass line
- Tutorial 5 - Adding a REX loop
- Tutorial 6 - Adding an arpeggio
- Index
SETTING UP
20
Windows
!
To be able to use both audio inputs and outputs, it’s required that the audio hardware
supports ASIO drivers.
D If you are using audio hardware for which there is a specific ASIO driver, you should se-
lect this.
With an ASIO driver written specifically for the audio hardware, Reason can communicate more or less
directly with the audio hardware. The benefits are lower latency (see below) and possibly better sup-
port for additional hardware features such as multiple outputs.
D If there is no specific ASIO driver, you should select the Direct Sound driver for the audio
hardware.
This makes Reason communicate with the hardware via Direct Sound (a part of the Microsoft DirectX
package). You need to have DirectX installed on your computer, and there must be a Direct Sound
driver for the audio hardware. You will only be able to use audio outputs in this scenario.
D If the audio hardware doesn’t support Direct Sound (i.e. there is no Direct Sound driver
available for the audio hardware), select the MME driver.
This makes use of Windows Multimedia Extensions, the part of Windows that handles audio, MIDI, etc.
Using MME often results in larger latency values (see below). You will only be able to use audio out-
puts in this scenario.
About Latency and other Audio Settings
In the audio page, you will find a number of additional settings for audio. The most important ones are Buf-
fer Size and the corresponding readout for Input and Output Latency.
The Input Latency is the delay between when the audio is “sent” from a connected microphone or instru-
ment and when it’s received and detected by Reason. Output Latency is the delay between when audio is
“sent” from Reason and when you actually hear it. The latencies in an audio system depends on the audio
hardware, its drivers and their settings.
If the output latency is large, you will notice that the sound is delayed when you play a device from a MIDI
keyboard. You may also notice that reactions are delayed when adjusting controls on the device panels
(for example, if you lower the volume of a device, you will not hear this immediately but after the latency
time).
If you experience high latency values, you will need to make adjustments to your configuration.
D If available, use the Buffer Size slider to lower the latency.
D If the Buffer Size slider is greyed out, you may be able to lower the buffer size in the con-
trol panel for the audio hardware - click the Control Panel button to open this.
For more information, please consult the Operation Manual.