As I mentioned in an earlier post, you can press the 'tab' key to flip your rack around. As you'll notice, there are many wires in which you can unplug and replug into tens of outlets on each patch. In a sense, you are layering from birth (oscillator) to the final product (mixer), and each patch inbetween these two points in an individual layer. Layering is a key concept in almost every program, and even in programming itself (especially object-oriented programming)!
The above picture is an example of HTML table layering. You start with the original square, and through individual layered cuts you have the final cell product. Patch layering in Reason is quite similar in a metaphorical sense.
I was talking with PotatoFinger the other day, who is part of the famous dubstep duo PotatoFinger & Fabian. I asked him how he orders the patches to his reese. His response was: "Instrument-eq-comp-scream-eq-unison-comp-stereoimager-scream-eq-vocoder (for the eq)-comp-maximizer." Now to a newbie to Reason this may seem like jibberish, but if you know what you're looking at this is a pretty golden setup. Notice how an EQ is always placed BEFORE the compressor and not after. EQing is always placed after a distortion patch (hence why it's always available within the Scream unit, handy eh? The frequencies on which it operates are hard set within the program... so unless it sounds good to your ends, don't use it.). At the end of the chain, he compresses and THEN maximizes it.
The word of advice is to pay attention to the order of patches in your chains. You'll notice that certain combinations work beautifully together, while if you reorder them they will work against eachother. The best way to figure this out, however, is to understand what each individual module does. So keep reading!
No comments:
Post a Comment