Create an External MIDI Instrument device, and choose your internal MIDI bus on its front panel. Reason can now treat Reaktor much like a hardware instrument, as in the main screenshot. Clock is being sent to Reaktor, and MIDI received. MIDI inputs need to be switched on in Reaktor in the Audio and MIDI Settings.Ģ: MIDI Settings in Reason. Windows doesn’t have this functionality built in, but you can add it for free with LoopBe1, or for multiple ports try LoopBe30 (or some of you may already use the alternative MIDI Yoke). If not (or if you want to make more) open the MacOS Audio MIDI Setup utility, switch to the MIDI device view, then double-click on the IAC Driver icon. There’s usually an IAC bus available on Macs by default, called Bus 1. On the Mac this is pretty simple using IAC (Inter Application Communication) buses. To control Reaktor directly from Reason, you’ll need to route MIDI to it. Mac users also have the option to use Soundflowerbed, which can route audio from apps using Soundflower to hardware interfaces. On Windows this can be handled by ASIO4All. On the Mac this is done by creating an Aggregate Device in the Audio MIDI Setup utility. You need to use an Aggregate driver that combines your hardware interface and the virtual connections. Reason doesn’t allow you to select different audio devices for input and output, so it takes a bit of thought to be able to route the internal input and still output to your monitors. These all add virtual audio devices to your computer that can pass audio between applications. To route internally you’ll need to install Soundflower on your Mac, or either VB-Audio Virtual Cable or LoopBeAudio on Windows. Remember to click the green input monitor button. To monitor and capture the audio from Reaktor you need to create an Audio Track and choose those inputs. While you’re in the there, set the latency as low as you dare. Audio output and routing in Reaktor is selected in File / Audio and MIDI Settings. I have a single AES I/O pair on my interface that I only ever use for routing between Reason and other apps: one cable, nice and neat. Many interfaces have some digital I/O on board that often never gets used. To go the external route you’ll need a spare pair of outputs and inputs on your audio interface. Internally it can be more flexible, but is more fiddly and can sometimes incur more latency. Audio routing between applications on one computer can either be done externally (going out via an audio interface then back in again), or internally via certain third-party utilities/drivers. However deep you go with Reaktor, as a minimum you’ll probably want to record audio from it into Reason, so let’s start there. And then there’s all the awesome internal sequencing possibilities in Reaktor, especially in Blocks, which can be enjoyed if you synchronise its clock with Reason. If you want to record and edit parts in Reason’s MIDI tracks, or sequence Reaktor from other Reason devices, you can route MIDI between Reason and Reaktor. In this case you just need to figure out how to get audio from Reaktor into Reason. You could simply treat Reaktor like a stand-alone instrument and play it directly from your keyboard. There are different levels of integration you can employ when using Reaktor with Reason. The settings and menus are the same for all the NI plug-ins, as well as Komplete Kontrol and Maschine. For clarity, let’s stick with one plug-in here: Reaktor. Alternatively, if you have Komplete, you can use Komplete Kontrol as a shell for running your virtual instruments (see the box). What makes the NI instruments great for working with Reason is that, unlike many plug-ins, they can run as stand-alone apps. This month I’ve brought together a bunch of tips for getting started working with these alongside Reason. In particular Reaktor and other Native Instruments plug-ins have been staples in most of my musical efforts. That said, even with Rack Extensions enriching the ecosystem, there are still other plug-in instruments that I can’t live without and that I sometimes want to use in Reason. The basic install has most of what I need, it doesn’t need relentless plug-in and library maintenance, and it’s guaranteed to still open 15-year-old song ideas that I should really have given up on. I love that Reason is a self-contained toybox. We show you how to use Reaktor within Reason. 1: Reason running alongside Reaktor 6, with internal MIDI and audio connections.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |