Some things should just work, amirite?
Let’s say you’re about to record some vocals. You’ve got the headphones on. The mic’s powered up, and you’re ready to roll.
You hit record, and the track starts to play. The first chord of the verse starts up, you take a breath and…
Nothing. Not a single word you sing comes through the headphones.
What the heck? You play back the track. Clearly you recorded something. You can hear it!
But why can’t you hear it while you’re singing?
So you take a trip down the Google Hole. 2 hours later, you have the dang mic coming through the headphones.
But now there’s a new problem.
Instead of hearing your singing while you’re singing, it’s delayed in your headphones. Or even worse, you’re hearing double.
w.t.f.
At this point you’re convinced that either:
- Your interface is busted, or
- Logic is a crap DAW.
Either way, your urge to kill is rising:
Recording Without the Hassle
First of all β you’re right. Things should just work the way you expect them to. Especially when it comes to recording.
The good news is that everything you need is literally a click away.
Logic has several Modes for a stress-free recording session. And they’re sooo close by, it’s easy to miss them:
Those buttons aren’t there just to look good. They’re huge to your recording life. Get to know these babies, cause they can save you a lot of headaches.
Software Monitoring: The Ghost in the Machine
Hearing you mic or instrument in Logic can feel surprisingly complicated.
But it’s really not a big deal. The hard part is knowing what the heck it is you’re looking for.
This obvious but “tough” thing you’re trying to do is called Software Monitoring. You’re trying to monitor your instrument through the software.
Or to put another way:
You’re trying to listen to your instrument through Logic.
Once you know what you’re after, it’s easy to get things working.
All the Logic Modes hang out in the upper right hand corner of the Arrange Window. And Software Monitoring looks like a speaker:
If you don’t see the Software Monitoring button, you’ll need to dig it up.
Do this by Control-Clicking or Right-Clicking in the top part of the Arrange page, and select Customize Control Bar and Display…:
A window will now open, and all the way to the right is the Modes and Functions:
When you select Software Monitoring, the button will appear in the Control Bar.
With Software Monitoring enabled, any track that you Record-enable will be audible through your headphones and monitors.
To Record-enable your tracks, Click on the red R button in the Track Header.
Input Monitoring
Now with Software Monitoring you should be all set to hear your tracks through Logic.
But let’s say you want to hear your microphone or instrument, but don’t necessarily want to record. In that case you can enable Input Monitoring for your selected tracks.
It’s a subtle difference, but one worth noting when it comes to monitoring your tracks through Logic:
- Enable Software Monitoring to turn on the whole system so you can hear your microphone or instrument through Logic and your plugins
- Record-Enable any tracks you want to hear and intend to record to
- Enable Input Monitoring for any tracks you just want to hear, but not record with
You can find Input Monitoring in the Track Header as an orange button with the letter “I”:
If you can’t find it, you’ll need to Configure the Track Header. To do that, use Key Command Option-T to open the Track Header menu:
At the bottom of the Buttons list is Input Monitoring. Click the box next to it and you should now have a shiny new orange button in the Track Header!
Pretty easy, right?
- Flip Software Monitoring on for the whole project, and
- Turn Input Monitoring on for the tracks you want to hear.
Managing Latency
Ah, but if only it were that easy.
Cause depending on your recording interface and Mac, there’s a tango you’ll have to dance.
Monitoring through Logic introduces a phenomenon called Latency. Latency is an audible delay of your mic signal.
For example: You try singing into the mic, and your voice comes through the headphones milliseconds after.
It’s pretty hard to get into the groove if your vocals sound off the whole time!
So how do you deal with latency?
Well. It depends.
The best approach always starts with adjusting Logic’s Buffer Size.
I’ve gone over the Buffer many times on the site, so I won’t belabor the point. But if you’re not familiar with the Buffer, I suggest reading this post.
Head up to the main menu bar at the top and dig into:
Logic Pro X > Preferences > Audio
Within the Audio Preferences menu is a field labeled the I/O Buffer Size. And within that menu are 6 values measured in samples:
- 32 samples
- 64 samples
- 128 samples
- 256 samples
- 512 samples
- 1024 samples
The rule here is the smaller the number, the less Latency you’ll have to deal with. But the smaller the number, the more you risk the chance of crippling your Mac with System Overloads.
So you’ll have to perform a balancing act:
- How small a buffer is small enough to eliminate the latency problem? And,
- How small is too small for your Mac to handle?
For my system, I record at 128 samples without any noticeable latency.
Which is awesome, cause then you can record with plugins π
Recording With Plugins & Low Latency Mode
What’s so cool about Software Monitoring is you can take advantage of the awesome plugins and routing in Logic.
If you need some reverb or delay to feel comfortable performing β throw it on your track! Let that reverb wash your self-doubt away.
Having a hard time hearing yourself in the mix? Throw on the Compressor to level out and bring out your performance.
Get as Plugin or Bus crazy as you like!
So you go to town. You’re throwing in plugins left and right. Once you’ve nailed the sound you’re after, you get ready and hit the record button β
But plot twist! There’s that Latency again!
It turns out Plugins and Busses can add latency too. And since you’ve gone buck wild on your recording session, it can be a real pain to track down what’s screwing things up.
To save you precious minutes of your life, Logic has a Low Latency Mode:
With the single click of a button, Low Latency Mode turns off all Latency-inducing plugins and routing:
Any Plugins that causing latency in your session are muted. Logic greys out the plugin buttons and changes the labels to orange to let you know they’re muted because of the latency they introduce.
In the case of busses Logic doesn’t mute busses. But instead optimizes their timing so you don’t experience latency on your Reverb and Delay Channels.
Thanks to Low Latency Mode all is well, and you can enjoy latency-free recording within Logic.
Once you’re done tracking, just turn off Low Latency Mode. And now all your Plugins and routing are back in action.
Enter: Your Recording Interface
The other factor in the latency equation is your recording interface.
If you’ve followed everything above and you don’t hear any noticeable delay β sweet! Your job is done and life is beautiful.
But if you’ve followed everything above and you’re still having problems, then you’ve got a bit more to go.
Direct Monitoring
For some of us no matter what we do with the Buffer, Low Latency Mode, or anything else β Latency is just a fact.
Oftentimes the culprit is a Project that has become far too big to manage effectively. By “too big” I mean either:
- tons of tracks
- tons of software instruments
- tons of plugins and routing
(And usually it’s all of the above.)
Another reason could be the combination of your interface and Mac. A slower connection like USB 1.0 or an older Mac just isn’t as fast as a new Mac or Thunderbolt connectivity.
Whatever the case, interface manufacturers needed a way to get around the latency problem.
The solution was to provide you with a separate Mix Software for Direct Monitoring.
Direct Monitoring is the opposite of Logic’s Software Monitoring. Instead of listening to your track through Logic, you hear it directly from your interface.
For example, here’s MOTU’s CueMix Software:
With CueMix you can dial in the direct signal from your interface and skip Logic entirely.
Direct Monitoring has its advantages. Namely β you don’t have to deal with Latency! The bummer is that you don’t get to take advantage of recording with Logic’s plugins.
So if your vocalist wants to sing with reverb or compression, you’re out of luck.
But it’s always better to have something instead of nothing. So if you haven’t downloaded your interface’s mix software β do it!
Just make sure to turn off Software Monitoring if you do use Direct Monitoring. Or you’ll hear both the Direct Monitoring signal and the Software Monitoring signal at the same time.
The result will sound like your vocals are going through a phaser pedal.
Trippy, but not helpful.
Conclusion
Monitoring may seem complicated, but it doesn’t have to be. Between Software and Input Monitoring, it’s really quite easy.
Things get a little more complicated when you have to think about Latency. but thankfully Logic gives you several ways to manage Latency:
- I/O Buffer Size
- Low Latency mode
Based on your Mac and interface, you may need to find a different way to manage your monitoring latency.
That’s why you should always download your interface’s mix software!
I would love to read your comments or ideas about the Recording Delay settings.
Thank you so much for boiling down the complexity to the essentials! I have bought so many books and watched so many videos trying to figure it out – even though I don’t need 99% of the features it has seemed like I need to understand them all just to use the 1% I need!
Now that I get the gist of Software Monitoring – is there any chance you could get the ‘Auto Input Monitoring’ monkey off my back?
Hey Sacha, thanks for the suggestion! I’ll definitely add it to my list of topics to cover π Can you explain what’s the issue for you related to Auto Input Monitoring?
Great article Chris. Super-useful, esp. for LPX beginners like me. Many thanks and keep up the good work.
Thanks so much Charles! Happy to help π
Hi,
With Apogee Element & Ensemble Thunderbolt interfaces, there’s an almost magical “Direct” button at the top of the Logic channel strip that somewhat magically eliminates latency. In fact, it sets up direct monitoring through that channel strip without having to open the Apogee app or change Logic prefs.
Even better, you can use Apogee FX Rack plugins with the Direct button for EQ & Compression. Finally, you can set up an Aux send for some of that awesome ChromaVerb.
Yup, I’m from Apogee. Very few know about the Direct button or Apogee FX Rack plugins, but this really is a great solution to the monitoring dilemmas you describe.
Roger @ Apogee
Welcome, and thanks for your comment Roger! Appreciate the full disclosure as well.
Iβve examined the Apogee interfaces and definitely have taken note of the direct monitoring available to Logic users. Very handy for sure.
This is one of the best Why Logic Pro Rules articles. Today, out of the blue, I started losing hours trying to track down latency issues. Thank you.
HI first I wanted to say I really enjoy your tutorials. My issue is a little different. I’m using an Apollo x8P and when recording then playing back a vocal for example I’m hearing the prerecorded vocal extremely louder than the vocal I’m currently tracking. have you experienced this and how do I fix it?
This is the exact problem I’m trying to resolve as well. I kind of remember some record vs playback volume settings, but I can’t remember where or how…
This all mostly makes sense except for this: I have not needed software or input monitoring before, and all of a sudden in the middle of a project I need software monitoring. Nothing changed. So at least I can keep recording vocals. But what on earth caused this to be different? Any ideas?
I have a question regarding direct monitoring. When I record audio with direct monitoring on, and, letβs say the total latency in the software is 100ms because of large buffer and many plugins and routing going on, I do not hear that latency because I use direct monitoring. So far all is great. Question is does my recorded audio line up in sync with my project or do I have to compensate that 100ms manually afterwards?
Hey Thematic, thanks for the comment! Logic handles lining everything up, regardless if you use Direct Monitoring or Software Monitoring. I’ve never once needed to compensate the timing of recorded audio in Logic after the fact.
I hope this helps!
Thank you Chris for clearing this up for me. It sure helps! I come from Cubase and still use a Steinberg audio interface. It has DSP on board with amp models, reverbs etc. So this is good news for me, no need for changing buffers and switch off plugins an such. Thank you!
Hi,
I’ve got a reversed question about monitoring:)
I don’t want to hear the (monitor) input sound of an external instrument track during playback. Only the result… otherwise I will hear the audio double. Maybe a stupid question. I will try to explain:
During playback of an external instrument track (Moog subsequent 37, local off mode) I hear the Moog ‘double’. The playback (stereo out) AND the input (mono in). Even when you mute the external Moog track, the stereo out, master Volume, etc. I will still hear the input audio. WTF. Only when I mute the midi. But muting midit means that the Moog track will not be heard during playback…
Mmm…. So I was looking for all kind off causes, maybe an prefade auto input monitoring that keeps on monitoring also in playback mode.
I’m using Logic Pro on a MBP and an Apogee Duet (iOS-MacOS) for audio interface. I really hope you can help me, this is so frustrating. Thnx already! Arthur
OK, this is driving me batty. Very simple setup: Logic Pro being fed by an Apollo 8. The mic is muted in the Apollo 8 Console software, so without Software Monitoring enabled, I hear nothing. The signal is still getting through to the enabled channel in Logic, so I know the signal path is good. Monitoring is done through the Apollo headphone outs.
The problem comes in when I enable Software Monitoring: I hear both the direct and the software-latent audio, no matter what I do. If I set the buffer really low, it’s just a subtle phasing; if I set it higher, it approaches a distracting slapback echo, for reasons that make sense.
When recorded, the audio is clean and clear, so it’s strictly a monitoring issue, but I have no idea how to clear it so that I’m only listening to the software, not the direct. I’ve been looking for solutions, but have found nothing effective. I’m sure it’s a simple thing I’m missing, but missing it I am. Any guidance would be most appreciated! Thanks!