Operation Manual

ManualsBrandsPropellerhead ManualsSoftwarePropellerhead Reason - 1.0.1

Table Of Contents

Table of Contents
The Sequencer
- Recording
- Copying REX loops and Patterns to Sequencer Tracks
- Editing - About Snap
- Editing in the Arrange View
- Using Groups
- The Edit View
- Quantizing
- The Change Events Dialog
- Importing and Exporting MIDI Files
Routing Audio and CV
- About the various signals that can be routed
- About Cables
- Automatic Routing
- Manual Routing
- Using CV and Gate
Routing MIDI to Reason
- About the Various MIDI Inputs
- Sending MIDI Data to Reason
- Controlling Devices directly via MIDI
Using Reason as a ReWire Slave
- About this Chapter
- Why use Reason with ReWire?
- Introducing ReWire!
- Preparations for Using ReWire - Macintosh only
- Launching and Quitting
- Steinberg Cubase VST
- Emagic Logic Audio
- Mark of the Unicorn Digital Performer
- Using the Transport and Tempo Controls
- MIDI Control With ReWire
- Converting ReWire Channels to Audio Tracks
- Synchronization
MIDI and Keyboard Remote Control
- Introduction
- MIDI Remote Mapping
- Keyboard Remote
- Saving Remote Setups
Synchronization
- ReWire users – Read This!
- What is Synchronization and MIDI Clock?
- Slaving Reason to an External Device
- Slaving Reason to Another Program on the Same Computer
- MacOS: Slaving Reason to a non-OMS Program
- Synchronization Considerations
Optimizing Performance
- Introduction
- Optimization and Output Latency
- Optimizing Your Computer System
- Optimizing Songs
- Songs and Memory Requirements
Transport Panel
- Overview
Reason Hardware Interface
- Introduction
- MIDI In Device
- Audio Out
The Mixer
- Introduction
- The Channel Strip
- The Mixer Signal Flow
- The Auxiliary Return Section
- The Master Fader
- Connections
- Chaining Mixers
Redrum
- Introduction
- About File Formats
- Using Patches
- Programming Patterns
- Redrum Parameters
- Using Redrum as a Sound Module
- Connections
Subtractor Synthesizer
- Introduction
- The Oscillator Section
- The Filter Section
- Envelopes - General
- LFO Section
- Play Parameters
- External Modulation
- Connections
NN-19 Digital Sampler
- Introduction
- General Sampling Principles
- About Audio File Formats
- About Key Zones and Samples
- Automap Samples
- NN-19 Synth Parameters
- Play Parameters
- Connections
Dr. Rex Loop Player
- Introduction
- About File Formats
- Adding a Loop
- Creating Sequencer Notes
- Slice Handling
- Dr.Rex Synth Parameters
- Connections
Matrix Pattern Sequencer
- Introduction
- Programming Patterns
- Example Usage
ReBirth Input Machine
- Introduction
- Preparations
- Routing
The Effect Devices
- Common Device Features
- 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
- COMP-01 Auto Make-up Gain Compressor
- PEQ-2 Two Band Parametric EQ
Menu and Dialog Reference
- File Menu
- Edit Menu
- Create Menu
- Options Menu
- Windows Menu (Windows Version)
- Windows Menu (MacOS Version)
- Help/Contacts Menu
About Audio on Computers
- General Information
- PC Specific Information
- Macintosh Specific Information
MIDI Implementation
- About This Chapter
- How various MIDI messages are Implemented
Index

ROUTING MIDI TO REASON

➜ 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 Pref-

erence dialog.

Once you have set up communication between Reason and the other device

or application, you can hide the sequencer from view, by clicking the “maxi-

mize 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

Reason 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 nor-

mally 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 oc-

cur immediately (not at the end of the bar), which may or may not be what

you prefer.

Please see page 8 for information on recording and editing pattern changes.