Specifications
Table Of Contents
- Table of Contents
- The Sequencer
- Routing Audio and CV
- Routing MIDI to Reason
- Using Reason as a ReWire Slave
- MIDI and Keyboard Remote Control
- Synchronization
- Optimizing Performance
- Transport Panel
- Reason Hardware Interface
- The Mixer
- 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
- 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
ROUTING MIDI TO REASON
46
D You have sequencer software installed on the same computer as
Reason.
This requires the “OMS IAC Driver” under Mac OS 9, or a MIDI routing ap-
plication under Windows, as explained previously in this chapter.
D If you want to manually play (i.e not recorded MIDI data) Reason de-
vices in real time from inside another sequencer program, MIDI thru
must be activated.
MIDI thru is when incoming MIDI is echoed out via the MIDI output. If you
don’t know how to do this, refer to the program’s documentation. You will
also need to make sure that the other application is “thruing” it’s data to the
correct MIDI port and on the right MIDI channel.
Bypassing the sequencer completely
It is possible to use Reason devices purely as “sound modules”, bypassing the
Reason sequencer completely. To do this, you should use the External Control
busses to receive MIDI, and deselect the Sequencer port in the Preference dia-
log.
Once you have set up communication between Reason and the other device or
application, you can hide the sequencer from view, by clicking the “maximize
rack” button at the top of the rack’s vertical scrollbar.
Sending Controller Data via MIDI
It is possible to send controller data from an external sequencer to control Rea-
son parameters. Just set up your external device to transmit the correct MIDI
controller messages on the right MIDI channel.
To find out which MIDI Controller number corresponds to which control on each
device, please see the “MIDI Implementation Charts.pdf” document.
Once you have located the controller numbers and set everything up, you can
record and edit the controller data in the external sequencer as you normally do,
and the Reason parameters will react correspondingly.
✪ Do not confuse Remote Control and direct MIDI control. MIDI Re-
mote allows you to map any MIDI Controller to any control on the
front panel, but is primarily intended for “live” tweaking of parame-
ters during playback.
Recording Pattern changes
As specified in the MIDI Implementation, MIDI Controller #3 can be used to
switch patterns in a device. However, pattern changes activated this way occur
immediately (not at the end of the bar), which may or may not be what you prefer.
Please see page 10 for information on recording and editing pattern changes.