Logic pro x latency recording free
So I’ve heard so much about latency, but as someone who works almost entirely ITB, have not experienced much yet. I have a couple of synths but have not actually used them much in my actual productions to this point.
I decided to make an entire track using my hardware only in an effort to familiarize myself with the workflow as well as the equipments. When recording say an 8 bar segment of MIDI triggered analog bass, I noticed immediately the audio file was just a smidge behind. Not a big deal, I just cut the little late start off of the front of the audio file. Is this all that is necessary or can latency wax and wane throughout the recording?
I think it sounds okay but am kinda feeling paranoia that it still may be off a bit. This is hard for someone who is anal about precision and getting all my ducks in a row.
Anything else I need to consider? If this is all it is, would changing the buffer settings really matter if I’m going to have to do this each time anyways. Also, I’m beginning to understand the benefits of sampling. I recorded 32 kick drums in a row and they are kind of all over the place.
For a hat pattern that is fine and even prefferable, but for the kick, I’m thinking I sample the best, and copy the audio on over or put it into my drum sampler Metrum and trigger with MIDI.
What do you guys do? If you care about making the performance sound “human”, then you try to keep as much of the original recording take as possible, without too much editing or fixing. That means the latency has to be low so that when you play you hear the sound instantly, which allows you to go for good performances. But certain interfaces cannot go to the lowest buffer of 32 because you start hearing crackles and pops.
RME Digiface.. Currently I use the External Instrument plug-in. My interface Scarlett 2i4 has a direct monitor knob that goes from input to playback what I hear through Logic. OK, that just confused me, so I had to read page 11 of the 2i4 user guide.
A blend control is a new one on me. Your inputs are sent straight back out to your monitors. You can’t hear Logic’s audio. So I assume you have the Direct Monitor knob set fully clockwise, for Playback? You can check this by inserting an FX plugin on your External Instrument’s channel strip. It’s important to establish exactly how you’re monitoring your synth.
Software monitoring will involve considerably higher monitoring latency than direct monitoring. Also, are we talking about monitoring the playback of a pre-recorded MIDI region? Or live MIDI keyboard playing? Yes, unless I’m just jamming, or working offline designing patches for my soundtower editor, I have it in playback mode while working in Logic.
Unless it’s just a little hat pattern or something I’m not really a good enough player to record live, though I’m getting a lot better. I have way more music knowledge between my ears than I can articulate with my hands. I practice regularly though. I’m a crap keyboard player!
It doesn’t matter. Are your drums in the box and therefore sample accurate and jitter free? This means you’re software monitoring your external synth. At least, let’s stick to this scenario for now. How are you recording the synth? Using a separate audio track that is record enabled? Or are you doing a realtime bounce wet with FX? So far I’m bouncing real time to dry audio and processing later.
IDK why, I usually have some processing on there, but I guess it gives me more options with a dry audio file. Its a mono but does have a stereo signal path. Oh yeah, normally I use high quality drum samples triggered via AU Metrum. But this whole latency thing became terribly obvious to me when creating a track made entirely with my synth.
While sequencing and recording my drum sounds made with the MEK, it became obvious the time was off. I don’t realtime bounce, I just record to a record enabled audio track. So I’ll have to set up a little test to see how.
Bear with me, there may be some time between posts but I will get there in the end. I’ll try to break this down into smaller posts to avoid information overload.
Also, apologies if you already know most of this:. Before we deal with MIDI we need to establish that your audio latency is being correctly reported by your interface’s driver. We need to do this in order to determine your Roundtrip Latency, which is displayed by Logic in. The image above shows that Logic thinks my roundtrip latency is 7. It isn’t. My audio interface’s driver is. My Recording Delay is therefore set to samples so that Logic knows my true roundtrip latency.
Annoyingly, Logic doesn’t show this adjusted figure. My actual roundtrip latency is approximately The driver’s latency will usually stay the same, unless you halve or double the sample rate but this depends on your driver. We need to know your roundtrip latency. In order to do this you need to check that your Recording Delay is set correctly.
If your 2i4’s driver is reporting it’s latency correctly, your recording delay can probably be left at zero. No point explaining this if you’ve already done it. I’d be very surprised if the 2i4’s driver is under-reporting by samples.
I was expecting 0, or something close to that. Looks like you’ll need to test your Recording Delay properly. I don’t think the Recording Delay is ever set automatically.
Unless something has changed in Logic X? What sample rate are you running at? You can post now and register later. If you have an account, sign in now to post with your account. Paste as plain text instead. Only 75 emoji are allowed. Display as a link instead. Clear editor. Upload or insert images from URL.
Click here! Latency When New to Recording. Share More sharing options Followers 0. Reply to this topic Start new topic. Recommended Posts. Posted January 23, Thanks, Kevin. Link to comment Share on other sites More sharing options Hi Kevin, If you care about making the performance sound “human”, then you try to keep as much of the original recording take as possible, without too much editing or fixing.
RedBaron Posted January 23, How are you monitoring your synths? Software monitoring via External Instrument plugin? Logic X Here’s my understanding: 1 Fully clockwise Playback is equivalent to software monitoring only. Posted January 24, RedBaron Posted January 25, Posted January 25, RedBaron Posted January 26,
Apple makes no representations regarding third-party website accuracy or reliability. Contact the vendor for additional information.
Set the sample rate of your project Set the sample rate for your project when you first create it. Click Devices. Turn Low Latency Mode on to manage plug-in latency Certain plug-ins can contribute to input monitoring latency, particularly dynamics plug-ins with look-ahead functions. Published Date: December 04, Use the techniques in this article to avoid system overloads.
Each CPU core in your Mac has its own meter. On Mac computers with processors that support Hyper-Threading, two meters are shown for each core. Watch the meters as the project plays back, noting when the meters are full. When a meter is full, the CPU or the disk has reached the limit of its processing capability. System overload alerts can appear when any of these meters peak.
You can use this information to make adjustments to your project or your system configuration. If you’re recording audio and not software instruments, you can monitor your audio directly from the source. If your project doesn’t include automation, or the automation doesn’t need to be sample accurate, you can reduce the CPU load by turning off Sample Accurate Automation.
If your project does include automation, choose the option that includes only the parameters you’re automating. Projects with higher sample rates create larger audio files, which can increase the load on the CPU and disk. Plug-ins also require more CPU power to process audio files at higher sample rates. Apple assumes no responsibility with regard to the selection, performance or use of third-party websites or products. Apple makes no representations regarding third-party website accuracy or reliability.
Contact the vendor for additional information. Set the sample rate of your project Set the sample rate for your project when you first create it. Click Devices. Turn Low Latency Mode on to manage plug-in latency Certain plug-ins can contribute to input monitoring latency, particularly dynamics plug-ins with look-ahead functions. This processing can take the form of input latency, output latency, or both.
However, monitoring an audio recording may have both an input and an output latency because the signal must be input into Logic Pro before it can be processed. Input latency if any is added to the output latency, resulting in an overall monitoring latency. Each further process—such as the use of insert effects, for example—may add to the overall monitoring latency.
However, Logic Pro can compensate for these latencies using plug-in latency compensation to ensure that all your audio output is perfectly synchronized.
You can turn plug-in latency compensation on or off.