![]() You are also free to send an audio track directly to Mixbus by sending it directly to a ReaRoute channel(s). Note that you can send individual tracks that are not in a folder association directly to one of the bus tracks in order to bypass the folder track’s VST processing. Now all of the audio you have running on the bus tracks is also running out of Reaper via ReaRoute and can be use by Mixbus. Based on the way I have Mixbus configured, these two channels will end up on Track 1 in Mixbus (which I’ve pre-labeled DRUMS).Īssign a pair of ReaRoute channels to each of the bus tracks. For 13 *DRUMS*, the track’s routing dialog box section Audio Hardware Output is set to ReaRoute 1 /ReaRoute 2. For example, 13 *DRUMS* receives from 4 DRUMS_FLDR ![]() Receive from one (respective) folder track.*** Eight Tracks dedicated to sending “Bus” tracks to MixbusĮach of these pre-configured tracks, which play no other role than sending audio out to Mixbus via ReaRoute, have no VSTs and are setup with default settings except for the following: I have each folder track preloaded with VSTs and AB Level Matching. For example, track 4 DRUMS_FLDR is set up to send to track 13 *DRUMS*. Ğach folder track is configured to send to its respective “Bus” track.Master send is deselected (because we want the signal to go to Mixbus, instead of Reaper’s Master bus).Keep reading to learn how to configure the routing.Įach of these tracks, which become parent folder tracks once we move individual audio tracks in and associate them as children, have the following presets in their routing dialog box: In this configuration, this is not desirable if your aim is to pass this track through Mixbus. Note that any tracks that you do not associate with a parent folder track will play audio directly out of Reaper’s Master bus by default. A chain for the snare, another chain for Lead Vox, etc. A vocal track would go under VOX_FLDR, etc.ĭifferent FX chains are applied to individual child tracks as needed. Handy for importing individual files or for performing an import of multiple tracks at once.Īfter renaming, each of these tracks is relocated under one of the folder tracks as a child. *** Two Tracks for Importing audio files. Reaper (actually ReaRoute) MUST be started first before you start up MixBus.If you don’t do this, the numbering of the ReaRoute pairs is not intuitive. To display the ReaRoute channels properly, go to Preferences|Audio and deselect "Show non-standard stereo channel pairs." (Thanks to VinodXAgent!).Then when I ran Reaper 64-bit, ReaRoute showed up in Mixbus. The fix (believe it or not) was to install Reaper 32-bit in its default location. However, when I ran 64-bit Reaper, ReaRoute did not appear. I’m currently using 32-bit Reaper, and ReaRoute shows up as expected in Mixbus.Make sure your ASIO driver is updated, preferably the one that shipped with your audio interface.If unsure, reinstall Reaper and select the ReaRoute option. ReaRoute supports the same number channels simultaneously back into Reaper.īefore getting started, here are some things you need to do: ![]() This implies a total of 12 stereo channels or a combination of mono and stereo channels. It appears that ReaRoute can send up to 24 mono channels out of Reaper to another compliant application. You can solo and mute freely on the Mixbus side. Note that the ability to solo tracks within Reaper may not work as expected as long as you have Mixbus connected via ReaRoute. This guide was written against Reaper v5.24 (32-bit) and Mixbus 3.4.13 (32-bit) on Windows 7 (64-bit). You might choose to route items in a simpler way. The scenario described adds some complexity on the Reaper side to mitigate gain staging problems, especially in larger multitrack projects, as I prefer to gain stage carefully before sending the signal over to Mixbus. ![]() Once you understand the routing, you can route however you please. You’ll set up eight stereo channel ReaRoute sends from Reaper to Mixbus, and a two-channel, summed, stereo send from Mixbus’s master out, back into Reaper. This attempt at an end-to-end guide demonstrates a scenario where you edit/mix in Reaper and mix/sum in Mixbus (while monitoring from Reaper), and print the Mixbus stereo output to a track in Reaper as a last step before mastering. Using Rearoute, you have the flexibility to assign any track within Reaper to any track within Mixbus, and return any track within Mixbus to any track within Reaper. You can simultaneously edit and mix in Reaper, and add additional mix flavor in Mixbus as you work, effectively using Mixbus as another “plugin” within Reaper.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |