

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.
#MIXBUS 32C V5 UPDATE INSTALL#
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.
#MIXBUS 32C V5 UPDATE DRIVER#

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.
