Wednesday, May 1, 2013

"Reason has a rack for that"

Reason 7 is finally here.

I guess some of the new features are too obvious and simple to understand why they are so great.

Channel bus/groups, parallel channels ad-infinitum, Spectral EQ controlling the good "old" channel EQ, audio auto/manual slicing and quantizing, the list goes on... there's even a bonus Instragram-like audio "toy" that... is no toy at all when in the proper hands ;)

But the thing that many were also waiting for years was Reason ability to output MIDI from the sequencer in a proper, easy to configure, easy to use and easy to understand way.

External MIDI Instrument

Reason 7 finally brings us the "little" External MIDI Instrument rack device (EMI for short).

Obvious use? Play your hardware synths :) ...old, new, vintage, digital, analog, mono, poly, big or small MIDI controlled audio generating gadgets, your OP-1's, your... iPad synth apps... even your 2nd laptop running any MIDI playable music app ;)

Not so obvious use? Control any MIDI enabled gear like mixing desks, FX or light boxes, sync/slave them to your Reason sequencer while performing live on stage.

Less obvious uses? Play/Control your soft-synths/virtual instruments through loopback virtual MIDI ports.

You can play/control them either as Standalone synths or using DAWs/Hosts as VST/AU "racks", allowing you to access more than 1 instrument at the same time either through MIDI Channels (1 per instrument) or using various (virtual) MIDI ports (each allowing 16 MIDI Channels)... whatever you DAW/Host allows.

As an example, Kontakt allows stacking instruments and assigning a MIDI Port+Channel per instrument and this is how you're able to play a specific one from Reason, sending MIDI to the respective MIDI Port+Channel pair.

MIDI Clock & Song Position

Besides sending out Note ON/OFF, Note Velocity, Program Change, Channel Aftertouch, Pitch Bend and MIDI CC's (CC 01 = Mod Wheel), Reason 7 makes it possible now to send out MIDI Clock and Song Position.

Keep in mind that EMI enables you to "convert" CV to MIDI CCs, which is kinda cool... playing iPad's Animoog with a Matrix, RPG-8, sequencer track or through the controller keyb while controlling its X/Y pad with Pulsar is always something kinda neat to do ;)

So, sending MIDI Clock out allows us to sync Reason's sequencer Tempo with any external (hardware or software) gear/instruments (or DAWs) that support MIDI Clock input.

This is how you're able to sync your external synth's Arpeggiator, LFOs or step sequencer with Reason's BPMs :)

Here's a quick example of sync'ing an external (software) instrument through MIDI while also playing it through MIDI (video by sinnerfire)

Besides MIDI Clock, another useful info being sent out is Song Position, extremely useful when controlling Rhythm/Drum machines, Sequencers or DAWs that support Song Position (some don't, you'll have to try it or check the specs list).
TE OP-1's Tape mode receives Song Position, so it's possible to sync its "Tape" position with Reason's Sequencer position :)

«Right, so I'm able to play other instruments not on Reason's rack through MIDI but that's not saved into my Reason song!!!»

Well, just like a singer's voice, a guitar or any other acoustic, electric or electronic instrument that you want to add to your Reason song, you need to audio record that performance to become a part of your song as audio tracks, right?

So you'll need to do the same with any of those External MIDI Instruments played by Reason. If you want to capture that audio performance and embedded it in your song, the definitive way to achieve that is to record that instrument audio output into a Reason audio track. Kinda obvious, isn't it? ;P

External hardware instruments are usually a no-brainer: You connect their audio output into your computer's audio interface inputs and record that into an audio track and you're done. Then, just mute the original MIDI source track and keep it just as a backup, in case there's a need to make some changes or tweaks to the MIDI track and re-record that instrument back into another audio take.

So, my Novation X-Station, my TE OP-1, my iPad or even my 2nd laptop running whatever MIDI enabled instrument apps I have, all fit in the above category of easily getting their audio into a Reason audio track, through real audio cables.

Windows users, as a last resort, can also try using their internal audio card through ASIO4ALL, connecting your computer's audio output to your external ASIO audio interface through a cable... as a last resort, keeping in mind that you won't get any miracles regarding audio latency, this way.

«What about all the virtual instruments, soft-synths (VSTs/AUs/Standalones) or DAWs running on the same computer I'm running Reason on?»
Well, this is where it may get a bit complicated (or not), depending on your system, your overall setup, gear, OS, etc...

In this case, the closest to "external hardware" scenario is using 2 audio interfaces.

In my case, I use Propellerhead Balance with Reason and Novation X-Station (that is also an audio interface) as my secondary audio interface.
With this setup, I have the X-Station's audio output connected to Balance on Line 1 through a pair of audio cables and that's how I'm able to record into Reason any soft-synth, DAW or the X-Station's own synth engine into Reason's audio tracks. Kinda straightforward, right? :)

The other option closest to the above is using your ASIO driver's capabilities to re-route audio internally achieving virtual connections between the driver outs into the driver ins... if you're lucky enough to own such audio interface with such capabilities.

I think Focusrite Saffire is an example of such type of audio interface (I never used one, so I'm not sure about this)
EDIT: Just found out that some Focusrite Scarlett interfaces also allow and include this Mix Control application.

The 3rd option is... using virtual audio cables with various good or bad results, depending on your OS and computer capabilities.

This is where Soundflower is mentioned for Mac users, JACK or Virtual Audio Cable for Windows users.

«Does it work ? Can I really use those virtual cabling "hacks"? Is that a reliable way to work properly?»
Maybe for Mac users that usually use CoreAudio's built-in audio, Soundflower is a good solution, but for Windows users, used to real ASIO hardware audio interfaces, you'll notice the drop in quality quite easily.

I've tried JACK a long time ago (so I won't bother retrying it now again) and it wasn't up to the standards I expect of an ASIO level audio interface. Also tried VAC 4.12 yesterday on my 2nd laptop (just a Core2Duo, unlike my main i7 laptop) and it kinda works but, just like JACK, at a very low quality and high latency settings and... not worth the trouble, to be honest.
For me, the best results are achieved with proper hardware audio (ASIO) interfaces and since I have 2 available at all times, that's exactly what I've been using and am happy with :)

If you need (virtual) multi-channels out of a a DAW or standalone synth application into Reason, technically VAC 4.12 can deal with up to 3 wires (i.e. IN-to-OUT) connections of 8 channels each but... like I said, you'll need a lot of CPU power and be extremely lucky and/or knowledgeable to make that bearably work. So not worth the trouble, IMHO.
If you really need inter-app multi-channel audio exchanges, stick with the ReWire technology.

Maybe Reason 8 will strike one of the last surviving ultimate requests for Reason: ReWire Master and then yeah, all we need is a ReWire slave VST Host to tackle this problem properly completely inside-the-box ;)
(*cof*cof* and Video Track(s)!!! *cof*cof*)

If all these "hacks" sound (or act) too troublesome for you, I guess the truth may be that you don't need them anyway. Stick to Reason, stick to Rack Extensions, stick to ReWire and enjoy that easily understandable and stable bliss ;)

Bottom line is... Reason 7 now allows both worlds to be happy: The "the box is my oyster" crowd and the tweakers, tinkerers, hackers, hardware fans to finally properly marry Reason with that other aspect of their music loving interest :)


  1. Greetings!

    I've been googling this for some time now but haven't found a definitive answer.

    Is it possible to do this in Reason 6? I've been searching all over and I keep seeing people reference doing it in 6 but no-one explains how or actually confirms it.

    My predicament might even be simpler than all of this. All I want to do is be able to record my Arturia synths in Reason. I'm not as worried about the midi data as I am just recording the audio. I have a multi-channel sound-card and I've considered attempting to route the Arturia out and back in to an available input and recording from that input in reason. Seems like it might be possible but maybe that would be too easy. After all, if the keyboard was controlling the Arturia then I'd have to disable it in Reason while I do that...Thinking out loud..

    Anyway, I figured I'd ask you after seeing your videos regarding version 7 on youtube and I figured you'd be the best person to ask. So.. is any of this possible with Reason 6?

    Thank you,

    1. IHi,

      I'm suspecting you're talking about Arturia's *soft* synths (or any other sound source application inside the same computer also running Reason) ?

      If so, as I mentioned in this blog post, there's 3 ways you can record a sound produced by an application (a soft-synth) on your computer into another application (Reason) running on that same computer:

      1) Use 2 audio interfaces. Interface A's audio output physically cabled to Interface B's audio input. Then the audio source app (the soft-synth or DAW) uses Interface A to output while the recording app (Reason) uses Interface B as its main ASIO interface.

      2) Some audio interfaces allow doing this audio loopback inside themselves, logically, without a need to do it phisically with cables. I references a couple of those in the post above.

      3) Do it virtually, through virtual (non-physical) audio interfaces through an application that allows that and also supports multi-client i.e. allows more than 1 audio application to take control of that (virtual) interface. These allow that same audio loopback from one app's output into the other app's input but all happening virtually, inside your computer.

      On Windows, I've never had any good examples of this 3rd option. Nothing I tested worked properly... until recently, when I found VB-Audio Software's Voicemeeter plus its Virtual Audio Cable products.

      Using a combination of their VACs and Voicemeeter "Banana" allowed me to finally use this 3rd option although only @44.1Khz reliably.
      Before this, I used the 1st option, through 2 physical audio interfaces.

      Explaining how to achieve this 3rd option with Voicemeeter is, in itself, a major task that I won't be able to do on a simple comment reply, so I'll just share here their URL and hope you'll be resourceful enough to find your way around it :) ...if not, there's always the 2nd option, if you're lucky enough to own an interface with internal loopback capabilities (I wasn't) or... use 2 interfaces (the 1st option).

      Good luck!

    2. Yes, I'm using Arturia's standalone VSTi synthesizers. And I know you mentioned several methods but since the post was specifically about Reason 7, I wasn't sure. I'm new to Reason and I couldn't find a single source of confirmation online that older versions could do this sort of thing and I haven't had the opportunity to try it at home yet. Anyway, this is the most informative post I've found on this topic yet and I appreciate it. Thank you!

  2. After several months of testing I have made the following conclusions:

    I tested with a Focusrite Scarlett 18i20 (2nd gen) and an M-Audio M-Track Eight. I also made use of my old M-Audio Delta 1010LT (which was a rock solid interface in Win XP).

    One thing I knew already: Audio interfaces don't play nicely with two different audio programs trying to make use of the interface at the same time, for example Arturia Soft Synth's and Propellerhead's Reason. I know that I could run Reason as a Rewire into Ableton, but I really don't like that workflow. At all. What I wanted was one audio interface that could handle Reason and Arturia running side by side. I would route Arturia to outputs 3/4 and back into inputs 3/4. I wanted to use 96khz with as small sample size as possible. For this purpose, I built a brand new 8 core AMD machine with 16GB of ram and SSD for the OS (during testing all audio files were on SSD to get maximum data transfer). In addition, I performed all of the PC optimization tricks that I could find on the internet, including those posted by focusrite themselves.

    What I found was the Focusrite 18i20 (2nd Gen) just wasn't very stable. It could handle only one audio app at a time without clicking and popping. Even on its own, (running a very intensive template I created) Reason with the 18i20 at 96khz and 128 samples wasn't 100% stable. When I bumped it up to 512 samples, it was only enough to note that it "seemed stable". But the pops and clicks were so prevalent in previous settings that I expected them any time. I didn't have faith in it being click and pop free. DSP usage was very high. In the end, the brand new 2nd Generation 18i20 was NOT capable of running Arturia and Reason at the same time in a real life multi-instrument-multi-track project. I even tried some tricks involving ASIO4all and it only made things worse. Buggy drivers. Bad results.

    The cheaper, less sexy and "less capable" M-track Eight performed significantly better. I was surprised by this. I could run both Arturia and Reason simultaneously at 96khz and 512 with very minimal clicks and pops. When I changed the Arturia to ASIO4ALL drivers pointing to the M-Track Eight, I couldn't detect any clicks/pops. I recorded a short session using the most intensive project template I had and then solo'd the Arturia track and initial results from this morning were click and pop free. DSP usage was still pretty low. M-Audio has very stable drivers. You can even select different rates with two different audio programs and it works. I couldn't do that with the 18i20. Not only that, you can bypass the pre-amps in the M-Track Eight. You can't bypass them in the 18i20. So I can use the higher end pre-amps from my analog mixing board (or any external pre-amp for that matter). More bonus points for the cheaper and less sexy interface!

    As far as my old Delta 1010LT, unfortunately it doesn't like Win 7x64. I was really bummed about that, this interface was absolutely rock solid in XP. Granted, you couldn't use two audio apps at once very well with it (you sorta could but it was buggy) but I ran it at 96k and low samples for about a decade with zero issues! I wish I could have brought it along with my new PC build, but it's time to move on from XP, I guess.. I blame Arturia for making such damn good soft synths and Reason for being a necessity. I require Arturia in my instrument lineup but it won't run in XP. Reason 6 does but its missing some features I rather like in the newer version. So here we are in December 2016 and I'm finally giving up on XP and my old reliable Delta 1010LT. It was a good ride.