Same with me…

I've been using logic for over a decade and can still learn something from this guy. absolutely amazing

Totally agree, I couldn't of worded this better. Thanks so much!

-12 to -18 dBFS is pretty standard. I’ll mention that when we get to recording with a mic.

It does. About 12 years ago Logic adopted a dual buffer scheme, where its default playback engine settings use a fixed 1024 io buffer for playback (non-live) tracks and the user-specified IO buffer for live tracks that Music Tech Help is describing here. Shortly after Protools vamped their playback engine to do the same thing. What you'll notice is that regardless of your IO buffer choice, your cpu usage when just playing back your session is identical. However when you record, your cpu usage goes up and down based on your io buffer. Logic, and Protools, are smart enough to line everything up so that the two buffers don't cause timing issues. Your performance timing is matched to how you heard it in the headphones. This means the record tracks aren't out of time with the playback. By default Logic hyper threads playback tracks (uses multiple CPU cores) for individual voices. You can set it to do this with live tracks. It amazes me how many otherwise really knowledgeable people with youtube channels don't really know how cpu is handled now. The test to do is to record let's say 32 audio tracks at 128 io buffer. Take a screenshot of Logic's CPU window. If you don't see this on the control panel at the top, right-click on the time or beats indicator at the top of the arrange window and select customize. Select Custom under LCD, and make sure "load meters (Cpu/HD)' is checked. Then click on the down arrow to the right of the CPU meter on the LCD (top session time indicator)t shows a vertical column for each CPU thread. This is what you take a screenshot of when recording. Record 32 tracks at an io buffer of 128, then 25, then at 512. You'll notice significant differences in CPU usage. Yet when you take the tracks out of record and just playback at the different IO buffers, you won't see a difference in CPU usage. This is impossible unless the playback buffer is fixed. This is one of the reasons why logic can be incredibly CPU efficient.

@@jessestuart5756 Thanks! This is great information.

If you are using direct monitoring mode on the Apollo, you can pretty much just leave the DAW buffer size alone. Just set it to a higher setting and leave it there, and monitor your recordings through the Apollo. The buffer size has no effect on the recording itself, just how the signal is processed and the amount of time it takes loop back the signal to headphones. The only downside is any effects you want during recording, will not be audible. So if you're running reverb or compression on your track while recording, you won't hear these effects during the recording.

Most interfaces with more than 8 channels will cost big bucks. However, there are several reasonable, affordable options with 8 channels. The Focusrite 18i20 is one example. New they go for around $500 USD. Funny you ask, because I'm actually selling a gently used one for $350 if you are interested, and live in the US?

Thanks for the input. I may consider that offer…

A few things to check: (1) Right-click or control-click on the track header, a menu will pop up. Go down to "track header components > input monitoring". I'm assuming that's what you were already talking about, but I figured I would mention it first. (2) Input monitoring only works for audio tracks, so if you have some other type of track pulled up like a software instrument track, or external MIDI track, the "record enable" function essentially does the same thing for MIDI. (3) Make sure your "advanced/complete features" are enabled. I cover this in part #01, the previous video.

@@MusicTechHelpGuy I did all what you've mentioned, including the part #1 but it still won't show the button...reinstalling logic maybe?

@@alex_bux Yeah, sounds like a glitched install to me. You can re-install, or first try trashing your Logic preferences ("settings" in MacOS Ventura). The bottom 2 solutions will help you out with this. Reset Logic Pro Settings and Trash the PLIST file.

@@MusicTechHelpGuy got it back by reseting Logic Pro settings..Thank you very much for your advices...;)

If you're getting output, the interface is definitely connecting with Logic. What kind of microphone is it? A couple things to check, and apologies if these seem obvious -- (1) If it's a condenser microphone, make sure that phantom power (48V) is turned on and the gain is pulled up a bit. (2) Make sure that the input you're plugged into is set to microphone input, and not line or instrument input. (3) Make sure that the channel input assignment matches the input on the interface. (4) Double check that the Apollo is being shown as both the input and output device in Logic's audio preferences/settings.

@@MusicTechHelpGuy DO YOU HAVE A EMAIL ADDRESS I COULD SEND YOU PICTURES OF WHAT IM DOING IT STILL NOT COMING THROUGH I HEAR MYSELF IN THE HEADPHONES BUT NOT THROUTH LOGIC

Usually when I record into a larger project and I get latency, it's caused by one or more plugins causing the latency. What I typically do is bypass all effects on the stereo out, lower the buffer to like 128 or 256 (still enough power to run most of your plugins), and check the latency on the recording. If it's still laggy, try checking some for some other high CPU plugins in your mix, OR turn on Low-Latency Mode which will automatically bypass high CPU plugins causing latency. You can get to it by right-clicking or control-clicking on the control bar at the top (anywhere in the light-grey area), Customize the control bar, and show "Low Latency Monitoring Mode". Turn it on, and you'll see some plugins turn orange, showing they are temporarily bypassed.

@@MusicTechHelpGuy Thank you very much.

If you relocate the sound library as I demonstrate in part #01, it moves all of the EXS instruments to the external sound library for you automatically. Logic doesn't support VSTs, it uses AU Components, but there's no reason for AU Component plugins to be moved to an external drive. The .component files are not large files, and that might make them not load up correctly.

Thanks for catching that. IDK how I managed that. But it's fixed now. Thanks.

Sure! Without an audio interface, you just won't be able to record with a microphone or use studio monitors. So if you're just working with MIDI and headphones, you'll be fine.

Whenever a new apple os drops, it is highly recommended not to update to it until all the plug-in and hardware manufacturers have had to time to update their products to be compatible with it. You should refer to the audio interface manufacturers website to determine their specific recommendations and whether or not you should update to the latest apple os.

According to the Apogee website, you need to update the firmware to ver. 3.5.2 or higher to run on Ventura and Apple Silicon. Here's a link to their compatibility page: apogeedigital.com/home-feature-news/apogee-products-and-macos-ventura-compatibility

Yes, the latency will affect software instruments, particularly if you have some plugins loaded that use a lot of CPU power, or cause a lot of latency. I typically lower the buffer a bit and bypass any effects on my stereo out when recording with MIDI.

Thanks!

It's been my understanding that you can simply open any GarageBand file directly in Logic. Just right-click on the GarageBand project, and select "open with" and then select Logic. Or just open Logic first, and open the GB project. It's been a few years since I've done this, but I don't see any reason why you would get clicks and pops. Sometimes these are just sync/jitter errors. A lot of the time, they can be corrected by changing the buffer size, hit apply, then change back to the buffer setting you prefer.

@@MusicTechHelpGuy thank you soo much that makes perfect sense!!!!!!!

For many years I use Logic with no interfaces, only the one Logic offers.

Yes. That was for their introductory period. The ads in future videos have been updated for this.