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.
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.
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.
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
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.
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).
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.
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!
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.
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 common and uncommon 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!
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 Unipolar setting on the back of the Matrix produces a Unipolar Curve on the front panel display (CV value 0 – 127)The same curve but shown in Bipolar mode (CV value -64 to +64). The line across the middle of the display is where the value is zero. Anything below this line is negative, and anything above this line is positive.
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:
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.
