Logic is chock full of great features and workflow enhancements! So much so, that it’s easy to overlook the truly essential bits.
Very often I get to peek into the Projects of both clients and readers. These folks are writing fantastic music and commit to honing their audio skills.
So when I take a look at their workflow, a little piece of me dies inside when I see certain details overlooked.
(Kinda like when I’m forced to watch Curb Your Enthusiasm. Watching Larry David embarrass himself over and over makes me want to crawl into a hole!!)
Audio production is all in the finer details. And details are the easiest things to overlook.
These flubs are so common though, that I just had to create a video this week to help!
So today’s video uncovers the 5 biggest mistakes I’m seeing across Logic user Projects. It’s a great checklist to make sure you’re making the most out of your Logic experience:
- Not knowing that the Pan knob is different between Mono and Stereo tracks.
- Not using Fades on Audio Regions.
- Setting Recording Levels too hot.
- Not using Bounce in Place or Freeze to conserve CPU.
- Not using Sends, Busses, & Auxes for Reverbs and Delays.
Stereo Pan–the only way to truly pan a stereo track!
The Fade Tool–sometimes its even better than using automation.
Region based audio gain adjustment in concert with Flex Pitch gain adjustment is also one of the easiest ways to set consistent vocal levels without automation. This way everything hits your compressor evenly, and every word is heard.
I usually dont even think about track automation until Im ready to start a final mix. Until then its just fader levels set and go.
Great analogy for Send, Bus and Aux. I use a similar one where I say this Track is getting on a Bus and Im Send-ing it to visit Reverb.
Just a thought, some users might want to know the difference between using a Send in Pre or Post Fader, and when to use one or the other.
Another helpful tip might be to always keep your system monitoring in Pre-Fader Metering mode, so you can always see how much input is really coming into the track.
Good stuff Jimmy, thanks.
Thanks for the ideas Jimmy! And that analogy for sends/busses/auxes is amazing! haha
Really useful info as always, Chris – many thanks. Glad I’ve never sent you an LPX project, for cringe-worthy workflow flubs would surely be found! Gonna start using these tips immediately!
Thank you Charles for checking out the post 🙂
Chris, I notice that in your Track Header options you always seem to have the On/Off track button there as an option, which you seem to use with the Mute button as well.
My question is, is there an advantage CPU wise to turning a particular track On or Off as opposed to just Muting it? I guess what Im really asking is, does turning the track off save more processing power than just muting it, and have you ever noticed any difference?
Hey Jimmy, good question! There’s a slight advantage with the Power button, as it turns off the plugin processing on the track.
But it’s probably a bit overkill, since I do just about EVERYTHING to quiet a track that’s not in use: turn off the instrument on the track (if there is one), bypass all the plugins, mute the track, turn off the track…
All that to say I’ve had tracks continue to play audibly when I thought I had muted them one too many times.