Dr. Octorex – Reason101

66 – The ECHO Echo echo. . .

Today let’s take a nice little look into the world of The Echo. New to Reason 6, this is one of 3 new effects which were much anticipated by the User Community (Do we all remember posts with subject lines reading “We need better effects in Reason”? I do).

You can download the project files here: Echo-Techniques. There are some Combinators and a .reason file showcasing the examples found below. In the .reason file, I’ve used mutes to silence all the tracks. To listen to a track, unmute it. I hope you find some of these tricks useful.

Also don’t forget that my latest Refill, Pureffects, is available with 1,250 effect patches designed specifically with Reason 6 in mind. There’s 200 Echo patches alone, and about 30 or so Echo Combinators with all kinds of interesting routing ideas. For example, ever thought about setting up Kong to “Play” the various “Delay Times” via your pads? Since there are 16 “synched” times in The Echo delay, they are perfect for mapping to the Kong pads. Yup. It’s in there. Read More about the ReFill.

Overview of The Echo

The Echo brings some nice new features into Reason. It’s an Echo / Delay device that can also phlange things around, and purports a new Algorithm to the Echo that you won’t find inside the RV7000. As with all Reason devices, it doesn’t replace anything, but instead adds something new into Reason. So it’s not meant to be a replacement for the DDL-1 or the RV7000 Echo algorithm. They all have their place inside Reason.

One of the nice things I like about the Echo is the “Keep Pitch” button. Essentially, this will keep the pitch as you adjust the Delay Time, so that you don’t get those insane squelches that you get if you were to change the Delay Time in Thor or the DDL-1 devices. This is unique to The Echo.

Another unique offering is the way in which you can control The Echo. There are 3 ways to control it:

Normal: Allows you to use The Echo as an insert or send device in any situation. The Dry / Wet knob determines the amount of Echo produced. This mode is probably the one you will be most familiar with, as it’s the way most effects are set up in Reason.
Triggered: Allows you to Trigger The Echo via the Trigger button or by sending CV to the back of The Echo device. The only thing to remember with this mode is that Any Audio being processed through The Echo will not sound unless the Triggering is enabled. Something that can be a little confusing at first. Honestly, I would have preferred if the Audio was sent through the device dry when not triggered, so that you could still hear the unprocessed audio, and then triggering allowed you to hear The audio processed through The Echo, but I’ll show you a way around that later.
Roll: This is a really nice option when you want to play a stuttering effect on the Audio. The Roll Feature will boost both the Feedback and “Wet” signal as the Roll lever is moved to the right. When this lever is all the way right, both Feedback and the Wet signal = 100%. Fully left, and both Feedback and the Wet signal are 0%. This makes it very useful as a “Freeze” or “Beat Repeat” function.

And of course you have the Color, Modulation, Ping-Pong mode, Offsets for Delay and Feedback, and Ducking. I’m not going to go into all of these features because the manual does a pretty good job of explaining them. Instead, I’m going to show you a few practical ways you can use them in your compositions.

Trick #1: Echoing Slices in a Loop via Parallel Processing

This idea uses 2 instances of the same loop to parallel process the drum beats. One will be the original unprocessed Loop, and the other will have a few slices of the same Loop run through The Echo. It’s a very simple process, but it can be a lot of fun when you’re spicing up your loops.

Start by creating a 6:2 Mixer inside a Combinator. Then create a Dr. OctoRex Loop player and initialize the device. Open up the lower section of the Dr. OctoRex and load up one of your favorite loops into slot 1. Now Duplicate the Dr. OctoRex Loop player. Flip around to the back panel (Tab), and connect the second Dr. OctoRex to Channel 2 (the first Dr. OctoRex should be connected to Channel 1). Flip back to the front, and select the Second Dr. OctoRex. Right-click and select Effects > The Echo. This will automatically connect The Echo as an insert device between the second Dr. OctoRex and the 6:2 Mixer. Perfect.

Now for the important part. Flip to the back of the Rack, and move the output of the second Dr. OctoRex from the Left / Right output to the 1/2 output instead.

Parallel Processing specific Slices in a Dr. OctoRex with The Echo (back of the Rack)

And now comes the fun part. Set both Dr. OctoRex devices to “Select Slice By Midi.” This allows you to see the slice focus as the loops are running. On the first Dr. OctoRex, select the “Slice Edit Mode” button and select the word “Level” in the Loop display area (not the “Level” knob). In the second Dr. OctoRex, select the “Slice Edit Mode” button and select the word “Out” in the Loop display area (not the “Out” knob).

Find a few key slices as the loop is played (Bass Drum is a pretty good choice in most cases), and in the second Dr. OctoRex, pencil in a quarter of the way up over these key slices. You should be hearing The Echo affecting those slices. In essence, the slices you select to be output from 1/2 (a quarter of the way up in the display) will be processed through The Echo. The reason it’s a parallel process is that the original loop is still playing simultaneously. If you don’t want the slices processed in a parallel way, go to the first Dr. OctoRex and reduce the level completely on the same slices you just sent to the Echo. You can introduce a little of the original signal back in by raising this level for the first Dr. OctoRex loop slices, or you can reduce/raise the levels in different ways to add a little variation and groove. It’s a very versatile method.

If you really want to start tweaking things, try transposing the second Dr. OctoRex loop by a few semitones or a whole Octave. If it sounds good, go with it. And when you’re done, save your creation in a Combinator.

Parallel Processing Specific Slices in a Dr. OctoRex Loop with The Echo (Slice Edit Mode)

Trick #2: Using a Matrix to Trigger Echoes

This idea is very basic but shows you how to use the Trigger Mode of The Echo. The idea is to use a Spider Audio to split the signal of a Dr. OctoRex Loop, and have one split going into a Mixer Channel, and another Split processed by The Echo and then sent to another Mixer Channel. Then take a Matrix Pattern Sequencer, and send the Curve CV from the Matrix into The Echo’s Trigger CV input on the back of the device. On the front panel, Set The Echo to “Triggered” mode, and set the Matrix to “Curve” mode. Start the Main Sequencer by pressing the “Play” button, and start drawing in some steps in the Matrix curve. The steps should be draw in at full level, and you don’t need a lot of them. Start by drawing in one or two on a few key beats. You’ll start to hear how The Echo is affecting the loop, so draw in your steps by letting your ears decide where they should go.

Here’s a video that showcases how to set up the above 2 tricks. Don’t worry, it’s really not as hard as it sounds. Once you understand the concepts, you can really have some fun with these methods.

Trick #3: The Echo’s Feedback Loop

Using the built-in Feedback loop of The Echo is something that hasn’t been talked about very much since Reason 6 was released a few days ago, but I’ll bet this will be one area that will get a lot of attention in the coming weeks and months. If not, then it should. The Feedback Loop is one helluva tremendous feature. And it’s really simple to implement with a lot of possibility. The only thing I would advise when you start fiddling with the Feedback loop is to reduce the Feedback of the Echo down to zero before you start connecting devices to it. Also make sure there is no feedback offset either. Keep that knob centered at zero (0). Otherwise you can really destroy your ears if Feedback is set very high and you accidentally connect a Scream to it, for instance.

No doubt someone will eventually do this. And for that poor soul I guarantee it will end up being the last time they do it.

So now that you know the rules of the road, here’s how you set it up:

Load up a sound device, like your favorite Thor, Malstrom, Subtractor, or any Audio Track if you prefer.

Create an Echo device underneath the sound source device (or you can place it inside the Audio/Mix Channel’s “Insert Effects” section). Turn the Feedback knob down to zero. I also turn the Delay Time down to zero as well, but this isn’t necessary.

Hold your Shift Key down and under The Echo device insert your favorite Effect device from the “Effects” subfolder (to make it interesting, select a Pulveriser).

Flip to the back of the rack and connect the Pulveriser’s audio outputs to The Echo Feedback Loop audio inputs (Breakout Input). Then connect The Echo Feedback Loop audio outputs (Breakout Output) to the Pulveriser’s audio inputs.

The basic setup is complete. Now you can flip to the front of the rack and slowly raise The Echo’s feedback knob. I would probably set the knob to somewhere around 20. Then start to play with the parameters on the Pulveriser. Don’t go crazy. Just slowly introduce a few things such as some dirt, filtering and dry/wet blend. If you don’t hear anything too exciting, keep experimenting by turning up the feedback a little more, then increase the dirt and perhaps the squash settings. Try out the various filters.

You’ll start to hear how it all affects the feedback inside The Echo. And believe me, there are hours of fun found just in creating weird feedback loops. I created a lot of different feedback loops inside my Pureffects refill for Reason 6. I even fed a second Echo device through the feedback loop in one patch, and an RV7000 in another patch. Though when you feed delay effects through the Feedback Loop, you really need to mind your manners. As you can imagine, piling delays upon delays can be a recipe for disaster. Though with the right settings, you can produce some phenomenal results. It goes without saying, but I’ll say it again and again: Experiment! Experiment! Experiment!

Here’s the Video for setting up a Feedback Loop in The Echo:

Trick #4: The Zipper Effect

Here’s a little trick to create an off-the-wall sound with The LFO feature of The Echo. I personally like it for a very rapid delay which sounds somewhat like a zipper. So I’m calling it the zipper effect. It’s also very simple to set up.

Here’s a short video on how this is set up:

Trick #5: Automating the Roll feature in The Echo with an LFO

This is another one of those simple ideas that can produce some nice results. Try automating the Roll in The Echo with an LFO. Any LFO will do. You can even use the Pulveriser’s Tremor feature (essentially an LFO) to control your Rolls.

A Subtractor LFO connected to The Echo's Roll CV Input

Here’s a short video on how this is set up:

Bonus Trick #6: Processing a Kong Snare Drum through The Echo

Much like Trick #1, where the Slices are independently sent out to The Echo, you can also set up a Kong Drum Kit, and send specific drums out to The Echo for processing. This video shows how you can set up a Snare Drum to be processed by a Pulveriser and an Echo, while all the other drums are sent out Dry. Once you understand these concepts, there’s no end to how you can process things with The Echo, as well as other effects devices in Reason. Have fun with it!

And here’s a really nice tutorial that Selig put together on parallel processing and sidechaining with The Echo, which I just found the other day. Really nice method to parallel process using nothing more than a single Echo. Sweet.

I hope that opens up some new ideas for those of you using The Echo. Any other ideas, please share them here. Until next time, have a blast with your new Reason 6 upgrade.

52 – Dr.VocoRex: Going Loopy

It’s time for something new and fresh to come out of Reason 5. So I give to you the Dr. VocoRex Loop Manipulator. It’s a bit of a glitch, and it’s a bit of a fun creative way to merge some Rex Loops and a Vocoder together, and provide a few parameters that you can play with and manipulate. So let me know what you think. I’ll show you how to build it below, and then I’ll provide a few Combinator variations. You’re the loop doctor. So let’s start dissecting our patient.

The project files can be found here: Dr-VocoRex-Loop-Manipulators. This is a zip file that contains 3 Combinators that we’ll be building below. I used Reason 5 to build them, and since they use features from the new Dr.OctoRex, you’ll need Reason 5 to work with them. However, try to work on something similar in Reason 4. You won’t have access to multiple loops in a single device, nor some of the CV inputs, but you can still go a long way to recreating something similar. I also included an .rns file so that you could quickly open them both and try them out. For the .rns file, I believe you will need Reason 5.

To start off, you can do a lot of neat things with the Dr. OctoRex via CV, and that’s really at the heart of this tutorial. When you start creating 2 Dr. OctoRex devices with different loops and using a Vocoder to bring them together, things can quickly get very wild and interesting, especially where the CV routing is concerned. So it’s time to put on our CV hats and dive in.

The Basic Setup

Here’s the video to showcase the kinds of setups we will be working to build:

First, create a Combinator and 6:2 mixer underneath. Now create a Dr. OctoRex, Vocoder, and Spider Audio Merger/Splitter. Then holding the Shift key down, create another Dr. OctoRex loop player.
Flip the rack around and send the Left and Right audio output from the second Dr. OctoRex player into 2 left (mono) channels on the Merger side of the Spider. Then send the left output to the Modulation input on the Vocoder.
Flip the rack around to the front once again. Expand the Rex loop players and Add two different loops into the first slots of each device. For the moment, let’s ensure they are both the same speed. So now you have a loop in slot 1 for both devices. The top Dr. OctoRex is what will be played (the Carrier). The bottom Dr. OctoRex is what will be used to modulate the top Rex loop (the Modulator).

For this exercise, I chose the Drb18_Optical_165_eLAB.rx2 for the first Dr. OctoRex and the Drb09_Shadow_165_eLAB.rx2 for the second Dr. OctoRex loop player (both files can be found under the Dr Rex Drum Loops > Drum N Bass folder).

On the Vocoder, set the number of bands to 32. I prefer this band level because it gives a better definition of the sound.
Now let’s get into the CV and play with a few bands in our Vocoder. Flip the rack around and create the following CV connections:

Vocoder (Band 12 CV Out) > Dr. OctoRex (Carrier) Osc Pitch CV In (trim knob set to 127).

Dr. OctoRex (Carrier) Voice 1 Filter Env. > Vocoder (Band 7 CV In).

Dr. OctoRex (Modulator) Voice 1 Filter Env. > Vocoder (Band 11 CV In).

Immediately playing this will yield some interesting results. Now try adjusting the Filter Envelope on both Dr. OctoRex devices. You’ll notice you can get a variety of freaky sounds out of this setup.

The back of the rack showing the two Dr. OctoRex devices used as a Vocoder Carrier and Modulator

All that’s left is to open up the Combinator’s programmer and setup the Rotaries and buttons to gain access to a few crucial elements of these devices. Here’s how I set things up:

Rotary 1 > Vocoder Dry / Wet : 0 / 127

Rotary 2 > Vocoder Shift : -64 / +63

Rotary 3 > Dr. OctoRex (Carrier) Osc. Env. Amount : -64 / +63

Rotary 4 > Dr. OctoRex (Modulator) Osc. Env. Amount : -64 / +63

Button 1 > Vocoder Hold: 0 / 1

Button 2 > Unassigned.

Button 3 > Unassigned.

Button 4 > Unassigned.

Going a Few Steps Beyond the Ordinary

So the next logical step is to add more loops and then set up 2 Combinator Rotaries to adjust the loop slot position of each. This opens you up to 8 different Loops in each Dr. OctoRex device which can be mixed and matched to your liking (it’s like having 8 carriers and 8 modulators; all of which are adjustable.

If you add more loops and then adjust the loops so that they can be tied to a Rotary knob and switched at will between them, ensure the “Trig Next Loop” on the Dr. OctoRex devices are set to 1/16. This way, the jump from one loop to the next will happen fairly instantaneously and without a long delay.

And Now for Something Completely Different. . .

Alternately, you could send all the output bands of the Vocoder into a series of Thors (4 CV bands for each Thor), then use these Thors to convert the CV to Audio and send all the audio outputs to a Mixer (you’ll need 2 14:2 Mixers to carry all 16 audio inputs). Then set up another bank of Thors to control the Level CV of each Channel on the Mixers. Once this is done, send the main audio output through a Spider Audio Merger/Splitter to make the signal Mono, and convert the audio back to CV in yet another “master” Thor. From there, it’s a matter of sending the CV into the Osc. Pitch of the Dr. OctoRex Carrier device. Now you can open the Combinator Programmer Modulation and set up a Rotary to control the “Step Count” (from 1 to 16) of all the Thor Audio devices (set in the “Reverse” direction). This allows the Rotary to cycle through the Vocoder’s “CV out bands.”

Of course, if you use this method, you’re going to need to give up a Rotary. So I would do this as an alternative to adding multiple loops. Instead, use only one loop for the Carrier and another loop for the Modulator. Then you free up 2 Rotaries (Rotary 3 and 4, which were previously used to control the loop slot position of both Dr. OctoRex devices). Apply the Step Count parameter to Rotary 3, and you’ll still have another Rotary (4) to spare, for controlling any other parameter(s) you like.

Then you can set up a series of Thors to control where the CV gets sent back “into” the Vocoder. To do this, you need to again convert the CV into Audio using a Thor, and then send this audio into a bank of new Thor devices, which are set up to determine where the CV source is sent (into 1 of 16 Input bands on the Vocoder). Then do the same thing we did previously on the Combinator’s third Rotary, except this time you’re using the Combinator’s fourth Rotary to control the “Step Count” of these new Thor devices. And there you have it. Rotary 3 controls the Vocoder’s “CV Out” bands, and Rotary 4 controls the Vocoder’s “CV In” bands. Pretty nifty. And it has all sorts of other applications, not just controlling parameters on a Dr. OctoRex. See: This tutorial provides you with more than just another loopy way to play with your loops. 😉

Ok this is a little crazy, but you can control the CV ins and outs on the Vocoder via 2 Rotaries on the Combinator. Here's the back of the rack.

If all of this is making your head spin, just check out the Project files. The third Combinator in the set (Dr. VocoRex 004) is the one that houses this little configuration. So look it over and you’ll see how it’s all set up.

Where do You go from Here?

Well, there’s many different directions you can go. If you’ve set up all the Vocoder CV bands as I did in the last part, it’s a cinch to plug the CV destination (from the Out bands) or CV source (from the In bands) to any CV in/out you wish on the Dr.OctoRex (or any other device you wish to introduce. So try playing around with these CV source/destinations.

You could also introduce another set of Dr. OctoRex / Vocoder devices and have two going simultaneously. Just a thought. And with the new editability of slices in the Dr. OctoRex, you can adjust each of the slices individually.

Or try perhaps to have a single Loop both be the Carrier and Modulator. With the separate outputs, you could have one set of slices modulating another set of slices; all within the same loop. Lots of possibilities.

So these are just a few ideas you can use with 2 Dr. OctoRex loopers and a Vocoder. There’s probably a million ways to combine them together for some awesome results. Why not share a few with me here. I’d love to hear all your ideas. Until next time, happy Reasoning and happy Recording. Go out and make some masterpieces!

38 – Kong as Scene & FX Selector

Calling Kong a “Drum Designer” is like calling a Computer a “Typewriter” — sure that may have been the original intent, but it’s so much more. Here I’ll show you a whole new side to Kong. This tutorial will use Kong as a mini Scene Selector, to imitate Ableton Live’s Session view and then also use it as an Effects selector for any audio you like. In this way, you can switch between clips (Rex Loops) and Scenes (groups of Rex files). We’ll also use one of Kong’s pads to cycle through as many FX as your processor can hold. Hours of fun.

It’s very easy to think of Kong as a “Drum” designer because of course that’s what it is called. And indeed that is its primary purpose. However, it would be a mistake to think of Kong as only a “drum” programmer. That’s like calling a Computer a “Word Processor” — sure that may have been the original intent, but it’s just so much more. Here I’ll show you a whole new side to Kong. This tutorial will use Kong as a mini Scene Selector, to imitate Ableton Live’s Session view and then also use it as an Effects selector for any audio you like. In this way, you can switch between clips (Rex Loops) and Scenes (groups of Rex files). We’ll also use one of Kong’s pads to cycle through as many FX as your processor can hold. Hours of fun.

To start, I’m going to use a Combinator I came up with which you can download here: OctoKong-Scene-Selector-3. It’s a single Combinator inside an rns file. The Kong inside the Combinator has been given its own track because I find it easier to play the Kong outside the Combinator and place all the midi data there, as opposed to sequencing midi data on the Combinator track.

A little Off Tangent: Recreating Ableton “Live” in Reason?

As an aside, I have to give a huge thanks to Dioxide for inspiring the idea behind this Combinator. He wanted to try to mimic Ableton Live’s Scene / Clip system. This comes pretty close and allows you to select between different clips in a mini 9-pad way. The pads along the right side trigger all the loops within their respective rows, while the pads on top cycle through that specific row’s Rex loops (8 loops in total). When you open it up, you’ll have to press the “Run Pattern Devices” button on the Combinator. This sets all the loops running freely. I’ve also set up the first 3 buttons on the Combinator to act as your “Mutes” — so you can mute any of the columns at any point in time. You can also play each loop individually by playing the other pads alone or in combination. In this way, it’s a mini scene/clip selector for Reason.

If you’re interested, here is a 2-part series on how to create that patch:

But moving on, the real focus of this article is that lonely little pad 16 up there in the top right corner. What to do with that little pad all empty and lonely. Let’s add a ton of effects and use the pad to cycle through each of those effects one after the other. Let’s load in as many as your CPU can handle!

Well, actually, let’s focus on the PROCESS to add in as many as your CPU can handle. I’ll give you the tools and know-how to add in a few effects, maybe 4 or 5, and then you can use the same technique to load up as many effects as you like. This way, you can take the FX Pad in any direction you like. Sound good? Ok. Let’s get started.

Adding 5 FX at once, and tying them to the Pad

The basic idea is to send all the FX into a separate Mixer and then back out to the main output. All the levels of all the channels are turned off and CV is used to determine which channel gets heard. The first Channel is the original (untouched) audio without any FX applied. Then you have five different FX applied to the audio chain which goes through the different channels on the mixer. The CV is then sent out from the two Thors and turns up each respective channel to level 100 on the 14:2 Mixer. The Thor Step Sequencer is used to move step by step through the different FX, and the Pad (Pad 16 here) is the main catalyst moving the step sequencer forward.

The main FX setup. Yeah I know it looks crazy. But follow the video and you can't go wrong. Try to understand the concepts, and you can add any number of effects. — The main FX setup. Yeah I know it looks crazy. But follow the videos and you can't go wrong. Try to understand the concepts, and you can add any number of effects.

In conclusion, pad 16 cycles through all 5 Effects devices. And the cool thing is you can create any number of devices inserted into the chain. So if you want to create custom FX devices, you can insert them into the chain in any way you like. You can also create more than just 5 tied to a single Pad in Kong. But I think this shows you a pretty good example of the possibilities. And that’s what I hope you take away from this.

So what do you think? Any other interesting ideas or uses for the new Reason 5 devices. Is it time for me to move on to Neptune? As always, comments here are welcome. And stay tuned for more to come. Good luck in all your Reason projects!

37 – Dr. OctoKong Looper

In this tutorial, I’m going to show you how to use Kong and the Dr. OctoRex together to create some continuous looping fun. You’ll learn how to continually loop and play a series of OctoRex files with Kong. This way each pad turns the loop on and off as a toggle, with Velocity sensitivity too.

You can download the project file here: DrOctoKong1-v4. There are 2 RNS files containing 2 Combinators in this zip file. Both Combinators contain the Kong device and 10 Dr.OctoRex devices. The first rns file shows you ways you can play the loops and switch from slot to slot to cycle through all 80 loops. The second one is an update I did which shows how you can use a separate pad to Re-Trigger the loops at any point while they are playing. Keep in mind that what you need to play is the Kong device, and not the Combinator (though you could play the Combinator if you want to. But it might be easier to lay down the midi note clips on the Kong track so you can see what’s going on inside Kong itself). Also, make sure you press the “Run Pattern Devices” button on the Combinator. Alternately, press the “Play” or “Record” button on the Transport. This ensures everything runs as it should.

To see how this setup works, take a look at the video below.

So here’s the basics of how it all works

You create your Kong device without any audio routings. Then you create a series of up to 16 OctoRex devices, all with their audio routings sent to different channels on a 14:2 Mixer. Load them up with your favorite Rex files, flip the rack around and send the “Gate Out CV” from each pad in Kong to the “Master Volume CV In” on each Dr. OctoRex device. Then press “Run Pattern Devices” on the Combinator to initiate the “Run” button for all the OctoRex devices at once (or alternately, press the “Play” or “Record” button on the Transport), and your pads become a play/stop loop toggle for each of the attached OctoRex devices.

The Routing necessary on the Back to link up the Kong with the Rex files

The front panel of the Combinator and Dr.OctoRex devices - Turning on "Run Pattern Devices" will enable all the Rex files to continuously run

A few notes here:

The way it works is by having the Rex files continuously looping and running. All the Pad is doing is turning up the volume. For this reason, the rex files are free-running and do not re-trigger when the pad is pressed again. But as I said in the video, don’t let this discourage you. It’s still a very simple and great way to play the Rex loops from Kong.
The best way I’ve found to play the loops is by using the Keys from C1 – D#2 on your keyboard. I haven’t tried using a Korg or Akai pad controller to play the loops in this way, but I have a feeling if you do, the pads will end up running the loops continuously without a way to shut them off (you’ll have to press the pad with your mouse directly on the Kong device to stop it again). It’s a little quirky, but I’ve tested the keyboard, and it works great. Press a key and the Rex file sounds. Lift up the key and the Rex file sound stops.
One of the benefits of this setup is that the Pads (or keys rather), are velocity sensitive. The result is that the Rex loop volume can be controlled via the Velocity of your pads. This adds a nice dimension to your loops and dynamics to your sound.
You can setup the Rotaries and Buttons as I did here. For each Dr. OctoRex, you’ll need to set up the following Modulation parameters in the Combinator’s Modulation Bus Routing:

The Combinator's Modulation Bus Routing - Just a suggestion. ;-) — The Combinator's Modulation Bus Routing - Just a suggestion. 😉

Taking things a step further

One thing you can do is load up the other slots of the OctoRex devices, and then tie the Loop Slot to a free Rotary (you’ll have to give up one of the parameters above). This way, you not only have the ability to play multiple loops using the Kong device, but you can also switch slots for new Rex Loops by turning one of the Combinator Rotaries. Add to that the various parameters you can tweak at the slice level of each Rex loop, and you have some very powerful fun at your fingertips.

I decided to go ahead and implement this. However, I realized that there’s a nice little way to keep all our parameter automation in place in the Combinator, and still provide the ability to switch from loop slot to loop slot in all the OctoRex devices. It’s really not too complicated. Here’s a video to show you how it’s done.

The nice thing about this method is that it uses the new CV inputs on the back of the Combinator in conjunction with Thor’s step sequencer and triggering provided by Pads 15 and 16. So you can see how some of the Reason devices can be interconnected and operate together to provide some useful functionality.

The idea that you can trigger 80 Loops (and if you used all 14 pads you could trigger 112 loops!) using a single Kong can be pretty overwhelming, but can provide some interesting chaotic possibilities. And even structurally, you can create some amazing songs using little more than Rex loops. For example, think of having each OctoRex device contain 8 loops related to a single instrument. So the first OctoRex contains your drums, the second contains the basslines, the third contains guitar loops, and so on. You have a complete band that you can switch from verse to chorus with one press of a key or a pad.

Extra Bonus: Let’s add some Effects

Here’s a quick video to show you how to simply add an FX or two. I’ve also updated the main project file so be sure to download that at the top of this post. For now, here’s the method I used to show how to add the effects to some of the free pads. There’s also some Delays and Reverbs on two other pads that you can cycle through (5 delays and 5 reverbs). The cycling is somewhat similar to how the Loop Slot Changers work on Pad 15 and 16, except the audio gets split between a bunch of different FX devices with different settings. I didn’t go over how to set that up, but you can look at the file and figure out the routing. Hope you have lots of fun with this one. I had a really great time making it. And now… the video:

Re-Triggering the OctoRex Loops

This video is an update to the main tutorial above. A big thanks has to go out to EditEd4TV at Bauman Productions for helping me figure out how you can re-trigger all the loops as they are playing. Essentially, it uses the note function of the Thor step sequencer to start the loops from the beginning again. Very cool indeed. I also placed the finalized file in the project file download at the top of this article. So go check it out there. And if you want to know how it was put together, check out the video below:

As always, any comments or suggestions or ways we can improve upon this are welcome. So please let me know what you think and what other ideas you might have. And have fun Reasoning!

35 – Glitch Box Redux (R4 & 5)

In this tutorial, I’m going to show you some new ideas for Glitch Boxes in Reason 4 and Reason 5. Because, hey, we can never have enough glitch boxes or IDM-style sounds. Just like you can never have enough creativity. Consider this a “Glitch Box (Part 2)” for those that missed my first installment.

Download the project files here: more-glitch-boxes This is a single zip file with one RNS file containing both Combinators. Since those with Reason 4 won’t be able to open the file, I’ve included the Combinators separately. Note that one of the Combinators is for Reason 4 and up, while the other one is for Reason 5. Sorry to those who can’t open the R5 file, but you at least get to use the R4 Glitch Box Combinator right?

Glitching up Keith LeBlanc via the Dr. OctoRex (for Reason 5)

I’ll start with the Reason 5 approach, which uses a Dr. OctoRex to apply some interesting variations to a single loop, then copies that loop multiple times into various different slots. Once that’s done, you change all the slice parameters in all the different loops. Then send the 8 audio outputs of the OctoRex to different FX devices (even the Kong FX) and back into the Mixer channels. Using this setup, you could even apply different mastering FX to the different outputs.

Incidentally, I’m using a rex file that’s located in the Factory Soundbank that was created by drummer Keith LeBlanc. I was supremely excited to see some of his material included in the FSB (among other very talented individuals). If you haven’t heard of him; he, along with Adrian Sherwood, Doug Wimbish, Skip McDonald, and even Mark Stewart, formed a group back in the 80’s called “Tackhead” which were revolutionary at the time. I would highly suggest you visit these links and explore them further on your own. While not the first band to ever use samples, they were one of the first bands to heavily rely on them for their music. And they ushered in the industrial hip hop genre which was an amazingly ecclectic mix of genres. Their music may sound a little dated now, but still gets me going. Definitely worth your time to explore. Luckily I have the original “Tackhead Tape Time” LP (yes, an actual original issue LP). But enough about that. Let’s get busy Glitching up Keith LeBlanc!

Once the basic setup is in place, you can go crazy editing all the slice parameters, but pay special attention to the “Out” or “Output” parameter. This is what will send the various slices to the various FX devices. So that’s going to have the most impact on how the slice is played.

Lastly (and this is discussed in Part 3 below), you can set up a few CV sources via Thor devices, and send them to the different FX device CV sources. In this way, you can take the Glitch Box to a whole new level of crazy. Don’t miss it.

Glitch Box (Redux – for Reason 4)

In this second approach, I wanted to give Reason 4 users another way to create some Glitch in their rack. This is an idea I got from delving into the Glitch Box Combinator that comes with the Factory Soundbank. It was an old patch that has been around since R3, and so it uses a few NN19s hooked up to a 14:2 Mixer, and the mixer levels are triggered by the Redrum CV Gate outs. In this one, I update the idea by using a few Thor devices. You can really have a lot of fun using a few different Wavetable oscillators, and changing around the LFO2 Wave types and rates between all the Thor devices (this is something I neglected to do in the video below, but I would think it would produce some interesting variations). Anyway, this method can be used in R4 and above and is for all those who haven’t yet purchased Reason 5. But seriously, what are you waiting for?

So does anyone else out there have some good glitch ideas or know ways in which these combinators can be improved? Possibly adding some mastering or Reverb before they hit the mixer is one thought I had. Any other ideas?

Reason 5 / Record 1.5 Overview

Reason 5 and Record 1.5: An overall 6 out of 10. Bottom line: The updates improve workflow, but there is nothing here which is earth-shattering, and very little that you can’t already do with Reason 4 and Record 1.0.1. Still, I’ll end up buying the upgrade because I’ve already invested $850 in the software. So what’s another $129 right?

DISCLAIMER: This is an opinion piece. This is an editorial. This is my view of the software while it is in the beta testing stages. The software is not yet finished or finalized. I take full responsibility for my opinion. But please let’s be crystal clear on this: Your rating and thoughts on the subject of the software may be completely different than mine. You may see this software as the second coming of Christ and it may bring you to the heights of orgasm. You may run out into the street totally naked yelling “This is it! Finally. It’s here! It’s here!” If that’s your thing, great. Send me a postcard from jail. I’ll be working on Reason & Record at home, as I usually am.

This is my view on the software as it stands right now with what information I have about it currently. This is based entirely on public knowledge of said software. If you agree with me, then great. If you disagree that’s ok too. Once this software is released, more than likely no one’s going to care about our opinions anyway. The time is now June 17th, 2010. All names have been changed to protect the innocent.

So here’s the talk of the town lately: Reason 5 / Record 1.5. And in case you don’t want to read through my rant, let me give you the lowdown right upfront:

Dr. Rufus Rex, the 8-legged animal: 5 out of 10

Bricks: 4 out of 10

That Roman Sea God (there’s always a deity involved): 6 out of 10

That live audio import thingamajig: 6 out of 10

King…. well you know.: 7.5 out of 10

. . . and more (secondary features): 7.5 out of 10

Overall: 6 out of 10

*(you did read that bit about names being changed in the disclaimer right?)*

To be fair, if you are a musician who cares nothing about Sound design or if you’re brand new to the program or you care more about making your workflow faster, then these ratings may be somewhat higher than mine. But for me, that’s it in a nutshell. Now will I purchase the upgrade. Sure. Why? Because I’ve already invested $850 in Propellerhead products and an extra $129 — even for the lackluster features — is not going to kill me. When you’ve run 14 km in a 15 km race, what’s one more mile?

I’d rather not be so nonchalant. I’d much rather be jumping for joy and bursting at the seams like I was for Thor. I’d rather be itching to get my hands on the new Kong features, but somehow that’s just not happening. We’ve seen Kong before in Live’s new drum setup. We’ve seen blocks in the form of scenes. And what is Octorex really trying to do? It feels like they took out your Grandfather’s car and are busily polishing it up to be sold as a fresh new idea. Sure, I love the vintage look of the thing, and I love how it rides. But can we kick-start it into the year 2010? To be fair, blocks is starting to grow on me. And Kong is definitely better than I expected, and it’s a very welcome addition to the software.

Don’t get me wrong. I love Reason. I even love Record. I love that I don’t even need to open up Reason anymore. Just launch Record and everything is there for me. Great. But where is the “wow”? I sure didn’t see it come to me in 5 days of anticipation when they were unveiling. It just kind of left me scratching my head.

Where is Recycle integration? I had to go out and buy it separately because I want to put some rex files together. And where are all those wonderful ideas turned into reality that we’ve all been adding to the Propellerhead feature suggestion forum? The ideas keep piling up. And this is the best they’ve got? Perhaps I have more faith in their programming skills. After all, they haven’t disappointed in the past. They did give us Thor after all. So maybe they’ve set the bar too high in the past that now they just can’t live up to their reputation? I don’t know for sure. I just know I expected so much more. And if I’m reading all the forums correctly, so did you.

Revisiting the Wishlist

So I went back to my old post (here it is if you need a refresher: My Reason/Record wishlist) and I looked to see how much of my dreams will actually come true in September. Green shows features implemented in Reason 5, Purple shows features partially implemented, and Red indicates those things which have not been implemented.

First, Record:

Automatic Routing of the Reason mixer channels to the Record Main Mixer. Somewhat there with Record 1.0.1, however this could still be improved because routings through spiders/mergers and Redrum / NN-XT individual outs are not handled correctly.
Comping for Midi as well. Nope. No improvements here.
Split Performance Controller Data into Separate Lanes. Nope. No improvements here.
Record Performance Controllers as automation. I think we got this with Record 1.0.1, so kudos!
Tempo automation/changes on a per-track basis. Well, you can timestretch audio clips. So I’ll say this is halfway there.
Display Masked Audio portion in the Audio Clip. Nope. No improvements here. Right now, there’s no visual indicator to show how far and wide the masked area is. It’s worthwhile to note that this is already pretty much implemented in the audio comp tracks. Now if we could bring that into the main arrange view, we’d be golden.
Synch Reason / Record Favorites. Nope. No improvements here.
Cut Note Events in the Clips. Nope. No improvements. Sometimes you DO want to split the notes, and sometimes you don’t. Provide us with the option to split the notes or not when splitting clips apart.
Scale Transposition of Notes. Nope. And this one is not difficult to do. This is imminently more useful than chromatic transposition of the notes.
Multiple Left and Right locators. Nope. No improvements here.
More Training/Tutorials and videos included in the user documentation. Documentation is starting to improve. Microtutorials, James Bernard video series. Glad to see this getting better! Green light on this one.

And now for Reason:

Adding some new Effects, especially a glitch box such as “Glitch“ Nope. Not there.
Having the ability to Randomize the entire Matrix or Redrum device with one click of a button. Nope. And for this one, I’m truly saddened. Especially since almost all their changes for Reason 5 are simply workflow improvements. To miss out on this one is nuts frankly.
Combinator updates: More CV connections and a better subdivided menu system get a big thumbs up from me. I would still like to be able to switch the rotaries from “pot” mode to “step” mode. But that’s a minor nit-pick. Kudos again!
Integrate ReCycle into Reason (or Record). Come on guys. Seriously! Big thumbs down! When is this going to happen already? Give us sampling without the ability to slice stuff up makes you look money-hungry; holding onto Recycle like an old dog clutching a tattered bone.
The ability to reverse midi and audio for backward playback. Yes. Beautiful!
Tap Tempo. Thank you!
When in edit mode in the sequencer, providing the ability to move notes from one clip into another. Yup. This one is added in Record 1.0. Sweet. However, I’m only giving half points here because it’s not currently available in Reason. If this makes it into Reason 5, I’ll give it the green light.

So 4 out of 18 of my original requests made it in, and 3 are halfway there. A little over 1/3 of my features made it in. I don’t think that’s too bad. You be the judge. To be fair, there may be more to remove from my list once Record graduates to 2.0, and I will say that a few things which made it into this update I’m very glad to see and would have had on my list if I had given it more thought. To name a few:

Neptune. I really can’t wait to get my hands on this and seeing what can be done with it from a sound design perspective. Routing Thor through it and using it in an experimental way should be really interesting.
Kong. Although I’m less than thrilled with the implementation — It feels cluttered with all the mini-fx machines and just doesn’t look very intuitive — I’m eager to explore some routing possibilities on the back of the device. Perhaps that’s just my nature. And I am glad to see some modeling synthesis introduced. But a Guitar modeler is really what I’d like to see more than anything. Perhaps the Props are testing the waters and we’ll see this in Reason 6.0?
As said before, the Combinator update with new CV and easier menu system. Yes. Thank you lord. Finally.
Sampling. Sure. Great. But I have a field recorder, so is this really adding to my toolbox? Not really. Sure it’s handy. But I’ve already got a workflow for this. Still, it’s a feature that’s been wanted by many, so I’ll add it to the “glad to have it” pile.

In case you didn’t know. . .

And for those that didn’t know, don’t forget to read the fine print. There’s lots of little additions to the program that you may have missed when you were enthralled with the Big 5. Some of these surprised me in that they are not hyped more. The extra CVs in the Combinator are a huge deal and should be up there in lights. However, these are the features that are relegated “second class citizen” status. You should read them nonetheless: Secondary updates to Reason/Record.

Of course, don’t forget to check out the videos from the Props home page below, and judge for yourself if these new updates are worth your money. Most of the updates are helpful to improve workflow. But bottom line is that there is nothing here which is earth-shattering, and very little that you can’t already do with Reason 4 and Record 1.0.1. My overall take is that there are three camps:

If you are a sound engineer and have invested in purchasing both Reason and Record, then it’s probably worthwhile to upgrade.

If you are a new hobbyist or musician who has only invested in Record and/or Reason, you may not need the update at all and might be better off sticking with what you have (which is already a very powerful system).

For people working on Live recording only and who only own Record, then the only advantage is Neptune. And honestly if you’re in this boat it’s probably not worthwhile.

What’s your take on the Record 1.5 and Reason 5 package?

http://www.youtube.com/watch?v=cBdy0aTW5YI&feature=related