May 042012
 

In this fifth installment of my series on better patch design, I thought I would take a much-needed break from all the theory and synth jargon, and instead focus on some creative Thor synth ideas. I can almost hear the collective yawn after reading the last few articles. So let’s spice it up with a few videos that showcase some of the concepts we’ve talked about, but more importantly, let’s just have some fun fiddling around in Thor.

You can download the project files here: better-patches-part5. This zip consists of a few Thor patches and demo .reason files that outline the ideas below. You can use any version of Reason above 4.0 (when the Thor synth was introduced to the world of Reason). Enjoy! Read on for more about these ideas.

The Hoover Sound (Redux)

Chris Petti did a great video on how to create a Hoover Sound in Reason using some Analog Oscillators and a Multi-Oscillator to fatten everything up. If you haven’t seen his video, I’m going to showcase it here. Have a look and build the patch first. We’ll use this as the base building block and figure out a few modifications you can add to enhance it’s flexibility. Here’s his video:

This patch is a really great sound as it is, and Mr. Petti does a bang up job of presenting it to us (not to mention his videos are way cooler than my own DIY camera work). Nonetheless, there’s lots you can do to add to his patch. So I’m going to start where Chris left off and see what we can do to make his patch more flexible, taking it to the next level of patch design. Check out the video below:

Button Trigger Madness

In my never-ending quest to solve interesting problems in Reason, I came across this dilemma. How can I use the button in Thor as a toggle switch to step through the Thor Sequencer? I wasn’t happy with the “it’s not possible” answer. So here’s what I devised. It’s actually a nice simple solution which allows you to use the Thor button as a cycler. The power in this trick is that when the Sequencer is set to “Step” mode, the button can be used to cycle through all 16 steps. If you watch the video below, you’ll see how this can help you devise Thor patches that contain 16 distinct sounds within a single Thor patch.

Here’s the short version of how you set it up (see the Chiptune video below for a practical application):

  1. Open a new Reason document. Go into Edit > Preferences, and on the “Audio Tab,” ensure the Sample Rate is set to 44,100 (should be the default). Then close out of this dialog.
  2. Create an initialized Thor device.
  3. Turn off the “Step Sequencer” green light in the Global section’s “Trigger” area. While we’re doing that, label Button 1 the “Stepper.”
  4. Turn off the Global Envelope’s “Gate Trig” green light.
  5. Turn up the Global Envelope’s Sustain to full (0.0 dB), and turn down all other Global Envelope parameters to zero.
  6. In the Modulation Bus Routing Section (MBRS), create the following two lines on the left side:

    Button1 : 100 > G.Env Gate

    Global Env : -100 > S. Trig

  7. Now, enter the following in the MBRS on the first line on the right side

    Button1 : 100 > S. Trig : 100 > S. Trig

  8. In the Step Sequencer section, change the Run Mode to “Step.”
The Thor Button Cycler, showing all the changes that need to be made to the Thor init patch

The Thor Button Cycler, showing all the changes that need to be made to the Thor init patch

Now when you press button 1, you’ll notice that the Step sequencer moves forward one step when turned on, and another step when turned off. In essence, we’ve tricked Thor into thinking that both button “on” and button “off” should trigger the Step Sequencer to “Run.” The Global Envelope was required because it is always left on, and so can be manipulated without requiring a Midi Note to “gate” the envelope.

You can now use the Step Sequencer’s Note, Curve 1, Curve 2, Gate Length, etc. to control any aspect of the Thor patch that you like, and build up different sounds at each step of the Step Sequencer. Think of generating 16 different Bass tones or 16 different Pads, Strings, Drum sounds, or any interesting sounds you can dream up. The only limitation is that you won’t have access to the Global Envelope — a minor limitation given the fact that you can get Thor to generate 16 different sounds from a single patch.

Chiptune Sounds (Redux)

As I was experimenting one day, I stumbled upon. . .

. . . a wonderful way to create some Chiptune sounds using the Wavetable Oscillator in Thor and affect it’s “Frequency (FM)” parameter with a stepped LFO. Sometimes it’s not how crazy you can make things. Instead, it’s about keeping things ultra simple. Have a look at the video to see how I paired this Chiptune idea with the above “Button Trigger Madness” idea to create 4 different Chiptune sounds within a single Thor patch.

Here’s the video:

Creating a Sweep

This is an interesting patch that will show you an alternate use for the Velocity performance of the Patch. Since the sweep changes the Volume (along with a few other parameters) over time to sweep the sound upward to full volume, you probably don’t want to have Volume modulated by Velocity. Instead, you can use the Velocity information from the musician’s performance to adjust the speed or rate of the sweep, making it rise slowly when the keys are played softly, and faster when the keys are played harder. You could also set up a button to reverse the Velocity behavior, if you like (see my previous tutorials in this series for explanations on how this is done).

Here’s the video:

Using the FSB for Practice

Another idea I had was to take patches from one synth and transfer them over to another synth within Reason. In this video, I’ll show you how you can take one of my favorite Subtractor patches and recreate the sounds inside Thor. While not every sound from the Subtractor (or Malstrom, for that matter) can be accurately reflected in Thor — they are, for the most part, different synthesis algorithms and techniques underlying each synth — you can still get pretty close, depending on the patch you start out with. It’s good mental exercise. It will help you get to know all the synth parameters and how they work. And you have an endless array of sounds at your fingertips in the FSB.

So why not give this a try with your favorite sounds? And there’s also another reason to transfer patches from the Subtractor into Thor: At the end of the transfer, you’ll still have the Rotaries, Buttons, and step sequencer to enhance or expand on the patches — something the Subtractor lacks. So here’s the video to show you the method I used:


So that’s part five in the series. As always if you have any questions or want to contribute your thoughts and ideas, I encourage you to do so. I’m always interested in hearing new ways you’ve found to work with Reason. All my best until next time.

  2 Responses to “78 – Creating Better Patches (Part 5)”

  1. Hey Rob,
    There is an alternative approach to programming the button that will not use the global envelope.
    In the MBRS (Source/Dest 1/Dest 2) program:
    Button1 / -100 CV 1 Out / 100 S. Trig
    Tab the rack and connect CV 1 Out to the Gate In (Trig).
    The only downside is that you need to save as a combinator to preserve the wiring.
    Thanks

  2. Hey Sterio! Long time no talk. Hope you’re doing well.
    You are absolutely right that you can use the CV on the back of Thor. And you can put Thor inside a Combinator and apply the stepping via a Combinator button as well if you are so inclined. There are definitely lots of options. But my goal here was to figure out a way to do it without the need for any other devices, and without the need to use any CV. Why? Because using the Global Envelope method is the ONLY way to save it as a Thor patch (as opposed to a Combinator patch). It’s also more economical and compact (not that this matters too much). But still, it was a bit of a challenge.

    There’s an even easier way: Assign a note value to the button in Thor, and use a Midi Key to step through the sequencer. But then you’re using a Midi Key, and I wanted to avoid that as well. In the end, I think it was more about the interesting challenge of putting it on a button and making it as simplistic as possible. But I very much appreciate you proposing the alternate ideas. All these ideas are completely valid.

    Cheers!

 Leave a Reply

(required)

(required)


*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>