ReWire

From CockosWiki

(Difference between revisions)
Jump to: navigation, search
(Undo revision 13228 by Ucokane (Talk))
 
Line 6: Line 6:
'''ReWire''' is a technology developed by '''Propellerhead Software''' that allows applications to share audio, MIDI and synchronization data. Audio and MIDI data are transferred between the two applications in real-time, allowing you to use the features in each application as if they were one.  
'''ReWire''' is a technology developed by '''Propellerhead Software''' that allows applications to share audio, MIDI and synchronization data. Audio and MIDI data are transferred between the two applications in real-time, allowing you to use the features in each application as if they were one.  
-
In a ReWire session, the first application acts as the Host, and the second application acts as the Slave. The Slave receives and sends signals via the Host application.
+
In a ReWire session, the first application acts as the Host, and the second application acts as the Client. The Client receives and sends signals via the Host application.
-
''NOTE: The Tempo of the ReWire Host sets the Tempo of both applications. When you launch a ReWire session, the Slave application will automatically adopt the Tempo of the Host application. If you are planning to use ReWire to open an existing Project in the Slave application, you should open the Slave application and note the Tempo of the Project before running a ReWire session.''
+
''NOTE: The Tempo of the ReWire Host sets the Tempo of both applications. When you launch a ReWire session, the Client application will automatically adopt the Tempo of the Host application. If you are planning to use ReWire to open an existing Project in the Client application, you should open the Client application and note the Tempo of the Project before running a ReWire session.''
Line 20: Line 20:
-
== Routing AUDIO from the Slave application to REAPER ==
+
== Routing AUDIO from the Client application to REAPER ==
-
The Main Mix output from the Slave application will be automatically routed to the Track you have just used to start the ReWire session.
+
The Main Mix output from the Client application will be automatically routed to the Track you have just used to start the ReWire session.
-
To check that audio is getting from the Slave application to REAPER, load a Project into the Slave application, and use either of the following methods to test playback:
+
To check that audio is getting from the Client application to REAPER, load a Project into the Client application, and use either of the following methods to test playback:
-
==== Method 1. Record-Arm the Track that contains the ReWire slave ====
+
==== Method 1. Record-Arm the Track that contains the ReWire Client ====
-
Arming the Track synchronizes the Slave application to REAPER. You should now be able to hear the output from the Project in the Slave application when you press Play in the REAPER Transport.
+
Arming the Track synchronizes the Client application to REAPER. You should now be able to hear the output from the Project in the Client application when you press Play in the REAPER Transport.
==== Method 2. Insert an "Empty Event" in the REAPER Project ====
==== Method 2. Insert an "Empty Event" in the REAPER Project ====
-
The other method of synchronizing the Slave application is to insert an "Empty Event" in a REAPER Track. In the example above, REAPER has automatically matched the Loop settings of the Reason Project. An Empty Event was inserted by selecting Insert > Empty Event, and the edge of the Empty Event was then dragged to match the length of the Reason Project. You can now press Play on the REAPER Transport to hear playback. With this method, the Track containing the ReWire Slave does not have to be record-armed.
+
The other method of synchronizing the Client application is to insert an "Empty Event" in a REAPER Track. In the example above, REAPER has automatically matched the Loop settings of the Reason Project. An Empty Event was inserted by selecting Insert > Empty Event, and the edge of the Empty Event was then dragged to match the length of the Reason Project. You can now press Play on the REAPER Transport to hear playback. With this method, the Track containing the ReWire Client does not have to be record-armed.
== Routing Multiple Audio Outputs ==
== Routing Multiple Audio Outputs ==
-
Multiple Audio outputs can be routed from the Slave application to REAPER. Audio outputs are routed via the Audio Outputs tab of the ReWire plug-in.  
+
Multiple Audio outputs can be routed from the Client application to REAPER. Audio outputs are routed via the Audio Outputs tab of the ReWire plug-in.  
==== To enable multiple audio outputs via a ReWire session ====
==== To enable multiple audio outputs via a ReWire session ====
-
1. Assign the outputs in the Slave application to individual outputs. The procedure for doing this will vary from application to application. Consult the User Manual for your application for more information.
+
1. Assign the outputs in the Client application to individual outputs. The procedure for doing this will vary from application to application. Consult the User Manual for your application for more information.
-
2. Click on the I/O button of the Track that contains the Slave application.
+
2. Click on the I/O button of the Track that contains the Client application.
3. Click on the Track Channels down-arrow and select the number of Channels you wish to route.
3. Click on the Track Channels down-arrow and select the number of Channels you wish to route.
Line 50: Line 50:
REAPER supports 64 Track Channels per Track. Track Channels work like an internal patch bay, allowing you to patch up to 64 outputs from any plug-in used in the FX chain of the Track.
REAPER supports 64 Track Channels per Track. Track Channels work like an internal patch bay, allowing you to patch up to 64 outputs from any plug-in used in the FX chain of the Track.
-
4. Click on the FX button of the Track that contains the Slave application to open the FX chain.
+
4. Click on the FX button of the Track that contains the Client application to open the FX chain.
5. Select the Audio Outputs tab.  
5. Select the Audio Outputs tab.  
-
The ReWire Output column will list the individual outputs you have assigned in your Slave application.
+
The ReWire Output column will list the individual outputs you have assigned in your Client application.
6. Right-click on the Track Channel corresponding to the ReWire Output you wish to route.
6. Right-click on the Track Channel corresponding to the ReWire Output you wish to route.
Line 68: Line 68:
The number of Track Channels displayed will correspond to the number you selected in Step 3 of this procedure. Track Channels can be assigned as Stereo - e.g. Channel 63/64, or Mono - e.g. Channel 64.
The number of Track Channels displayed will correspond to the number you selected in Step 3 of this procedure. Track Channels can be assigned as Stereo - e.g. Channel 63/64, or Mono - e.g. Channel 64.
-
The individual audio outputs from your Slave application will now play via the Tracks you have assigned them to in REAPER.
+
The individual audio outputs from your Client application will now play via the Tracks you have assigned them to in REAPER.
-
== Routing MIDI from REAPER to the Slave application ==
+
== Routing MIDI from REAPER to the Client application ==
-
ReWire gives you the ability to use MIDI instruments in the Slave application as if they were normal VSTi or DXi plug-ins. You can route MIDI Tracks from REAPER to the Slave, or record MIDI Tracks in the Slave via ReWire.
+
ReWire gives you the ability to use MIDI instruments in the Client application as if they were normal VSTi or DXi plug-ins. You can route MIDI Tracks from REAPER to the Client, or record MIDI Tracks in the Client via ReWire.
-
=== To route a MIDI Track from REAPER to the Slave application ===
+
=== To route a MIDI Track from REAPER to the Client application ===
-
1. Click on the I/O button of the MIDI Track you want to route to the Slave application. In this example, we are going to send the MIDI from Track 6 to the Slave.
+
1. Click on the I/O button of the MIDI Track you want to route to the Client application. In this example, we are going to send the MIDI from Track 6 to the Client.
-
2. Select the Send to the Track that contains the Slave application. MIDI from Track 6 will now be sent to Track 1, which contains the Slave application.
+
2. Select the Send to the Track that contains the Client application. MIDI from Track 6 will now be sent to Track 1, which contains the Client application.
=== Multiple MIDI channels ===
=== Multiple MIDI channels ===
-
Multiple MIDI Tracks can be sent to the Slave application as long as they have been separated into individual MIDI channels. MIDI Routing is assigned via the MIDI Inputs tab of the ReWire plug-in.  
+
Multiple MIDI Tracks can be sent to the Client application as long as they have been separated into individual MIDI channels. MIDI Routing is assigned via the MIDI Inputs tab of the ReWire plug-in.  
-
To route multiple MIDI channels to the Slave application:
+
To route multiple MIDI channels to the Client application:
-
1. Open the FX chain of the Track that contains the ReWire Slave application.
+
1. Open the FX chain of the Track that contains the ReWire Client application.
2. Right-click on the ReWire Destination for the MIDI Channel you wish to route.
2. Right-click on the ReWire Destination for the MIDI Channel you wish to route.
Line 97: Line 97:
4. Repeat for each MIDI channel that you want to route.
4. Repeat for each MIDI channel that you want to route.
-
The MIDI channels will now be routed from REAPER to the selected destination in the Slave application.
+
The MIDI channels will now be routed from REAPER to the selected destination in the Client application.

Latest revision as of 14:38, 15 June 2020

Main Page > REAPER Documentation


Contents

Starting a ReWire session in REAPER

ReWire is a technology developed by Propellerhead Software that allows applications to share audio, MIDI and synchronization data. Audio and MIDI data are transferred between the two applications in real-time, allowing you to use the features in each application as if they were one.

In a ReWire session, the first application acts as the Host, and the second application acts as the Client. The Client receives and sends signals via the Host application.

NOTE: The Tempo of the ReWire Host sets the Tempo of both applications. When you launch a ReWire session, the Client application will automatically adopt the Tempo of the Host application. If you are planning to use ReWire to open an existing Project in the Client application, you should open the Client application and note the Tempo of the Project before running a ReWire session.


1. Click on the FX button of the Track that will host the ReWire application.

2. Select ReWire from the FX plug-in list.

3. REAPER will display a list of the ReWire equipped applications that are available on your system. Select the application you wish to use, then select OK.

The application you have selected will now load.


Routing AUDIO from the Client application to REAPER

The Main Mix output from the Client application will be automatically routed to the Track you have just used to start the ReWire session.

To check that audio is getting from the Client application to REAPER, load a Project into the Client application, and use either of the following methods to test playback:


Method 1. Record-Arm the Track that contains the ReWire Client

Arming the Track synchronizes the Client application to REAPER. You should now be able to hear the output from the Project in the Client application when you press Play in the REAPER Transport.


Method 2. Insert an "Empty Event" in the REAPER Project

The other method of synchronizing the Client application is to insert an "Empty Event" in a REAPER Track. In the example above, REAPER has automatically matched the Loop settings of the Reason Project. An Empty Event was inserted by selecting Insert > Empty Event, and the edge of the Empty Event was then dragged to match the length of the Reason Project. You can now press Play on the REAPER Transport to hear playback. With this method, the Track containing the ReWire Client does not have to be record-armed.


Routing Multiple Audio Outputs

Multiple Audio outputs can be routed from the Client application to REAPER. Audio outputs are routed via the Audio Outputs tab of the ReWire plug-in.


To enable multiple audio outputs via a ReWire session

1. Assign the outputs in the Client application to individual outputs. The procedure for doing this will vary from application to application. Consult the User Manual for your application for more information.

2. Click on the I/O button of the Track that contains the Client application.

3. Click on the Track Channels down-arrow and select the number of Channels you wish to route.

REAPER supports 64 Track Channels per Track. Track Channels work like an internal patch bay, allowing you to patch up to 64 outputs from any plug-in used in the FX chain of the Track.

4. Click on the FX button of the Track that contains the Client application to open the FX chain.

5. Select the Audio Outputs tab.

The ReWire Output column will list the individual outputs you have assigned in your Client application.

6. Right-click on the Track Channel corresponding to the ReWire Output you wish to route.

7. Left-click to select the Track Channel you wish to route the output to.

8. Click on the I/O button to open the Routing window again.

9. Select the Send(s) you wish to route the outputs to.

10. Assign a Track Channel to a Send by selecting the Track Channel from the Audio drop-down list for that Send.

The number of Track Channels displayed will correspond to the number you selected in Step 3 of this procedure. Track Channels can be assigned as Stereo - e.g. Channel 63/64, or Mono - e.g. Channel 64.

The individual audio outputs from your Client application will now play via the Tracks you have assigned them to in REAPER.


Routing MIDI from REAPER to the Client application

ReWire gives you the ability to use MIDI instruments in the Client application as if they were normal VSTi or DXi plug-ins. You can route MIDI Tracks from REAPER to the Client, or record MIDI Tracks in the Client via ReWire.


To route a MIDI Track from REAPER to the Client application

1. Click on the I/O button of the MIDI Track you want to route to the Client application. In this example, we are going to send the MIDI from Track 6 to the Client.

2. Select the Send to the Track that contains the Client application. MIDI from Track 6 will now be sent to Track 1, which contains the Client application.


Multiple MIDI channels

Multiple MIDI Tracks can be sent to the Client application as long as they have been separated into individual MIDI channels. MIDI Routing is assigned via the MIDI Inputs tab of the ReWire plug-in.

To route multiple MIDI channels to the Client application:

1. Open the FX chain of the Track that contains the ReWire Client application.

2. Right-click on the ReWire Destination for the MIDI Channel you wish to route.

3. Left-click to select the destination from the list.

4. Repeat for each MIDI channel that you want to route.

The MIDI channels will now be routed from REAPER to the selected destination in the Client application.


Main Page > REAPER Documentation