Recording 101?

[SeikoT123]

Can anyone recommend some basic sources online where one can study recording basics? I mean very basic, such as signal flows (what's a "bus"?) and what various effects do (what's a "limiter," and how does it differ from a "compressor"?). All in a DAW context (like DP!) would be great, but not necessary.

I am discovering as I work with DP8 that there seems to be an assumption (probably accurate) that most users already have familiarity with recording fundamentals. Alas, I do not.

Thank you in advance for your help!

[MIDI Life Crisis]

http://bit.ly/12qnMV5

and here:

http://intenseproductions.blogspot.com/ ... s.html?m=1

[NazRat]

There's a lot of good training videos @ Groove 3 (http://www.groove3.com/str/home.php) covering several products plus categories like mixing. The DP videos are excellent and an All Access Pass is very reasonable these days. YouTube is a great source also, but mixed in with the good is bunch of somewhat questionable material.

[bayswater]

Craig Anderton has written a zillion books that cover most aspects of making music with DAWS and synths. They're everywhere: I've seen them in public libraries and in drug store discount bins.

Sound On Sound has hundreds of articles going back 20 years or so that are free to view if they are more than six months old. A lot of them give specific DP examples. Here's an example:

http://www.soundonsound.com/sos/feb11/a ... p-0211.htm

[Prime Mover]

First off, welcome to the world of recording/engineering! And welcome to the forums, it's a great place, and I guarantee you'll learn a lot.

(what's a "bus"?) and what various effects do (what's a "limiter," and how does it differ from a "compressor"?).

Buses are simply signal routers, they're the "cables" you use to route the output of one track to the input of another. A basic mix setup is to route similar instrument tracks into a "subgroup" track (for instance, have a subgroup of all your drum tracks), which you can control and process together. In digital workstations, you call these "Aux" tracks, which you can create from the menubar. They contain no audio recording in of themselves, but are used to process incoming signals. In the drum kit analogy, you would have separate tracks for snare, kick, overheads, toms, etc. You would create a bus, and assign the output of all those audio tracks to that bus. Then you would create an aux track and assign the INPUT of it to the same bus... now you've successfully routed all the instruments to one aux subgroup. You can create buses right inside the input/output dropdown menu, but an even better way is to create them in the "bundles" window, and then you can rename them to something more descriptive (a total lifesaver).

Another thing you should be aware of is serial vs parallel signal flow. In parallel, a track's output is just bused into another track's (usually an aux) input, as in the drum subgroup analogy. In serial routing, a duplicate signal is "sent" off the side of a track to a different destination. This is most typically used for reverb. The most common and best reverb practice is to have a dedicated reverb aux track with a reverb plugin set to 100% wet. Instead of passing a track's main output to the reverb, you would use a "Send" from off the audio track to the reverb track. So you'll have the dry audio that's simply output to a subgroup or main out, and a side signal that goes through the reverb track. The output of the reverb track would be to the main out or a subgroup, and eventually mix back in with the dry signal. The advantage to this is that you can use one reverb plugin for many different tracks, by sending from each of them, instead of having to create multiple instances on each track. Another advantage is control: with a parallel reverb, you're beholden to the "wet/dry mix" setting, which will decrease the dry output as you introduce more reverb. But more often than not, you want to raise and lower the level of the reverb without changing the volume of the dry sound. If it's sent off the side, you can automate either the send output level, or the fader on the reverb aux track, and not worry about it interfering with the dry level. And finally, often times it's good to EQ a reverb, after and even sometimes before it hits the plugin. Reverb units often have simple EQ stages, but they're typically less user-friendly and less powerful than the average EQ plugin that you're used to using. With a separate reverb aux track, you can forget about the built-in amenities, and apply your own EQs, compressors, or other processes that you might want to be part of your reverb sound (I'm sometimes known to use distortion in a reverb channel to thicken up a sound).

As for Compressors/limiters/levelers. You are correct, they are all technically the same thing, but with different settings and purposes. But that's not particularly fair because even compressors are used for totally different tasks. And though limiters are most typically used for mastering purposes, some industrial limiters and sought after for their performance as compressors. Limiters are compressors with an extremely high compression ratio, so that when a signal hits the threshold, it can't increase any further. These are referred to as "brick wall" limiters, and are commonly found at the end of a mastering chain. They're not as well suited for mixing because they can easily destroy the natural flow of an individual track because of their extreme signal-processing quality. For a more transparent sound, you would typically use a standard compressor with a lower ratio (1.5 - 6, or something in that range), and give it some attack time to allow for attack transients to still punch through. The term "leveler" is basically synonymous with compressor, just being more descriptive of its function. Often levelers use multiple parallel compressors, or non-parametric compression techniques (such as photosynthetic cells... the MasterWorks Leveler simulates this) to achieve smooth exponential compression. Don't quote me on this, because I don't even think there's an exact standardization of terminology between "compressor" and "leveler", but from my experience, this seems to be the only common difference. Levelers tend to have more going on under the hood, and less specific control for the user, so different levelers are sought after for different purposes. But many things called "compressors" also fall under this definition, so the line is blurry.

I am discovering as I work with DP8 that there seems to be an assumption (probably accurate) that most users already have familiarity with recording fundamentals.

I think this is basically due to the fact that DP is a lesser-known, but older DAW. It's found its biggest niche among film and television composers, and is common around Hollywood. Unlike DigitDesign (now Avid), MOTU didn't do an aggressive push of massive hardware/software packages for recording studios. Its used a lot more by composers, artists, and bands. But the reasons for that are largely due to marketing and history. All professional DAWs basically can functional admirably in many different situations. Because of its niche audience, it's often not the first DAW that a users has used (for me, it's the third, actually, I came way of Sonar and Pro Tools), it's fairly common for someone who is a long time user of another DAW to fall in love with the workflow enhancements of DP. So yes, it tends to attract a more seasoned audience.

[kats_corner]

Another thing you should be aware of is serial vs parallel signal flow. In parallel, a track's output is just bused into another track's (usually an aux) input, as in the drum subgroup analogy. In serial routing, a duplicate signal is "sent" off the side of a track to a different destination.

Just a note. If I'm reading that right, I think there is a conceptual reversal there regarding series vs parallel.

When the signal goes directly from one unit's output to another unit's input, such that things happen one after the other, in series, this is a serial path:

---[]---[]---

While the drum subgroup analogy may initially sound like a "parallel" scenario (many into 1), that subgroup is encountered *after* the individual drum tracks, which places the subgroup in a sequential position in the signal chain, i.e., in series (serial). If all drums are routed to such a subgroup, and you mute that subgroup, no drums will be heard; because the subgroup is routed in series after the drums, where it can break the signal chain for all the drums.

When a duplicate of a signal is extracted mid-path (usually via an aux send either pre- or post-fader) so that it continues in both, the original channel strip, and a separate channel strip or bus (for reverb?) at the same time, side-by-side, this is a parallel path:

---<===

If you mute the reverb track, you'll still hear the dry tracks, because the dry tracks and the reverb bus are not sequential and do not depend on each other (well, duely noting the behaviour of post-fader aux sends WRT channel muting of course). They are routed beside each other, in parallel.

Just my $0.02....

[Prime Mover]

LOL, brain fart, you're right, I just was typing away and wasn't thinking!

[kats_corner]

Heh.

Easy enough to do.
I seem to be getting too many bouts of encephalo-flatulance myself these days....

[SeikoT123]

Wow - all great information! More than expected.

Thank you everyone! Looking forward to jumping in.

[kats_corner]

Wow - all great information! More than expected.

Thank you everyone! Looking forward to jumping in.

I think there are 2 great truths about audio engineers:

We love to discuss and debate (in a friendly manner of course) engineer to engineer;

And we REALLY love to offer insight, pointers, tips, etc to anyone truly interested in getting into audio. So, welcome aboard!

Just my own $0.02 on the Craig Anderton books: though I've not read his books at this point in time, I have read MANY articles from him over the years. He has a way of presenting facts and explanations that are accurate, to the point, and inviting and engaging to engineers at all levels and experiences.

In fact, I recently picked up a Samson Graphite-49 controller, and had a dickens of a time getting it to talk to DP for a while. Found Anderton's tutorial article online about it, and learned from him that all of the documentation for the G49 left out a key piece of info (it's a MACKIE protocol controller!). He gave that info, along with the proper port settings between the G49 and DP, and I had them talking perfectly in minutes. The man *does* know his stuff, and he presents it very well for the rest of us.