Gate – Reason101

Echodile Deluxe

Here’s an interesting patch that I submitted to the productspecialist@propellerheads.se email in response to their first video in the “Reason Sound Design” series, a new series put out by the Propellerheads to help us all learn a little more about the Combinators inside the Factory Sound Bank, and allow the user community to submit their patches. I love it when they launch a new series!

Here’s the original video in case you’ve been living under a rock and don’t know about this new series:

So without further ado, I give you my humble take on this type of technique. . .

The 4-Way X-Fade Echodile Deluxe

Download the .reason file (example) and Combinator patch here in zip file format: echodile-deluxe.

4-Way Crossfade Echodile Deluxe — 4-Way X-Fade Echodile Deluxe

First, here’s a video to showcase what the Echodile Deluxe sounds like:

An explanation of the Controls:

Pitch Bend: This is connected to the Echo Envelope.

Mod Wheel: Connected to the Delay R Offset

Rotary 1: This rotary crossfades between 4 different Alligator Patterns, and is really the heart of the whole thing. It allows you to blend any two of the four Alligators together using a single Rotary. Ed Bauman came up with the idea of using the Thor’s Shaper set to a Sine wave to fade between four different Mixer Channels. If you want to know more about this little trick, I wrote about it here. So in the interest of full disclosure, I wanted you to know this was not my own idea. A good artist mimics, a great artist steals. According to Picasso anyway.

Note: In order to have all four Alligators Crossfade properly, you will need to either press the “Run All Pattern Devices” button on the Combinator, or press “Play” on the Transport first. Otherwise, the CV-based Thors’ step sequencers won’t start running, and that’s necessary to let the signal pass through them.

You’re also not tied to using these 4 Patterns. You can, of course, change them around to your liking, or else load completely new Alligator Patches into each of the 4 Alligators. In this way, you can really make this device “your own.”

Rotary 2: Echo Feedback. Simple enough. Mix / Max values are 0 / 72

Rotary 3: Shift. Allows you to use the Shift knob of all four Alligators at the same time.

Rotary 4: Delay Time. I ran out of Programmer assignments for the Echo unit, so I had to route this through the P-Pongy Thor’s Rotary 1 and send that into the Delay Time CV on the Echo. So you won’t see the delay move visually on the Echo.

Button 1: Freq. Shifter. The LFO from each Alligator is split out to all three filter frequency bands on the respective Alligators. This way you get some further Filter modulation if you want it. Turns it on or off.

Button 2: Smear. I love this little button. It cranks up the LFO in the Echo to give it a really nice gritty electro quality. Sweetness to my ears.

Button 3: Pingy-Pongy. Turns the Ping Pong of the echo on, but also wobbles both the Ping Pong Panning as well as the Feedback Offset R knob, based on the settings in the Pulveriser.

Button 4: Delay Time Sync. Turns on the sync.

Hope you guys have fun with it! 😉

69 – All about the Alligator (Part 2)

Let’s continue with the Alligator and find a few other tricks that it can perform. In the first part, I looked at how the Alligator works, and provided a few ideas for how to work with it. In this part, I’m going to get a little more practical and show a few new ideas you can incorporate into your tunes. Hopefully this will provide you with some new creative inspiration.

You can download the project files here: alligator-techniques-part2. 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 Alligator patches alone, and several Alligator-based Combinators with all kinds of interesting routing ideas. Read More about the ReFill.

So let’s continue where we left off last. . .

Technique #5: Using the Alligator Effects without the Gates or Filters

After I wrote the first tutorial, it occurred to me that you can use each part of the Alligator independantly. For example, you can use the Gates only, without the Filter and Effects section. Or you can use the Filter section only, while keeping the Gates continually open. And lastly, you can use the Effects or Mixer sections only, if that’s all you want to use (Drive, Phaser, Delay, Pan, Volume). The way to achieve it is as follows:

Start with “Technique #2: Keeping your Gates Open.” To recap, you set the pattern to #60, and ensure the Amp Envelope Decay knob is set to 127 (fully right). Then flip to the back of the Alligator, and send Gate CV Output 1 to Gate CV Input 3, Gate CV Output 2 to Gate CV Input 1, and Gate CV Output 3 to Gate CV Input 2. This way all your gates are Fully open.
Fully turn down the volume of the High and Band pass filters. Note: Alternately, you can move the main left/right output cables to the Low Pass Channel left/right outputs on the back of the Alligator. This way, the audio input into the Alligator is only passing through the Low Pass section of the Alligator. Note also that this doesn’t have to be the Low Pass Channel. This idea works with any of the Channels in the Alligator, since the effects and mixer sections are the same for all 3 Channels. The idea is to pick one Channel, and mute the other two.
Turn off the filter section (green light) on the low pass filter.
You might also want to reduce the volume of the low pass filter (I found a volume setting of 64 for the low pass volume combined with a volume setting of 100 for the master volume is equivalent to bypassing the Alligator — at least to my ears).

Now your signal is passing through the low pass Channel only, and with the Gate always open and the Filter section turned off, you can use the effects & mixer sections independently to affect your sound.

The Alligator Front Panel, showing the areas of importance when trying to use a single channel for effects and Mixer only; in this case, using the Low Pass Channel

Technique #6: Using External Effects

As with all Reason devices, you can very easily set things up to use external Reason devices. In other words, you are not limited to using the Drive, Phaser, and Delay that’s already built into the Alligator device. If you wish to use an external effects device, such as an Echo, Scream, or even any of the Kong FX modules, you can easily set this up. Here’s how you go about it.

Select the sound source device or Audio Channel and then add an Alligator so that it’s auto-routed.
Determine if you want the external effect to be applied to all three Channels or just one of the Channels.
If you want the effect applied to all three Channels, it’s super easy. Just select the Alligator and add your effect device (a Scream, for instance). The Scream is auto-routed after the Alligator and will be applied to the Gated signal from all three Channels.
If, however, you want to have the effect applied to specific Channels, select the Alligator and add your effect device (a Scream, for instance). Then flip to the back of the device (Tab), and move the main left/right Alligator audio output cables to one of the three desired Channel output pair (High, Band, or Low Pass Channel).
If you desire, you can do the same thing for the other two Channels by adding other effects and routing them in a similar way. This way, you could have a Chorus effect inserted into the High Pass Channel, a Scream inserted into the Band Pass Channel, and a Pulveriser inserted into the Low Pass Channel. Or you could have three different screams inserted into the three different Channels, and set the parameters/settings for all three Screams differently to get more variation.

The more you experiment with external devices, the more I’m sure you’ll find how versatile the Alligator is in processing your sounds. You might even wonder how you ever lived without this device.

The back of the rack, showing how to process the audio through single Alligator channels and external effects.

Here’s the video showing you the above two techniques:

Technique #7: Gating Three different Audio signals across Three Different Gate Channels.

Here’s an interesting way to go about using the Alligator Effect device. How about taking three different sound sources and passing them through the three different Alligator Gate Channels, and then outputting them to three different Mixer Channels? Confused yet?

No, you can’t really do this with a single Alligator because the Alligator only has one pair of Inputs. However, you can create three Alligators, and then send your three audio sources into the three different Alligators (one audio source for each Alligator). Once this is done, you can send the separate channel outputs on to their own Mix Channel Inputs. The setup would look like this:

Audio Source 1 > Alligator “A” main left/right input > High Pass Channel left/right output > Mix Channel “A” left/right input
Audio Source 1 > Alligator “B” main left/right input > Band Pass Channel left/right output > Mix Channel “B” left/right input
Audio Source 1 > Alligator “C” main left/right input > Low Pass Channel left/right output > Mix Channel “C” left/right input

The nice thing about this setup is that you can choose to keep all three Alligators’ “Pattern” section the same, in which case the “Pattern” sounds sync nicely together between all three Alligators, or you can spice it up by setting up different parameters in each of the Alligator “Pattern” sections. For example, you could set Alligator “A” to have a resolution of 1/8, Alligator “B” to have a resolution of 1/16, and Alligator “C” to have a resolution of 1/32. And/or you can set all three Alligators to different patterns entirely. This way, you can attain some very intriguing and unique gate patterns going on, and all your friends will wonder how the hell you did it. Well, maybe not, but it’s something worth a try!

Showing different audio sources processed by different alligator channels to achieve an interesting result.

Technique #8: Oh Hell, let’s just dive off the cliff already!

You want something completely off the wall right? Well here goes. Since the Alligator contains separate outputs, you could theoretically “Nest” the Alligators one after the other. This creates a Double-Gate-Filter-FX Channel for any audio source passed through it. Here’s how this little trick works at it’s most simplest (note that you can create Triple- Quadruple- and so on, nested Channels up to the point where it probably just won’t sound good anymore and your CPU will have a heart attack and lie dead on the operation table). This technique goes down one nested level, and only highlights the “High Pass” Channel. Of course, there’s nothing stopping you from mixing/matching nested channels either. For example, a High Pass Channel goes into a Low Pass Channel, or a Low Pass Channel goes into a Band Pass Channel. Just be warned that you may need to write this out as a diagram on paper first before you lose yourself in Cables.

Audio Source > Alligator “A” main left/right input > High Pass Channel left/right output. . .

. . . Alligator “A” High Pass Channel left/right output > Alligator “B” main left/right input > High Pass Channel left/right output > Mix Channel left/right input

So now that you’ve set it up in this way, if all your Alligators are set to the exact same parameters, adding on these additional “nested” Alligators won’t produce a different sound. Where things get interesting is when you start changing the parameters so each of the Alligators are set with unique parameters. See the Project Files at the top of this tutorial for a Combinator that shows this type of setup.

Of course, if you want to use all three channels, you’ll need to create more Alligators, and each nested level will require a new Alligator. You’ll also need a Spider Audio Merger/Splitter to both split the Audio Source into the three channels, and then use the Merged side to merge them back again before going on to the Mix Channel input. As I said, this could get very tricky very quickly, and will probably be quite CPU-intensive. My advice would be to start off with one Channel and two levels (as the example shows above), then start setting up the parameters on both Alligators. See how that works out for you. Then build it up by moving to the next Channel (if you like), and so on.

Processing your audio source through multiple Alligator Channels. This shows the High Pass Channel in series. But you can do the same with other Alligator channels.

Technique #9: Let’s Dial it Back a Bit. Adding Filter Movement

This technique is a little less freaky, and I’m going to end off with it so that you give your mind a chance to wrap around that last little technique. In this one, we’ll do something easy. We’ll take some Malstrom Curves and send them into the Alligator’s Frequency CV inputs to create some movement. Then, since there is only 2 Curve’s available with the Malstrom, we’ll steal the LFO CV output and send it into the third Filter Frequency CV input (all within the same Alligator). Sounds more complicated than it actually is. But here’s an image that shows the setup:

Showing the Malstrom's 2 Mod A/B waves and the Alligator's LFO to provide movement to the Alligator's 3 filters.

Those are all the ideas I have for the Alligator at the moment. I’m sure there’s many other interesting ways it can be used. If you have any other ideas, I’d love to hear them, so please don’t be shy and comment to let me know what you’ve come up with. I’m all ears. Until next time, go make some killer music. 🙂

68 – All about the Alligator (Part 1)

In this tutorial I’m going to talk about the new Alligator device in Reason 6. I think no other device has mystified so many since the RPG-8, and a lot of people have reluctance to really dive into it, thinking it’s mainly built for electronic musicians. Truth is that it’s a very easy device to work with, and it has applications for all kinds of instruments and all kinds of genres. So don’t be intimidated by all the knobs and levers. It’s a veritable evil laboratory, but getting it under control is easier than you think, and that’s the focus here.

You can download the project files here: alligator-techniques. They contain a .reason file with all the techniques described below, as well as the separate combinators. You will of course need Reason 6 in order to load and use any of the files.

Introduction to the Alligator

The Alligator is billed as a “Triple Filtered Gate” and that’s exactly what it is. However, it’s quite a bit more. It contains 64 patterns that can be manipulated, it has a few built in effects (Drive, Phaser, and Delay), it has 9 LFO’s that can be used to affect the filters, and the Panning capabilities allow you to create some movement in the stereo field. That’s not even taking a look at what you can do with the CV connections on the back of the device.

To start, let’s take a look at the various sections of the Alligator. When I’m starting off creating a patch for this device, I usually first load up a sound I want affected. So if it’s a Bass or a Synth or a Drum sound, all of these sounds will require a different approach to the Alligator. In other words, the sound I feed into it coupled with what I want to do to that sound in my head, will decide how I proceed with the device.

Following is an explanation of the parameters you will find on the front panel of the Alligator device.

The Alligator front panel with legend and explanation of the device functions.

And following is an explanation of the inputs and outputs found on the back panel of the Alligator device.

The back of the Alligator device with an explanation of the CV and Audio inputs and outputs.

And here’s the quick introduction video to show you the main components of the Alligator:

Technique #1: Creating a Dry / Wet Knob for the Alligator

Since the Alligator does not have a Dry / Wet knob, we have to go about getting a little creative. This means wrapping the device inside a Combinator. Once there, you can use the Dry Level Knob and program its direction to be inverse to the individual Band level knobs. Set that up on a rotary in the Combinator and you have an instant Dry / Wet control for our Mister Alligator.

Technique #2: Keeping your Gates Open

You’ll notice that the Alligator by default uses a pattern to open/close the gates. You can turn them off or turn the pattern on, but what if you want to keep the gates open all the time. The easy solution is to do the following:

Set the Alligator pattern to #60
Flip to the back of the Alligator and send the Gate 1 CV output to Gate 3 CV input (both on the same Alligator device)
Send Gate 2 CV output to Gate 1 CV input (both on the same Alligator device)
Send Gate 3 CV output to Gate 2 CV input (both on the same Alligator device)

If you flip back to the front of the Alligator you will see all the gates are permanently on. This means that you can still use the LFO, Frequency, Resonance, all the Effects (Drive, Phaser, Delay), and Mixer controls to affect the sound, but you bypass the Gate section of the Alligator. It’s always on.

Just note one thing when you do this: You want to keep the Amp Envelope Decay set to full (fully right). If you lower the Amp Envelope Decay knob, the gate will fade out (even though it is completely open). If this happens, you’ll have to first move the decay knob all the way right, and then reset the CV on the back of the Alligator (unplug all 3 CV connections, and plug them back in again).

Alternately, you can send a one step tied curve pattern in a Matrix split 3 ways through a Spider and then sent to all 3 gate inputs, but this means creating additional devices when it can all be accomplished with a single Alligator.

This video will show you how to set up the above 2 Techniques:

Technique #3: Creating your own Patterns to Control the Gates

You’re not limited to the 64 patterns that are built into the Alligator (though you can definitely have a lot of fun with so many different patterns). You can easily use 3 Thors or 3 Matrix Curves/Gate CV to control all 3 gates in a single Alligator. To do this, first turn off the pattern section in the Alligator (the big “ON” button at the top of the Pattern section). Once you do this, you’ll need to create your Thors or Matrixes and flip to the back of the rack. Send the CV from the Step Sequencers into the 3 Gate CV inputs and then start all of the pattern devices up (this is easier to do if everything is Combined in a Combinator. That way when you press the “Run all Pattern Devices” or press “Play” on the Transport, the Step Sequencers start gating the Alligator. Dead simple my friends!

Best of all, this means you can create any kind of gate of any length you can imagine (See my “Matrix” series of tutorials #48-51 or Thor sequencing ideas #60-62 for ways in which you can extend the length of your patterns).

Technique #4: Stealing the Patterns to sequence other Reason Device Parameters

Forgetting about the Alligator’s intended purpose for a second, you can use its built-in patterns to affect any other parameter in any of Reason’s devices (just about). In this way I got pretty excited to see that you can use the Alligator as an “already pre-configured Matrix with double the amount of patterns” — yeah that’s pretty exciting for a nerdy nerd like me. It means I don’t have to tediously program two matrixes filled with patterns (though truth be told, if you’ve read article #3 in my 101 Creative Projects category, you already have a huge array of Matrixes from which you can copy/paste into any of your projects, right?).

In any event, to get the ball rolling, pick a pattern you like. Then flip to the back of the Alligator and disconnect the audio cables. You’re only using the pattern section here to trigger something else in Reason. And since you have 3 gates, this means you can modulate three other parameters from a single Alligator device (or how about using a spider to combine the three gates and sending the merged output to control a single parameter). I think you get the picture. This is a very quick and easy way to control things via CV.

One idea is to use the Gates in the Alligator to play the Kong drum designer. Send the three gates of an alligator into 3 drum pad CV inputs on the back of Kong, and then you can set up some pad groups in Kong so that you get even more variation. Finally, set up a Matrix curve to control the “Shift” knob via one of the CV inputs in a Combinator, and you have instant “Groove” for your drums, without ever using the ReGroove. It’s a nice alternate way to get some drums going quickly in your tracks. For the full feature on how this is done, see the video below.

Tip #1: Tuning your Filters

This concept was provided by Peff when he was doing his tutoring session in Las Vegas. And I really do hope that he doesn’t mind me providing the tip here. But in the attempt at full disclosure he needs full credit on this one.

Tuning filters is not a concept I was all that familiar with, but armed with this knowledge, it actually makes perfect sense, and has applications that reach out much farther than just the Alligator. But that could be a whole tutorial in and of itself. For our purposes, tuning the Alligator filters is a way to produce a more even sound coming out of the device. The idea is that you pick a frequency as your “Base” and then set the other filters up so that they are multiples of this “Base” frequency. So if you set up the LP Filter on the low end to be 200 Hz, then the BP Filter could be set up to 400 Hz and the HP Filter could be set to 800 Hz, which should produce a “cleaner” tone than if the filters were out of sync or out of tune.

Now while this is a handy technique, I should also say that going for a sound where the filters are more out of tune is perfectly valid. This is not a practice that should be set in stone. It’s more a technique that you should understand and get acquainted with and add into your arsenal of knowledge. But don’t be afraid to venture outside this technique.

You’ll also notice that it’s not always possible to get a precise multiple of a specific Filter Frequency. But generally, the closer you are to a multiple, the more “in tune” the filters should be with each other.

Tip #2: Taming the Dreaded Pops & Clicks

One thing that still bothers me to this day is how quirky the envelopes and LFO can be in the Alligator. Under certain settings, you can hear noticeable pops and clicks which are most definitely unwanted. Here are a few ways to deal with this if you find it happening to you.

First, it’s important to note what’s causing the pops and clicks in the first place. More often than not, it’s a result of a short Attack Time in the Amp Envelope coupled with a slow-running LFO with a sharp edge (think the Pulse or stepped Waveforms). The lack of a lag feature (which is available in the Pulveriser) means that you can’t smooth out the LFO. And when it’s running too slow, and the attack time is short, this is usually a recipe for disaster. Here are a few hints to get you out of this jam. Note that all of these methods will change the sound of the gated effect, but there’s really no way around this that I’ve found.

Use a smooth LFO, such as the Sine Wave or even the Triangle Wave. Stay away from the Stepped, Ramp, or Pulse waves.
Adjust the Amp Envelope’s Attack time to be slower (turn the knob more to the right). Times that are above 25 or 30 work well.
Don’t use the LFO at all. Ensure that all the LFO knobs for the bands you are using are all pointing due west! This means the LFO does not affect the bands whatsoever.

So there are a few tips and tricks for you to get acquainted with the Alligator. Give it a whirl on any kind of audio just to get a feel for it, and have some fun gating your audio. Until next time, happy Reasoning!

61 – Generative Ideas (pt. 2)

Continuing our story about creating some random generative musical ideas in Reason, I’m going to take the Random Sequencers we built previously and find some usefulness for them. So hold on to your hat. It’s going to be a bumpy ride.

You can download the project files here: Generative-Ideas-Part2. The files highlight the ideas I’m covering here. Note that some of the files work for Reason 4 and some work for Reason 5. C’est la vie.

Random Glitch Box

The Front panel settings on the "Glitch Box" Combinator

The first and probably best use I can find for these random generators is as a glitch box. Surprise surprise. This one really is a no-brainer. Just fire up the 128-step sequencer, duplicate the devices, and with a little reworking we have two separate randomizations: one for the notes and the other for the gate. Then load up a sample that spans the length of the keyboard, and this will be our “Grain Sample” which will be played via the sequencer Combinator. You can put the sample player inside the Combinator and just rewire the sound source CV / Gate inputs into your device of choice. Here, I’m going to use an NN19 for the sample.

The front of the Sampler glitch Box. It's almost like a Grain sampler, when you use the sequencer this way.

The back of the Sampler. You could also randomize the "Sample Start Time" if you wanted to go further with this idea.

Random FX

Remember that gargantuan “Key Flux FX Processor” I built oh so long ago? Well how about we fire up that bad boy and take it for the ride of its life. Using the same sequencer as above, we’ll plug it into the FX processor, and let it process any of your sounds. Just sit back and watch it cycle through all the various effects randomly. I think I could sit here for hours just listening to it doing its thing.

Crafting Some Useful Leads

Though this might not make any earth-shatteringly great lead tracks, you can make your sequencer more musical by implementing the following idea. First, take the 64-step sequencer, and change the notes around so that each of the four “Thor Sequencers” are 2-steps long. Then put the first two notes of your key (here we’ll use the key of C Major to keep it simple) into the first sequencer, the next two in the second sequencer, and so on. You will end up with this configuration:

Thor Sequencer 1: Step 1 = C3; Step 2 = D3

Thor Sequencer 2: Step 1 = E3; Step 2 = F3

Thor Sequencer 3: Step 1 = G3; Step 2 = A3

Thor Sequencer 4: Step 1 = B3; Step 2 = C4

Next, we’ll map the other steps so that we can add more of specific notes from the same key. In my patch I put more C, E, and G notes in the empty steps on the first Thor sequencer, and more of the D, F, A, B notes in the empty steps of the second Thor sequencer. I then added some sharps and flats into the third Thor sequencer, and additional suspended notes (and Octave shifts — i.e.: C4 notes) into the fourth Thor sequencer.

The steps in the first "Thor Step Sequencer" showing a C3-E3-G3-C4 pattern.

Finally, in the Combinator Modulation Routing section, I mapped the Sequencer > Step Length parameter of all four thors to Rotary 3 & 4, and Button 3 & 4 respectively. The min / max values on all were 2 / 16. This way, we can use the Rotaries and Buttons to add in further steps to increase the “weight” of them into the Random sequencer. For instance, if you turn up Rotary 1, you will introduce more C, E, and G notes. This has the effect of weighting those notes more than other notes in the key. In other words, the sequencer will “pick up” and “play” those notes more than the others.

The front of the Combinator, showing the Rotaries / Buttons. Note the Step Count is mapped to Rotary 3 to add more weight to C-E-G notes.

Of course if the Combinator had more Rotary assignments, you could weight each key separately using 8 rotaries. But that’s just not the case. But if you look at my Kongtrol articles from a few weeks back, you could very easily build it using Kong (wink wink, nudge nudge).

The patch I built only uses 1 octave range, but there’s nothing stopping you from building this across multiple octaves, up to 128 steps, using my random sequencer here. Or you can use the Transpose feature to raise it to two octaves. Or you could use the RPG-8 to force octave switches, but then you’re going to be inputting values into the “Main Sequencer” in Reason, and I’m trying to stay away from doing that.

Modulation, Modulation, Modulation

Another interesting use of the random sequencer is when you start to get into modulation. With a random setup, you can use the CV output to modulate parameters on any of the Reason devices, even ones that don’t have a CV input (using the Combinator Rotaries as the CV pass-through). Included in the file is a “Mods” patch which show you how to create a random EQ generator and also use the same random sequence to affect some parameters to the Thor sound source directly (via CV1). The Thor’s CV1 is then mapped to the “Amp Pan” and “Osc 3 Position” parameters. Note that in order to get the EQ Frequency modulated, you need to send the random sequence CV to a Combinator rotary first. Then in the Combinator’s Modulation Routing section, you can map the rotary to affect the EQ Frequency. In the patch I’m providing, I set the Min / Max values to 600 / 100, which provided some nice movement to the sound.

The front of the Combinator showing the Thor sound source and EQ, Both of which are modulated with the Thor Random Step Sequencer.

The back panel showing the Note CV sent to the Spider and then sent to Rotary 1 and the Thor sound source CV 1 input.

The front panel of the Combinator with the Programmer displayed. Note that the EQ Parameter 1 Frequency is mapped to Rotary 1. This way a parameter without a CV input can be controlled via CV using the Rotary as a pass-through.

In a nutshell, if you open this patch, you can press play on the transport, which starts the sound. No modulation is affecting the EQ, Pan, or Osc 3 Position parameters yet. In order to turn on these modulations, press button 1 (Run / Reset). You will then hear the modulations taking effect. To select the amount of modulation applied, use Rotary 1. To affect the Synced Rate of the modulations, use Rotary 2.

Note: in this kind of setup, I only used the “Note CV” value from the random sequencer. The gate CV value was not needed or used. I also removed the CV visualization DDL-1 devices, so that the patch would be accessible for both Reason 4 and Reason 5 users. Note also that the CV values are inverted through the Spider so that Rotary 1 will gain more modulation when turned to the right. If the signal wasn’t inverted, turning the Rotary to the right would produce less modulation, which is counter-intuitive in my book.

Where do you go from here?

These are just a few ideas I had when I was playing around with the Random Sequencer I created. As I went from having the first initial “problem,” I ended up with several interesting sequencer patches and ideas. This just proves that if you have a single thought or problem, and you can solve it, you can end up going in a lot of different directions which lead to even more ideas and creative projects. So I guess my point is this. Find as many “problems” as you can, and then work toward solving them. Because that just might be the creative spark you need to start an imaginative wildfire.

One other place you could take this is to build an entire “generative” song, in which all parts of it are randomized. In this case, if you used the Thor sequencer here, you would end up with a song that is never the same way twice, and one which bypasses the Main Reason sequencer entirely. As a creative project, that would be quite an undertaking. But if you want creative ideas, there they are.

Another creative “generative” idea is to blend multiple LFOs together, so that you end up with a lot of variety. You could then take a third LFO and use that to apply to one of the two LFO’s rate or amount parameter. There’s all kinds of ways you can layer LFOs to come up with some pretty intricate modulation sources. But I think I’ll save that one for another article at a later date. For now, I’m pretty much done looking at Thor’s sequencer for a while. And it’s Music Making Month, so it’s time to actually make some music right?

PS: If you come across any other ideas related to this idea of “Generative” or “Random” music, please share them. I’d love to hear and take a look at what you’re working on. All my best for now.

51 – Matrix Track Building (Part 4)

Just when you thought it was over. . . You were wrong! I’ve decided to extend this series of tutorials to explore a few things that I didn’t get to within the track I built. I could probably go on for 10 more parts to go over all the possible things you could do with the Matrix. But I wanted to focus on a few areas and explore them in a little more depth. So here’s a few things beyond the track, which you can do with the Matrix Step Sequencer.

Download the new project files here: Matrix-Track-Building2(NoCheat). This zip file contains a new version of the main song .rns file, as well as the two new Combinators for the Bass and Pad tracks. They both contain new Matrix devices that can be used in place of the Mod Wheel Automation clips found in the song. Read on to see what was done to update them. Note: please respect that these project files, like everything else on this site, is under the Creative Commons 3.0 licensing, meaning you can mix, remix, share, and play around with the song to your heart’s content, but you will need to provide the source info and a link back to my site here in any productions you do with this file. Share and share alike ok? And you can’t make any money off the file. It’s not going to win any awards anyway. But if you remix or play with the file, send them back to me privately and I’d be happy to showcase them here in a new posting (send to my email in the top menu), I’d love to see what you come up with. Don’t be shy! 😉

Chaining Patterns together to create a Pendulum Direction

As I mentioned in Part 1 of this series, you can chain two patterns together to create a Pendulum direction for any pattern. To do this, simply have one pattern going one direction, and another pattern going the opposite direction. Then you can place the patterns back to back endlessly in the main sequencer on the pattern track. The pattern clips would alternate and sound exactly as if you used the Pendulum direction setting on the Thor Step Sequencer. Here’s a short video to show how that’s done.

Automating the Resolution Knob

Spend more than a few minutes with the Matrix, and you’ll realize that you can’t automate the Resolution knob in a Matrix. So how do you keep the pattern the same, but change the resolution of the pattern? I came across this problem when I was first starting out with Reason. And it’s no problem. The solution is to create copies of the pattern (A1, A2, A3, A4, etc.) and then change the resolution for each pattern. If you want a pattern that can travel across all resolutions in the Matrix, you’ll have to create 9 copies of the same pattern, and then change each pattern’s resolution setting from 1/2 to 1/128.

Note: You can even put the Matrix inside a Combinator and assign a Combinator Rotary to switch between the different patterns (A1 to B1). In this way, the Combinator Rotary acts as a Resolution knob, and it IS automatable. Only downside is that your pattern must complete the full pattern cycle before it switches to the next pattern/resolution in this scenario (because the Matrix is “locked” to the main tempo).

Finishing up the song. . . No Cheating this time!

Now let’s delve back into the Track I completed and update those last two automations that were put on the Mod Wheel automation lanes, and change them to be controlled by the Matrix. Once this is done I can clear my conscience and bring this series to a close.

Note: For a full explanation of how this is accomplished, refer back to “Part 2” of this series, where I go into great lengths on the subject of using the Matrix to create a long complex pattern (or rather, a compound pattern). If you’ve been reading this tutorial through chronologically, the hope is that you’ve given this a try yourself and come up with something similar to the solution I came up with here.

If you look at the image below, you’ll see how I changed the automation in the main sequencer for the Bass and Pad track. For both those tracks I turned the automation lanes off (to keep them here to show you the relationship — they are just above the new Matrix Pattern Lanes), and added a new Matrix to control the Mod Wheel of each of those Combinators (labeled “M.Wh.Seq.”). This essentially does the same thing as the automation. If you open the Project files at the top of this posting, you’ll be able to open up the .RNS, solo each track and then play the song at the automation points to listen to how the Matrix is working. You can also open up the rack and see the Matrix cycle through the patterns. If you want to switch back to compare, just turn the Matrix pattern lane off, and turn on the automation lane again.

The main sequencer showing how the Matrix patterns can be used in place of the Mod Wheel Automation clips

And that about does it for the Matrix. I’m sure there are many other ways to use the device, but my hope is that this shows how you can get the Matrix to play most anything the Reason devices can dish out. I hope this also shows you some new creative ways that you might not have known about before. If you have any other uses for the Matrix, please feel free to share them here. It’s been an interesting creative journey for me, and I hope for you as well.

As always, thanks to those who watch, read, and listen in.

50 – Matrix Track Building (Part 3)

In this tutorial, I’m going to finish up our Matrix song, and then explore the differences between the Matrix and the Thor Step Sequencer in a little more detail. It’s important to note the differences between the two and how one is not necessarily better than the other. Although I would argue that Thor’s step sequencer is much more advanced from a programming standpoint. I think the Matrix still has a lot to offer and still provides a lot of possible uses. So don’t shelve it just yet.

Creating a Bell Fill

This time we’ll use the Matrix in a new way, as an Arpeggiator. I know if you have Reason 4 and up, you have the great RPG-8 (which I’ve explored in a different series of tutorials). This time, however, we’ll use the Matrix to arpeggiate your sounds. In this specific case, the Bell Fill track is used to add some arpeggiated notes into the song. Creating an Arpeggio with a Matrix is really easy. Think of it this way: You need one Matrix to play the notes/gate and another Matrix to apply the Arpeggiator. In the second Matrix, the Note CV is sent to the Osc. Pitch CV input (Osc. Pitch is a CV input on all Reason Synths and Samplers).

In this case, a Thor is used to create a Bell sound using 2 FM Pair Oscillators, and then one Matrix is sent to the Note/Gate CV input on the Thor (this plays the Thor in a normal way), and another Matrix Note CV output is sent into the CV1 input. On the Modulation Bus Routing Section (MBRS), the CV1 input is sent to the 2 Oscillator Pitches. Any notes you input on this second Matrix device will adjust the Pitch as the Thor is played; i.e.: it arpeggiates the Notes being played. This gives you a great degree of control over your Bell sound.

Song Cleanup

Finally, we’ll do a little bit of cleanup to the song overall. First, we’ll add a Reverb as a send to all the tracks and “glue” the whole song together. Second, we’ll add a Mastering Suite underneath the Hardware Interface to master the entire track. Note that this is just a starting point. You can tweak all the mastering device parameters to fit the song as you see fit. But it’s a good starting point to try out some of the Mastering Suites that are included with Reason and Record. For that matter, you can bring everything into Record and use the SSL to master your track. So many options.

Probably more important is the fact that if you have Reason 5 (not sure about Reason 4), you can select all the Matrix Sequencer tracks (using Ctrl+Right-clicking on the tracks at the left section of the sequencer) and select “Convert Pattern Automation to Notes.” This is a very handy way to convert all the pattern automation you’ve spent so much time getting “just right” into note clips on note lanes. Once this is done, you’ll have to move all the note clips to their respective Combinator tracks. The Pattern lanes are automatically muted for you though, because the expectation is that you won’t want to have them playing or “doubling” up, after you move the note clips to the Combinator lanes.

This little trick provides you with the ability to then go in and adjust individual notes or entire note clips using the “Sequencer Tools” (F8). You can quantize, Transpose, adjust velocity, randomize notes, Scale Tempo, etc.

So there in a nutshell is how you can use the Matrix to build a track in Reason. Now I think I’ll try building one with nothing but Subtractors. That should be an interesting task. As always, let me know what you think, or if you have any suggestions on ways in which you can use the Matrix within Reason and Record.

If you want to download the final song file, along with all the separate Combinators, you can find them here: Matrix-Track-Building. The file includes a final .rns file as well as the separate Combinators. The reason the Combinators are provided is because I’m running reason version 5. But for this project, I stuck only to devices you would find in both version 4.0 and 5.0. So if you can’t open the .rns file, then you have the Combinators and can reconstruct things yourself if you like. It’s more fun that way anyhow. Note: please respect that these project files, like everything else on this site, is under the Creative Commons 3.0 licensing, meaning you can mix, remix, share, and play around with the song to your heart’s content, but you will need to provide the source info and a link back to my site here in any productions you do with this file. Share and share alike ok? And you can’t make any money off the file. It’s not going to win any awards anyway. But if you remix or play with the file, send them back to me privately and I’d be happy to showcase them here in a new posting (send to my email in the top menu), I’d love to see what you come up with. Don’t be shy! 😉

Where do you go from here?

Well you have the file, so feel free to remix and play with it and send it back my way. I’d love to take a listen. As I put together this posting, I also thought a little more about the comparison between the Matrix step sequencer and the Thor step sequencer, so I’ll leave off with a look at both in a side-by-side comparison. Just to give everyone a little more food for thought about both, and when one would be better suited over the other. In asking some people on “The Sound of Reason” website which was more advantageous than the other, I got some mixed responses. Most found the Matrix to be easier to use live, but they also found the Thor sequencer to be advanced on a number of fronts. I’ll let you decide. For now, the jury seems to say that both are still very much necessary, and they are more like sisters than a parent-child relationship.

So let’s take a rundown of the Pros and Cons of each by providing a side-to-side comparison:

	Matrix	Thor	Notes
Pattern Enable	Yes	Yes	You can use the “Step Seq.” button on the Thor Controller (top panel) to enable or disable the Step Sequencer.
Pattern Reset	No	Yes (non-automatable button).
Number of Patterns	8 Patterns x 4 banks = 32	1	Obviously, the Matrix can produce more pattern variations than Thor. You will need to create a new instance of Thor for each pattern you want to input.
Pattern Randomization	2 Options (via right-click context menu): Randomize Alter Pattern	1 Option (via right-click context menu): Randomize	Dear Props: Please add Alter Pattern to Thor. Pretty please with a cherry on top.
Convert Patterns to Notes	Yes (via right-click context menu).	No	This is the biggest beef users have with Thor. You can’t send the Thor sequencer data to the Main Reason/Record sequencer, either as patterns or as notes. Nuff said.
Number of Steps	1 – 32 (selectable via digital input and up/down arrows). Non-automatable.	1- 16 (selectable via lighted square step buttons) or Step Count knob. Note that the Step Count knob is automatable, while the step buttons are not.	Thor’ step count knob is automatable, which means you can automate the number of steps, but since you can’t automate the step buttons, you can’t automate turning steps on or off.
Pattern Input Type	Note/ Bar visual display (non-automatable)	16 Rotary inputs (non-automatable)
Resolution Input Type	Rotary (labeled dial)	Rotary (digital dial)
Step Directions	1 direction: Forward	5 directions: Forward Reverse Pendulum 1 Pendulum 2 Random
Run Button	Yes (non-automatable)	Yes (non-automatable)	It’s a little unfair to say that the Thor Run button is not automatable. As with most things in Reason/Record, there are workarounds. And you can get it to run using the Modulation Bus Routing Section (MBRS) or CV to trigger the sequencer. As far as I can tell though, there’s no way to automate the Matrix Run button.
Run Modes	No	4 modes: Off Step One-Shot Repeat
Mute Light	Yes	Yes
Sync Capability	Yes	Yes
Synced Rate / Resolution	9 Positions (non-automatable): 1/2 1/4 1/8 1/8T (Triplet) 1/16 1/16T (Triplet) 1/32 1/64 1/128	21 Positions: 16/4 12/4 8/4 7/4 6/4 5/4 4/4 3/4 2/4 3/8 1/2T (Triplet) 1/4 3/16 1/4T (Triplet) 1/8 1/16D (Dotted) 1/8T (Triplet) 1/16 1/16T (Triplet) 1/32 1/64	Synced Rates/Resolutions which are shared between the two are in Bold. While the Matrix has less positions, it has two positions Thor does not: 1/128 and 1/2. Though I would venture that using 8/4 and 2/4 is the same as using 1/2.
Non-Sync Capability	No (always synced)	Yes
Non-Synced Range	N/A	.10 Hz – 250 Hz.
Editability
Notes	Yes (5-Octave Range from C1 to C6)	Yes (Full Range from C-2 to G8)	Note that for Thor, there are 3 global Note modes: “2,” “4,” and “Full” octave ranges. Note also that for Thor, the Octave switch is not automatable
Velocity	Yes (Range is 0 – 127)	Yes (Range is 0 – 127)	Note: in Thor you can see a digital readout of the Velocity value. In the Matrix you do not see the precise value. It’s a bit of a guess to get the Velocity exact. Though workarounds exist to see the numerical CV value (see Part 1 of this series of Matrix tutorials).
Gate Length	3 states: Off (0) Half (50%) Tied (100%)	100 States (Full Range of 0% – 100%)
Step Duration	Static	Varied (17 Positions): 1/4 1/3 3/8 1/2 5/8 2/3 3/4 7/8 1 5/4 4/3 6/4 7/4 8/4 9/4 3 4	This parameter is different than the gate length. Whereas Gate Length determines how long the gate stays open, Step Duration signifies how long the note plays. Put another way, this allows you to create a self-contained tempo inside Thor’s Step Sequencer. Something you can’t do with the Matrix because all steps are a static value. There is no ability to change step duration for each note played. If you use Step Duration in Thor, generally, you’re going to want your entire pattern to equal the same value as the overall tempo. This means if you change One step duration downward, you want to change another one upward to compensate. If you don’t compensate, you’ll end up with a pattern that’s out of sync (which of course may be what you want, but probably not). Try it out to get a feel for how it operates. If you go too far, there’s always the “Reset” button.
Curve 1	Yes. 2 “modes”: Unipolar (Range: 0 – 127) Bipolar (Range: -64 to +64)	Yes. 1 “mode”: Unipolar (Range: 0 – 127)
Curve 2	No	Yes. 1 “mode”: Unipolar (Range: 0 – 127)
Shuffle	Yes (valid for Resolution values 1/8T and above). This is non-automatable, but is set on a per-pattern basis.	No	Though Thor does not have a Shuffle feature, you are usually better off using the ReGroove functionality for Both Thor and the Matrix. In Thor, you can use the Step Duration to shuffle as well.
Editing Input / Edit Knob	Note / Step / Gate / Velocity are drawn in by hand.	Rotaries are available for each step, and are turned for one value at a time (determined by the Edit knob). Note that the edit knob as well as the steps and Rotaries are all non-automatable.	This makes for easier “Live” editing input for the Matrix. Thor can be a little difficult and unwieldy to enter. It takes more time and precision to lay down a pattern.
CV Capability (all of which are non-automatable)
CV Outputs	3 Outputs: Curve CV Note CV Gate CV	6 Outputs: Note Gate / Velocity Curve 1 Curve 2 Start of Seq. Out End of Seq. Out	This is where Thor really shines, because there is an extra Curve CV, and extra CV outputs that can get sent to other locations when the Sequencer starts and/or stops.
CV Inputs	None	5 Inputs: Gate In (Trig) Rate In Pitch In Gate Length In Velocity In	Again, Thor has some nice input capability where CV can be used to send values into the Sequencer to Trigger all kinds of Parameters. For example, you can have the sequencer run (and play a short sequenced thor melody, for example) based on a Kick by sending the CV from the Kick drum into the Gate In (Trig) CV input.

*Note: Unless otherwise specified, all above parameters are automatable in the sequencer.

In leaving, I’ll say this: They both have their respective places. And what you want to do in your tracks is going to determine which step sequencer you use. One question that I can’t seem to shake is why on earth the Props didn’t provide the ability for the Thor step sequencer to create 64 patterns in a single device, and provide the same kind of editing interface that the Matrix has? If these two things were implemented, the Thor step sequencer would go light years beyond the Matrix and would probably negate the need to keep using the Matrix altogether. These two feature implementations would solve the two biggest issues: multiple patterns per device, and an editing environment that is easy to manipulate in a “live” environment. So if the props are listening, take note: This would help the users out immensely!

Your thoughts?

And after writing this, Sterioevo was kind enough to provide this cool little patch which shows how you can chain several Thor sequencers together to create a giant 256-Step-Transposable-Sequencer. No this is not a tutorial on Thor necessarily, but it shows that with some creative CV routing, you can get an amazing thing going on. Very cool stuff!

49 – Matrix Track Building (Part 2)

Now we get to some fun stuff: How to use the Matrix in a few different and interesting practical ways. To that end, I decided to build an entire track using nothing but sound devices that are controlled by Matrixes (Matrices?). This way, we can explore some of the practical uses of the Matrix along the way.

Creatively, it can also be a test of limitations to try creating tracks entirely with certain devices in Reason. It helps to set some boundaries and you might want to try creating an entire track using nothing but Thors, or nothing but one set of 10 samples or something along those lines. It forces your mind to think in new and innovative ways. And that, after all, is the point of this Blog.

Kick Drum and Roll Creation

In this video, I’ll show you how to create a kick drum and roll using a Subtractor. The Matrix is used to gate the drums and 2 patterns are created: One for the main drum part, and the other for the Roll. Once this is done, you can program the patterns in the sequencer and put the roll anywhere you want.

Snare and Hi Hat Creation

In this video, I’m going to do the same thing with the Matrix. Once again, we use some Subtractors for the sound sources, and the Matrixes are used to gate the drums.

Entering a Bass Line and Variations

Next, we’ll use a Malstrom and Matrix to create a simple Bass line. We’ll also use the “Copy/Paste Pattern,” and “Alter Pattern” functions on the Matrix to create some variations of the main bassline. Note that the “Alter Pattern” feature of the Matrix (accessed from the right-click context menu when you hover your mouse over the Matrix device) is unique to the Matrix. Even Thor doesn’t have this feature. The difference between Alter Pattern and Randomize are as follows:

Randomize: Randomizes the Note values anywhere from C1 to C6 in the Matrix. Also Randomizes the Gate & Velocity events (on / half / tied is also randomized), and the Curve. In other words, all three Matrix outputs are randomized.

Alter Pattern: Randomizes the notes, Gate / Velocity, and Curve events along the left and right axis. No new notes are introduced, no new velocity and gate values, and no new Curve values. Put simply, it reorders what already exists on-screen. And is one of the best features of the Matrix in my honest opinion.

Ok, I’ll admit, I cheated a little on this one. I automated the Mod Wheel directly in the sequencer. I could have just as easily created a curve ramped upward in a new Matrix and sent the Curve CV output from the Matrix into the Malstrom’s Mod Wheel CV input. Then drawn the pattern into the sequencer at the position where the Combinator Mod Wheel automation is located. Oops. But this gives you a great opportunity to practice some of the concepts I’ve presented here. Why not try reproducing this automation lane with a new Matrix yourself? Yeah, let’s go with that. 😉

Creating the Lead

In this video, I’ll show how you can create a Lead with Thor. Then we’ll use the Matrix to create a few patterns as we did for the Bassline. One of the things I hope you take away from this video is the idea that you can use the Matrix to adjust parameters that don’t have CV input jacks on the back of them. I know this sounds counter-intuitive, but it’s not a hard setup at all.

For example, here we have the BW parameter on Thor that can’t be adjusted via CV input, and since it can’t be adjusted on the Thor Modulation Bus Routing System (MBRS), you can’t send the curve CV of the matrix into Thor to adjust it that way. The solution is to send the Curve CV from the Matrix into a Combinator Rotary (or CV input in Version 5.0), and then set this parameter in the Combinator’s Modulation Programmer, so that Rotary 1 on the Combinator adjusts the BW in Thor. This way, the Combinator Rotary acts as a CV pass-through between the Matrix CV source and the Target parameter. This means that you can automate almost any parameter in Reason using the Matrix as a source. Such a simple idea with profound and powerful consequences.

In this second Lead-creation video (below), I’m going to introduce the idea of creating Chords using the Matrix. Since the matrix is a monophonic device, you cannot play more than one voice (or note) at a time. So Chords are out. However, once the lead is created, you can duplicate both the sound source and Matrix a few times to gain access to multiple voices. For example, create three instances of the Sound Source/Matrix duo, and then on step 1 for the first Matrix, place a “C” note. On step one of Matrix 2, place an “E” note. Finally, on step 1 of Matrix number 3 place a “G” note. If you have a pattern that is one step long, you will hear a C-major chord when all three are played simultaneously (when all three Matrixes are “run” at the same time).

So this video shows you how to create polyphony, and automate a polyphonic lead line in the sequencer.

Adding Pads

Now comes the part where we add our pad sound. This is a basic Thor device using some Wavetable Ocsillators and a Multi-Oscillator. Two Matrixes are used; one to control the note/gate of the pad, and the other used to adjust the Filter 1 Frequency.

Once again, I cheated on the Matrix in favor of a Mod Wheel automation lane. The poor girl is never going to forgive me.

Looks like another opportunity to try switching automation lanes into pattern lanes using a Matrix. For this one, it will be a little trickier. Since the Matrix pattern can only go 32 steps long, at the highest resolution(1/128) a single pattern can last 1/4 bar, while at the lowest resolution (1/2) a single pattern can last 16 bars. Put another way, if you want the smoothest possible curve, you will need to use 1/128 resolution. If you want the choppiest curve, you can use the lowest resolution (1/2).

Why does resolution matter? Because it’s important to understand that the Matrix is a “Step” sequencer, and not a a smooth curve (like a vector curve, for example). Put another way, think of the steps in the step sequencer as a square wave and a vector curve as a sine wave. As the amount of steps increases and the amount of time to play those steps decreases, the Resolution becomes finer (the Square Wave moves closer to morphing into a Sine wave). As the amount of steps decreases and the time it takes to play those steps increases, the Resolution becomes coarser (the Sine wave moves closer to morphing into a Square Wave). The finer your resolution, the less you will hear the change from one step event to another. The coarser your resolution, the more you will be apt to hear the switch from one step to another. This is a key concept to keep in mind when working with the Matrix. If the resolution is too course, you’re going to hear the switches between steps — which may be what you’re after. For this specific case, we want to create a very smooth curve. That’s going to mean a lot of Patterns and some work to create smooth, even curves. Truth be told, in the Matrix, there’s no such thing as a pure vector wave or sine wave. It’s just that there is a point at which the resolution becomes so fine that the ear does not hear the switch from one step to another (similar to how resolution works with sight. look at a newspaper photograph up close or through a magnifying glass and you see all the dots — course resolution. Look at the newspaper from farther away and your mind can no longer discern the dot pattern — fine resolution).

So how do you recreate the 20-bar ramp upward that I used for the Pad’s Mod Wheel automation?

The solution is to determine the resolution you want, then chain your patterns together using multiple curves. Let’s go somewhere in the middle. Using 1/16th resolution, we will need 10 patterns to create a 20 bar curve (all patterns using 32 steps). So you will need to utilize patterns A1 to B2 to create a continuous ramp upward. Still with me? Good. Now the most difficult part comes. Since the Matrix does not provide a proper way to set each step (you have to do this visually), you’ll have to figure out approximately where the curve starts and stops between patterns. For this, you can use the Visualizing CV trick I showed in the video in Part 1 of this series. Or you can eyeball it using the hash marks along the left edge of the curve input area. You know that the curve ending A5 and starting on A6 will need to be at the 50% mark of the Unipolar Curve height. So work backwards from there ramping downward all the way to zero at the start of pattern A1 (use the Shift key to create an even line of step events in each pattern). Then work upward from the start of A6 to the end of B2 (again holding down shift to create an even line of step events). Once that’s done, create a series of 10 patterns on the sequencer, each 2 bars long, and chain them together from A1 at the start to B2 at the end.

Now repeat this process using another 10 patterns and create a downward ramp 20 bars long (from B3-C4). To create the middle clip that is at level 127 is easy. Create a pattern (on C5, for example) which is one step long. On this first step of C5, raise the curve value up to the top in the Matrix editor. Then place that pattern on the sequencer for the duration of the middle clip (4 bars long in this song).

Phew! Now you see why I cheated. This is no small task. It’s fiddly, and it takes some effort. So why would you do it this way? Well, it shows you the concept of chaining patterns together, which can come in very handy to create curves or note sequences over long passages in your song. Also, it’s a great way to learn how the Matrix operates, which is, after all, the reason for this tutorial series. But more on this whole pattern chaining issue later on.

Thus ends the second part of our track creation using Matrixes. In the next part of this series, I’m going to show you how to use the Matrix as an arpeggiator, finish and clean up the track, convert all the patterns to notes, and more. Until next time, hope you have some fun in Reason and Record, and post a comment to let me know how you’re making out with the software and how I’m doing teaching it to you. Thanks for reading!

48 – Matrix Track Building (Part 1)

In this tutorial, I’m going to work with the Matrix and build a track by step sequencing. Egads! I hear the purists gasp, as they turn away in disgust. But rest assured, I’m merely presenting this as a creative idea to force you to think about alternative ways to build your songs. Take from that what you will. In the end, I hope this shows you how the Matrix, and step sequencing in general, can be a powerful ally when you compose your tracks.

In this tutorial, I’m going to work with the Matrix and show how you can build a track by sequencing, rather than by plugging notes into the standard Reason sequencer. Egads! I’m not saying this is the best and only approach. Indeed, a lot of people (purists mostly) would probably turn away in disgust at a tutorial like this. I’m merely presenting it as one way you can use to build your songs. Take from that what you will. In the end, I hope this shows you how the Matrix can be a powerful ally when you compose your track, whether or not you go to the extreme of building an entire track using step sequencing or not.

In this first part of the series, I’m going to familiarize you with the Matrix device, and show you how it works. I’m also going to show you a few ways you can use it, as there are an infinite array of ways in which it can be applied. So let’s start out with the Basics, and then we can move on to Part 2, where we get a little more complex.

Matrix Basics

First, a bit about the Matrix. The Matrix is a monophonic step sequencer that is used to generate CV signals to control other devices. It makes no sound on its own. Rather, it must be used in conjunction with other devices for you to achieve anything with it.

Here’s a short video that goes over the various parameters of the Matrix:

The Matrix controls other devices via the 3 CV outputs on the back. Here’s a rundown of the purpose of each of the CV outputs:

To send a gate on/off signal to tell other devices when to start and stop (or to turn a parameter on another device on or off).
To send a note output in a 5-octave range a from C1 to C6 (take note that this is not the full range of all octaves on the keyboard, but rather a subset — for this reason, certain notes and triggers are outside the reach of the Matrix – for example triggering a rex loop to start and stop).
And finally, there is a curve CV which is a straight CV value that can be used for a variety of purposes (much like the Curve 1 or 2 value in a Thor Step Sequencer). The Curve CV is great for drawing in your own curves to be applied anywhere you like.

There is a special switch on the back of the Matrix device called “Bipolar / Unipolar.” Put simply, there are 2 possible CV algorithms that can be used: One is “Bipolar” which sets the CV from -64 to +64 and the second is “Unipolar” which sets the CV from 0 to 127. To understand how this works, think of the difference between volume and Panning in the midi world. Volume is Unipolar: It can go from zero (0) volume to full volume (127). This is the way the fader operates on the 14:2 and 6:2 Mixers in Reason. Panning, on the other hand, is bipolar because it can go from fully left (-64) to fully right (+64). In this instance, zero would be the middle of the stereo field. This switch allows you to set how you want your source curve to act on the destination of the CV signal. And you can visually see how it is displayed on-screen in the “Curve / Keys Display area.

The Front Panel

From the front of the panel, you fill in your pattern information. Here’s a rundown of the front panel of the Matrix:

The Front of the Matrix Device with all parameters outlined.

Pattern Bank: Here you can select from 8 different patterns and 4 different banks (for a total of 32 patterns within a single Matrix). To work on entering a pattern, select an appropriate pattern in a specific bank (usually starting with A1), and then enter curve, note, and velocity (gate) information for the steps in that pattern (or any combination).

Curve / Keys Switch: This switches the display mode from Key display to Curve display. By default, the matrix is set to show Keys in the display (in a 5-octave range). When you switch to Curve display, the Curve can be visually drawn into the display.

Note: holding down the shift key and drawing across the Note or Curve steps creates an even line of note or curve events from the first click to when you let the mouse go. Also, the gate does not play a factor when working with Curves. Gates are a separate CV source from Curves. The curve simply provides a value from 0 – 127 that is represented visually by the bars in the Curve Display.

Curve / Keys Display: This area provides a visual display of the note events in the C1 – C6 range. When the Matrix is run using the Run button, the step sequencer starts and travels from left to right for the number of steps entered, then starts over from the left again and runs through the pattern again. It is forward-moving from left to right and repeating. This is the only direction of movement for the Matrix. In contrast, you can move the Thor Step Sequencer in a few different directions (Forward, Reverse, Random, Pendulum).

Enter note events using your mouse to click on the note value you want. The screen displays 13 notes (1 octave+1) at any given time. Use the “Octave Switch” to the left of the note area to move down or up to the next or previous octave.

Gate Velocity Display: This area runs along the bottom of the Matrix and provides Gate Velocity information. Use your mouse to determine the velocity level of the notes being played by lowering or raising this small bar. You can turn off a note (making it silent) by pulling the Velocity bar all the way down so it is no longer visible. In this case, no matter what note is entered in the Note Display for this event, the note acts as a “rest” for the duration of this gate event.

By default, the note duration is only half the length of the gate. You can enable the “Tie” button, and this allows you to enter full gate duration, so the notes seamlessly sound from one note to the next (or from one gate event to the next).

Note: You can also use Shift when entering Gate/Velocity events. By default, holding Shift down as you draw the events allows you to enter “Tied” gate events. If you have the “Tie” button on, holding Shift down enters non-tied gate events.

Think of it this way: There are 3 settings for a gate event in the Matrix

None: In this case, there is no sound for the note on this step. In other words, the step is a full length of silence (when the Velocity bar is pulled all the way down). The event still occurs for a whole step of silence. This would be like looking at the “Gate” setting in Thor’s Step Sequencer, and having the Step Knob set to 0% (no gate).
Half Step: the Velocity bar is visible and set to a value of some sort. This is the default setting where the velocity bar occupies half the length of the note (from left to right). This would be like looking at the “Gate” setting in Thor’s Step Sequencer, and having the Step Knob set to 50% (half).
Whole Step: The Velocity bar is visible and set to a value of some sort. However, the “Tie” button is enable when you set it (click on the gate event). In this case, the gate is set to be the full length of the note (and glides into the next note/gate event). This would be like looking at the “Gate” setting in Thor’s Step Sequencer, and having the Step Knob set to 100% (full).

As you can start to see, there are some limitations to the Matrix. You cannot create step gate lengths other than these three states (though you can creatively workaround the situation — See Sterioevo’s comment below this post). You cannot change the play direction of the Matrix as you can in Thor (though a workaround is to create two patterns and chain them — for example, create one pattern with notes going forward, and another pattern with the notes going in reverse, and then put their clips on the sequencer back to back for a “Pendulum” direction. You also cannot see the CV’s numerical value for all three sources (Note / Gate / Curve). They appear visually on-screen as bars and note blips. Whereas, you can see the CV values clearly in Thor.

As a sidenote, if you ever want to see CV values for any parameter in Reason, send the CV value to a Combinator Rotary, and include a Thor device in the Combinator. Then on the Combinator Programmer, assign the Combinator’s Rotary 1 to Thor’s Rotary 1 with a min/max value of 0 / 100. Then you can hover your mouse cursor over Thor’s Rotary and see the readout of the value in the Tooltip. And if you want something a little more advanced, you should check out Meowsqueek’s CV Monitor Tool at his Off-White Noise site. But for something very basic, here’s a video for how to set up the Thor Rotary as a Monitor tool:

Steps: For each pattern, you can select the number of steps from 1 to 32. To create 4 1/4 note beats per bar, enter 4 in the number of steps, and dial in 1/4 for the Resolution (see “Resolution Knob” below).

Resolution Knob: While the Matrix adheres to the Global tempo value that you set, the Resolution knob allows you to force the Matrix to play at different tempos or speeds. For example, in 4/4 time, if you create a pattern with 4 steps, and want 1/2 notes, dial in 1/2 for the resolution. You’ll end up with 2 1/2 notes in your sequencer. In other words, the lower the resolution value, the slower the step sequencer runs (or the less notes that are entered per bar). The higher the resolution value, the faster the step sequencer runs (or the more notes that are entered per bar). There are 9 possible Resolution values from 1/2 to 1/128 (two of which, 1/8t and 1/16t, are triplet values).

Shuffle Button: Provides a swing feel to your notes. As the user manual puts it: “It delays all 1/16th notes that fall between the 1/8th notes.” This means, as far as I can see, the Matrix Shuffle setting only affects your output if you have the Resolution knob set to 1/8t or higher. Any setting below that will not change the “groove” of the Matrix pattern. In addition, the shuffle amount is set by the ReGroove “Global Shuffle” setting in the ReGroove Mixer. The “Shuffle can be set independently for each pattern.

Note that this “shuffle” feature is like a poor man’s single-setting ReGroove. All I can say is that it’s great for a quick shuffle feel, but you’re usually better off using the ReGroove in most cases. But since this is all about the Matrix, we need to explore all of its settings.

Matrix Quick-Start 1: Matrix as Sound Previewer

Long before we had the computer keyboard controller (F4 in Reason 5), in the days of old, the best way to preview a song was to use a Matrix. This probably goes without saying but create a sound device in Reason (synth or sampler), and then create a Matrix directly underneath. The Note / Gate CV outputs from the Matrix are connected to the device automatically. Now, with the Matrix still selected, press Ctrl+R to enter a random pattern into the Matrix on pattern A1. Then click the “Run” button on the Matrix (or the “Run” button on the main transport). Bingo! Instant sound previewer. This is great for situations when you want to listen to how a synth sounds as you’re making parameter changes to the synth. And it’s the most basic use of the Matrix.

Matrix Quick-Start 2: Matrix for Parameter Adjustment

Next up is still a very basic concept, but it’s worth exploring. Keep the setup you just created in the “Matrix as a Sound Previewer” section. Now flip to the back of the rack and connect the Curve CV from the Matrix to the Pan CV input on the channel of the mixer where the sound device is located. Turn the trim knob way up. Now set the Bipolar/Unipolar switch to “Bipolar.” Flip back to the front of the rack and press Run again. Voila! Not only is the matrix playing the sound device, it’s also changing the Panning for the device based on the Curve in the Curve display.

The Back of the Matrix with proper Note/Gate CV controlling Thor. And the curve controlling the Pan on the Mixer.

In Summary

As you start to work with the Matrix, you begin to realize how it is a poor cousin to Thor’s Step Sequencer, and you’d be very right. The Matrix has been around since the birth of Reason back in Version 1, and Thor, who came around in version 4, has opened us all up to an entirely revamped “Matrix” in its Step Sequencer. In this respect, Thor is more than just a synth. It’s an enhanced Matrix as well (on steroids, no less). For example, in Thor you have multiple directions your Pattern can take, you have a full 0 – 100% range for the gate length (the Matrix has 3 static states). And you have 2 available curves (the Matrix has one). Still, the Matrix does have at least one advantage over Thor: It can produce 64 patterns in a single device; whereas Thor can only produce one. So it might not come down to a question of who is bigger and badder (though I would still argue Thor wins out every time), it might also be about which device is right for the job.

So why on earth would you still use the Matrix? Because sometimes you don’t need all the power of Thor. Because you might want to create a lot of pattern variations with minimal fuss. Because sometimes it’s healthy to work within a device with set limitations. And most of all, because knowing one will help you learn about using the other. The Matrix is a great place to start. And it’s a wonderful stepping stone to understanding the Thor Sequencer. If Thor seems too intimidating, start with the Matrix and learn it inside out, You’ll be more than halfway to understanding what goes into Thor’s own Step Sequencer. It’s like learning the Subtractor synth before you jump into the Thor synth. And it can be a great creative way to learn how to use it in depth.

Please feel free to provide any comments or insights you might have about the Matrix, Thor, or anything else Reason-related. Stay with me until the next part in this series where I take you further down the Matrix rabbit hole.

10 – Creative ReDrums (Part 2)

Creative Redrums (Part 2)

In part 1 of our Redrum tutorials, I showed you a few ways you can improve the drum kits in your arsenal by using Thor’s filters, and some M Class Mastering devices. In this tutorial, I’m going to work in reverse and show you how to use the Redrum as a gate CV device to trigger a series of 10 Thors, which act as the drum sounds. This is where things can get pretty interesting, as you can gain complete control over the drum sounds by creating them from scratch using Thor’s Oscillators and Filters. Then, we’ll try to use a technique laid out by Matt Piper in which all the drums are filtered through a Vocoder. This is yet another way to get some beef and boom out of the drums. So let’s work some creative Redrum magic.

The project file contains an .rns file with a single Combinator which outlines a complete drum kit with vocoder filtering, Mastering, and a few extra effects thrown in. Download the Project Files here: creative-redrums-2.

The Basic Setup

Create a Combinator, and inside create a 14:2 Mixer. Then holding Shift down, create in order a Redrum, Spider CV Merger/Splitter, and Thor Synth.
Right-click over the Redrum Pattern section and select “Randomize Pattern” just to quickly add a pattern. For this tutorial, the Redrum is used as a sequencer, and nothing more. You’ll be able to change the Resolution of the Pattern, number of steps, and use the Mute/Solo functions, but samples are not necessary.
Next, Create a Bass Drum sound in Thor. Here’s an example of one way you could go about doing this (see the screenshot below). In the Sequencer section, change the Run Mode to 1-shot, and reduce the steps down to 2. Then in the Modulation Bus Routing Section (MBRS), enter the following:
CV In1: 100 > Filt1 In

The Front Panel of Thor with our Analog Bass Drum Sound
Now let’s flip the rack around to the back and make our routing connections. First, connect the Left and Right Audio Outputs (1 and 2) from Thor into the Left and Right Audio Inputs on Channel 1 on the Mixer. Then connect the Gate Out on Channel 1 of the Redrum into the Split A input. Send one split output to the CV 1 In on Thor, and send another split to the Gate in (Trig) CV input on the Thor Step Sequencer (at the bottom of Thor).
Routings on the Back of the rack
Press Play, and if you will hear the Bass Drum playing. If you don’t hear anything, be sure to check the Pattern in the Redrum and make sure there are some Bass Drum parts in the Pattern Sequencer.
Still on the back of the rack, select the Spider Merger/Splitter and Thor together by shift+clicking on both devices. Right-click and select “Duplicate Devices and Tracks.” Then connect the Left and Right Audio Outputs (1 and 2) from the second Thor into the Left and Right Audio Inputs on Channel 2 on the Mixer. And connect the Gate Out CV from the Redrum second channel into Split A on the Spider CV Merger/Splitter.
Flip the rack around to the front and create a new drum sound in Thor, maybe another Bass Drum or Snare. Repeat this process until you have all 10 Redrum channels filled up. Congratulations! You’ve just created a complete drum kit.

Vocoder Filtering

This trick was shown in Matt Piper’s great Youtube video where he set up a Vocoder to filter his drums. To see the video, visit his tutorial here: propellerhead-record-reason-vocoding-with-drums

Once you have your drum kit set up, go to the back of the rack, and select the Mixer. Hold Shift down, and create a BV512 Vocoder, Thor, and a Spider Audio Merger/Splitter.
Move the Left and Right Audio input cables on the Combinator (From Devices) to the Left and Right Carrier Input on the Vocoder. Then connect the Left and Right Carrier Output from the Vocoder to the Left and Right Audio input on the Combinator (From Devices).
Route The 1 Mono/Left and 2 Right Outputs from the Thor device to two Left Merge channels on the Spider Audio Merger/Splitter. Connect the Merged output from those two cables to the Modulator Input on the Vocoder. With our routing set up, flip around to the front of the rack.
Vocoder Routing setup
On the front panel of the Vocoder, set the Band Count to 4 Bands (I also found the 8 and 16 bands work well, depending what kind of sound you are looking for). Move the Shift knob to around -24, and Decay to around 80.
In Thor’s global top panel, set the Polyphony to 1, Release Polyphony to 0, and Key Mode to mono Retrig. In the Voice section, add a Noise Oscillator in Slot 1, set the Noise Wave to Color, and Noise Mod to around 36. Then turn on “1” to send the Oscillator to Filter 1 slot (which is on Bypass by the way). Turn off everything else except the Filter and Amp Envelope. In the Step Sequencer section, set the Run Mode to Repeat.
The front panel settings for the Vocoder and Thor Modulator

That’s really all there is to it. Not too complex, just time consuming to create all your drum sounds in the various Thor devices. But it’s very rewarding when you have your own custom drum kit set up just the way you want.

Where do you go from here?

You can try the same setup with a stack of Subtractors or Malstrom devices, or any combination of Subs, Mals and Thors to create your custom drum kits.
You can add a reverb and a delay to your drums. Also, for an instant doubling effect, you can modulate a button on the combinator to switch from 1-2 steps in all the Thors at once. This doubles up the drum beats (see below for this setup in my own Electro Drum kit).
Try going into the Thor which is used as the Vocoder’s Modulator, and switch the Oscillator 1 Noise wave from Color to Static, and then set the Noise mod dial to around 30 or so. You’ll create some very interesting glitch effects.
As you can see I’ve added a few effects here and there. There’s two phasers tied to the Hi Hats, for example. In this same way, you can chain some effects into the drums individually. Try adding some scream or even vocoding the drums separately. However, if you do, you’ll have to realize that the more effects, the more CPU intensive this gets. As it is, I only saw 2 bars on my CPU meter. Not too bad. Definitely less intensive than the last kit I put together.

Electro Drums Combinator Controls

Pitch Bend: Unassigned.

Mod Wheel: This controls the Band Count on the Vocoder from 4 bands (no modulation) to FFT (512) when pushed all the way up.

Rotary 1: Voc Filter – This controls the Noise Mod from the Vocoder’s Modulation Oscillator. This can be used to shape the sound of the Drum Filtering through the Vocoder.

Rotary 2: Shift – This controls the Shift parameter on the Vocoder. Again, this can be used to sculpt the sound of the Drum’s Vocoder Filter.

Rotary 3: Pattern Seq. – This knob is used to switch between all 31 patterns in the Redrum. You can assign any patterns you like in the redrum and it will be tied to this knob. In this way, when you’re playing the drums, you can switch on the fly. In my drum kit, I threw in a bunch of random patterns so that you can hear something playing no matter where the knob is set. Note that if the knob is turned fully left, an empty pattern plays (essentially turning the Pattern Sequencer off and silencing all the drums). This is good if you need an empty spot in your song.

Rotary 4: Master Level – This controls the master level of the Submixer, so that you can adjust the drum level globally.

Button 1: Doubler – This doubles all the drum beats via the Thor Step Sequencers. When on, the steps are set to 2, which will play two beats anytime the drum is triggered. When off, only one drum beat will occur when the drum is triggered.

Button 2: Alt Filter – This quickly switches the filters used to modulate the Vocoder, as well as adding a Scream and Reverb effect to the drums. I wanted to make this drum template as versatile as I could, so I thought why not add a completely different sound in the Combinator for some fun. It gives the drum sounds a completely different and more electronic (less organic) sound.

Button 3: Master Bypass – This button controls the Mastering (M Class) devices, as well as the Vocoder filter. If you don’t want to add any mastering or Vocoder Filter to the drums, turn this button on. The Drum sounds are then completely dry (or as they originally sound via the Thors). Leave it off if you want the drums compressed, EQ’d and Vocoded.

Button 4: HH FX – I added some Phaser FX to the High Hats just to give them a different feel. You’ll just have to try it out and see if you like it. I thought it was a cool sound, so I kept it in there as an option for you.

So let me know what you think of this setup, and if you have any other ideas or have some great tips for drum creativity, please feel free to share your comments.

Good Luck!

Ed’s Reasonable Help 2010

EditEd4TV’s Reasonable Help for 2010
Available now at: http://www.baumanproductions.com/reasonablehelp.html

It’s rare that I advocate a specific refill. I can actually count on my fingers how many refills I rely on in my own work, and would rather try and figure out the answer myself or else try building my own instruments and combinators. But when it comes to inspiration and I’m looking to expand my knowledge I can’t think of anyone better than Ed Bauman. In his latest refill offering “Reasonable Help 2010” he provides you with 50 amazing combinators which push the envelope on what Reason can do. And he sets off to prove that most anything you can think of in your head can be worked out in Reason routings and device Combinations.

Without a doubt this is one of the best refills I’ve seen, and it’s not because it’s packed to the brim with a ton of new sounds or new patches. If you’re looking for new sounds, there are other refills out there that can give you off-the-shelf sounds. This refill is aimed straight at the Sound designer who wants to learn how to route devices in reason. It’s also aimed at solving common problems that people face in Reason. How to create a noise gate? How do yo scrub your audio, how do you make reason strum a guitar? All of these questions and more are answered. Other common questions from the forum are answered too. How do you put your vocals through a vocoder to get that Telephone voice? Want an instant Steam Locomotive with Whistle and train speed included. It’s all in there.

In a nutshell, if you’re willing to sit down and look through the patches to see how they are routed, and read the accompanying documentation, you’re going to learn some new tricks and better your Reason skills. If you’re just starting out, you may not entirely be ready for this one. But if you have a decent grasp of how to route your devices together and want to take yourself to the next level, these 50 patches will open your eyes to some brand new ideas. The true benefit of Reasonable Help 2010 is in the educational value. What better way to expand your Reason knowledge than having a 50-session class provided by one of Reason’s top gurus: Ed. He’ll hold your hand the entire way, and speaking from personal experience, he’s always there to help if you get stuck. I highly recommend you purchase your copy now. At $50.00 it’s an awesome deal.

Ed was gracious enough to provide a free .rns file from Reasonable Help: EditEd4TV_GateModifier.

EditEd4TV's Reasonable Help Gate Modifier Combinator — EditEd4TV’s Gate Modifier Combinator

Ed also had some comments about this file, as well as some great insights into his work flow:

The reason I made this Gate Modifier patch was simple – the Slice Output of Dr. Rex is basically useless for triggering synth pads. I wanted something that could easily serve as an “in-between” module to transform CV data into something more useful. The concept is pretty simple: just take incoming slice data, which is basically just a small millisecond CV burst, and send that to Thor’s Step Sequencer CV Input Gate In Trigger. That small gate burst is perfectly fine for triggering the Step Sequencer. That trigger is used to trigger Thor’s Amp Envelope, which is held open depending upon the value of Combinator knob 1, which adjusts the Step Sequencer Gate Length value. The Amp Envelope attack and release values are adjustable as well. There’s also Gate Strength, which can be inverted so it sends negative CV values instead of positive values, which can be used as sort of a “ducking” feature.

So how do I go about this sort of thing? Well, most of my patches always begin with a need, a want, a solution to a problem. I always start with a Combinator with a Mixer inside. I may ditch the Mixer later if it isn’t needed, but that’s the default. At the heart of most of my problem solving solutions is Thor, since it offers so many incredible ways to take incoming audio or CV and manipulate it to death. There’s almost always a way to solve a problem with Thor.

So sometimes I’ll just decide I’m going to tackle a problem, I’ll make the Combi and put the Mixer in there, along with one Thor, and I’ll just sit there and think, maybe for a few seconds, or maybe an hour or two… just thinking. I’ll experiment along the way, maybe draw things out on paper so it makes sense visually instead of just mentally (sometimes if I’m away from home and I’m sitting somewhere on a video shoot I’ll start drawing out design concepts that just come to me, I’ll draw them out on paper, you can see 3 of them on the last few pages of the RH’10 PDF manual).

The worst is when inspiration hits when I’m driving, and all I can do is dictate the concept into my cell phone, which is somewhat difficult depending on the complexity of the design stuck in my head. So, once I’ve come up with a solution, and I design it in a Combinator, I’ll sit and stare and think for maybe an hour or so, thinking… “If I’m the end user of this, what will I hate about it, what will I want, what would I change”, and I go about solving those problems. Sometimes this can be really frustrating because I’ll come up with additions before I stumble upon some solutions, so I may end up programming knobs 3 and 4 to do something, then I discover it’s a much better solution if I have, say, the Mod Wheel do the same job as those two knobs, so I have to redesign my modulation routings and perhaps some CV cabling as well.

Eventually I land on the final design, and I’ll have some buttons or knobs left over empty, so I’ll try to come up with some fun stuff at that point. That’s when I wish the Combi Pitch and Mod Wheels had labels as well, since they’re stuck being labeled via the Combi skin… Sometimes I use those two wheels for other things and I’m too busy/lazy to design a custom skin for those different purposes. Also, I try to avoid tying up a knob with the “do not touch!” label, though sometimes it’s necessary. And that’s when I wish the Combinator was 8×8 instead of 4×4, and I wish it had, say, 8 CV inputs and 8 CV outputs on the back as well, not necessarily tied to the knobs if you don’t want them to be.

And here is an explanation of the inner workings of the rns file, direct from Ed’s PDF documentation:

EditEd4TV_GateModifier

This Combinator allows you to modify/extend Dr. Rex gates into a more useful state.

Knob 1 “Gate Length”: This knob adjusts the gate length.

Knob 2 ” Gate Strength”: This knob adjusts the gate strength.

Knob 3 ” Gate Attack”: This knob adjusts the gate attack time.

Knob 4 ” Gate Release”: This knob adjusts the gate release time.

Button 1 “2 Ordered”: This button switches the gate mode from single to two varying triggers.

Button 2 “16 Random”: This button switches the gate mode from single to 16 random triggers.

Button 3 “n/a”: This parameter is unassigned.

Button 4 “n/a”: This parameter is unassigned.

Pitch Wheel: This wheel is unassigned.

Mod Wheel: This wheel is unassigned.

Details: This Combinator is particularly useful when used with a Dr. Rex loop player. On the rear panel of Dr. Rex you’ll find a Slice Gate Output. Note that this CV signal is routed to the Spider CV Slice Splitter – this is purely for demonstration purposes. Note that the first split output is routed directly to Thor 1 Pad’s Filter 1 Frequency Modulation Input, whereas the second split output is routed through the GateModifier, then into Thor 2 Pad’s Filter 1 Frequency Modulation Input. Play back the demonstration sequencer and solo Mixer channel 1. This is the drumbeat that we’re using to send gate signals to the two Thor units. Return the Mixer back to normal and now solo Mixer channel 2. This is Thor Pad 1. Notice very short and barely useful clicks in the audio signal, which is a result of the very short slice gates affecting Thor’s filter. Return the Mixer back to normal and now solo Mixer channel 3. This is Thor Pad 2. Notice the much more active and useful affects on the audio signal, which is a result of the GateModifier creating better gate signals.

Inside the GateModifier you’ll find a single Thor unit. CV control needs to come directly into this Thor, into the Step Sequencer CV Input Gate In (Trig) jack. Each incoming slice gate will trigger a step in the Step Sequencer. This first step is set for a gate of 0%, but Combinator knob 1 (Thor Rotary 1) is used to adjust this gate length up to 100%, thereby creating much more useful gate lengths. This new gate signal triggers Thor’s Amplitude Envelope, which is then routed to both CV 1 and CV 2 outputs, where CV 2 is a polar opposite of CV 1. Though not used in this demonstration, know that CV 2 output is ready for use if needed as an inverted output. Combinator knob 2 is used to trim the strength of both of these outputs. Note that Combinator knob 2 is bipolar, with no affect on strength when centered. Right of center results in positive results (with negative results from CV 2 output) and left of center results in negative results (with positive results from the CV 2 output).

Combinator button 1 is used to change the number of steps of the Step Sequencer from 1 to 2, in a back and forth pattern. Step 2 contains modified parameters that create a different result than step 1, thereby making a noticeable difference in how the gated signal controls Thor. Combinator button 2 is used to change the number of steps of the Step Sequencer from 1 to 16, in a random pattern, with all 16 steps set for variable settings that result in an unpredictable, yet still slice accurate, gate signal.

Combinator knobs 3 and 4 adjust the Amplitude Envelope attack and release times, respectively.

In our example we’ve sent the gated signal to Thor’s Filter 1 Frequency Modulation Input CV jack, but you can of course route this signal anywhere you like. You’ll find this new signal works much better than the standard slice output of Dr. Rex. This GateModifier is also useful to modify the gate signals coming out of a ReDrum, where the ReDrum channel is set for gate mode 0 (sawtooth wave). Though you can get workable results by switching the ReDrum gate mode to 1 (square wave), this potentially affects the ReDrum channels audio waveform; in the case of, say, a crash cymbal, the affect of switching the gate mode to mode 1 are more often than not unacceptable (muted crashes). The alternative is to sacrifice a ReDrum channel to use purely as a gate signal in mode 1, which may also be unacceptable. Your best option may be to use the GateModifier Combinator, allowing you to select any gate output for use.

The Dr. Rex, Spider CV, Thor units, and sequence in this file are provided simply to test the Combinator’s features.

A huge thanks to Ed for putting this package together. You truly are an inspiration to all of us Reason users. Please keep doing what you’re doing and I look forward to your future products as well. You can purchase Ed’s Reasonable Help 2010 here: http://www.baumanproductions.com/reasonablehelp.html