Contribute

 

As this site grows in content and an abundance of great ideas from users such as yourself, I’m finding that more of my time is spent putting together new material and generally trying to make this a great resource for everyone in the Reason/Record community. I’m also getting different requests from users on how to do certain things, and also many great people out there are sparking me to find new ways to achieve things in Reason/Record. I don’t want this to stop, so please keep the questions coming. I’ve always believed that this site is a joint partnership between you and me. And I would certainly like to keep it that way.

So now is the time in this partnership in which I ask you to give something back, not just to me, but to everyone else out there in the Reason/Record community. Here is how you can help both of us achieve our goals:

  • Donate. This helps me pay for hosting costs and my time creating the patches and tutorials for you. If you like what you’re reading, watching, or listening to on this site and want it to continue, or if you use my patches in your work, then please make a donation. Every little bit helps and is greatly appreciated. I do 100% of this for free, and I would like to keep it that way.
  • Donate a link or a mention. Spread the word in any way you can. Let people in other message boards and blogs know about Reason101.net. Post a link in your own sites and blogs, and tell everyone that this resource is completely 100% free for any and all musicians under the Creative Commons 3.0 license.
  • Donate your comments and questions. Positive critical comments are always welcome. If you have a better way to do things, or know a workaround to an issue that I don’t, we all benefit. If you have a question, I’ll try my best to answer it, work out a patch for you, or help you in any way that I can. If I can’t, I’ll usually have a suggestion or two on where you can find the answers you seek. Just please keep things on topic and be specific and clear.
  • Donate an article, patch or refill. I won’t guarantee I’ll post it or review it, but if you have some method or technique that you think is really hot, or you have some kick ass sounds, send me an email and let me know about it and I might just feature you under the “Contributor” section. Email me privately if you want to know where to send any CD or DVDs if your refill is too large to send. Are you really going to say no to free promotion?

Thank you for taking the time to read this and do your part to make this site and all the content within it a success! Now let’s go make some great music!


  55 Responses to “Contribute”

  1. Thanks Carmen, I appreciate you checking out my tracks. And Tackhead was a pretty great group of folks back in the day. They did some awesome and innovative music for their time. I don’t think they quite got the recognition they deserved.

    Good luck with the Dr. OctoRex adventure. It can be quite interesting when you start messing around with that Slice Edit Mode. ;-)

  2. thats rob im going to mess with that on my day off…..and by the way i like the track ‘severed’ i heard and i checked out’ tackhead’ good stuff

  3. @Carmen,
    The “Slice Edit Mode > Out” is tied to the audio outputs on the back of the Dr. OctoRex. Refer to the manual for more information about this. Essentially, There are 10 outputs on the back of the rack (4 sets of L/R PLUS the main audio left / right output). Now when you are in the “Slice Edit Mode > Out” selection, you can “paint over” each slice with your cursor. Take your cursor and draw over a single slice going from the bottom to the top (drag your cursor) – notice that there are 5 positions that can be selected: 1. No selection, 2. slice is filled a quarter of the way up, 3. slice is painted over half way up, 4. 3/4 way, and 5. fully shaded.

    Ok… these 5 positions correspond to the 5 pair of audio outputs. No selection = Main Left/Right output; 1/4 = Output 1&2; 1/2 = Output 3&4, etc. etc.

    Now you can select one or more slices to go to any of these audio outputs you wish. The loop will still play back normally from start to finish (assuming you haven’t edited the “Alt” parameter), but as each slice is triggered, it will be sent to the output you’ve determined for it based on it’s output setting. Make sense so far? Good.

    Now, if you think about it for a minute, you’ll see that if you want to process each slice with different effects, you have a limitation of 5 slices for each Dr. OctoRex device (in a Stereo configuration), or 10 slices in total (for a Mono configuration). To process more than 10 slices with different effects, you need to jury-rig it so that you have multiple Dr. OctoRex devices playing the same loop at the same time; using the first Dr. to process the first set of slices, the second to process the second set, etc. etc.

    So the real question is this: do you really need to process each and every slice in a loop differently? If so, there’s a lot of work and jury-rigging involved. However, if you have a 20-slice loop and you want to process 4 slices in one way, 5 slices in another, etc. you can easily do this in a single Dr.

    Now, this all doesn’t even touch upon using a loop in a Nurse Rex module inside a Kong. But there’s another idea for you.

    Oh and one last thing. This conversation is probably getting very specific so let’s take it into email if you need more clarification than I’ve provided here. Just shoot me an email directly (link at the top of my blog), and we can discuss it further offline. And if you’re STILL having problems, send me over the file you’re working on so I can take a look and we can both be on the same page. But first, try to understand what I’ve written here, as well as reading the User manual on the Dr. OctoRex and how it works.

    All my best,
    Rob

  4. Hi rob, i have my dr octo outputs and effects going and its working other than one thing.I’m routing my effects only one slice at a time..but if i want the entire patch with the effects..its alot of work..{routing slice at a time}..if i click on the ‘out’ like you said in slice edit mode it only by- passes that slice.. there must be something i missed in order to get the entire effect on the entire patch.

    ~Carmen

  5. @Carmen,
    No problemo!

  6. thank u

  7. Carmen,
    There’s a few ways you could do this. I have one video online that shows how it’s done. But it’s probably easier for me to just tell you.

    Open a Dr. OctoRex and load up a loop in slot 1. Then click on the “Slice Edit” button.
    Select the “Out” label just below the slices.
    Now you can select different slices to be output to different audio outputs. If you flip to the back of the Rack, you’ll see all the separate output jacks from the Dr. OctoRex. Simply send these audio outputs anywhere you like through any effects you like, and then back to a mixer channel.

    There you have it. Different slices processed in different ways. Simple right? I actually go over this in the following tutorial:
    http://www.reason101.net/101-creative-reason-projects/35-glitch-box-redux-r4-5/
    so have a look there and see if that answers your question.

    Note: If you need more outputs, either copy the Dr. OctoRex and send some of the slices out of the first Dr. OctoRex and the other slices out of the second Dr. OctoRex. This might start gettting a bit complicated, but you can do it.

    OR you can load a Rex file into an audio track and use the slice tool to slice it up into bits and put each bit on their own audio channels and then process separately.

    OR you can load a Dr. Rex file into an NN-XT where you can send to 16 separate outputs for separate processing.

    And then there is Kong.

    Explore explore explore.

    hope that helps.
    Rob

  8. Hi there rob,

    Do you have a video for putting individual effects on each Dr. Octo rex slice?

  9. @Miguel,
    The best way to add automation is to use a MIDI Controller. That way you can use a physical knob or fader to add automation. Set up the MIDI Controller so that it is “Communicating” between the controller and Reason, then “Record” your automation into the track in question. For example, if you are automating a Combinator Rotary, make sure the track’s “Record Enabled Parameter Automation” button is enabled (in Red in the main mixer. Then press Record, and start to move the knob or fader around to record your automation. You can draw it in as well, but that may or may not be faster, depending on what you feel more comfortable with.

    Hope that helps.
    Rob

  10. Hi there,

    Rob what do you think is the best way to put in automation.Let’s say you want reverb on block one and not block two.Just by- pass all the time then draw it in in block one with enable and whatever else u want?Drawing it in is a bit diffacult because it doesnt alway’s do excatly what you wish it to do.

  11. Cole,
    I’d be happy to take a look at what you have. Shoot me an email at webmaster@reason101.net. If you have an article you want to share and it’s got some cool tricks, I could put it up in the “Contributions” section. Or if it’s just some patches you want to share, I could post them in the “Patches” section. In any event, send me what you have along with your thoughts and I’d be happy to take a look. Just give me a few days, if not a week or more, as I have some other things in the works currently. But I will get to it.

    And thanks for thinking about contributing. That’s very nice of you.

    All my best,
    Rob

  12. I could put together some material on piano sounds. I have ideas and patches I’m happy to share.

  13. @Asante,
    I would start with the Noise Oscillator in Thor. Working with that Oscillator, you can create some convincing Engine-type sounds. Also, my friend EditEd4TV has a refill called “Reasonable Help” and I believe there’s a patch in there which does this. Check with him about it. You can find this refill online here: http://baumanproductions.com/reasonablehelp.html Aside from the Engine sound, you’ll learn a lot about programming in Reason (if this is your thing). But shoot him an email and ask him about it. Hope that Helps. And thanks for the comment. I try my best here at Reason101 to provide some useful information for the Reason community. Rob

  14. before stating just have to say really appreciate the stuff u doing here man.
    Sorrry if this has already been asked but. i’ve seen a lot of different uses for the reason but i was wondering if it was possible to make a car / motor bike engine sound using synths ect. and be able to control the revs using the pitch or mod wheel. would be a massive help i need this patch for a project i’m doing

  15. Amy,
    I’m always interested to see what you guys come up with. So try a few loops out and even if you succeed, send it my way. I’d love to hear it. :-)

    Rob

 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>

© 2012 Reason 101. All work under Creative Commons 3.0 license. Suffusion theme by Sayontan Sinha