Logic pro x latency on playback free. Manage Logic Pro input monitoring latency
So a setup that previously worked fine, and now without any changes doesn't, is completely normal? How do you see the plugins latency while hovering over? Is it when placing the pointer over the plugin name in the channel strip? Where does the latency show? I cannot see it. However, I disabled every single plugin and send from output down to each channel strip, and the latency is still unchanged, so I still believe there is some setting that has changed during a recent update.
Any more troubleshooting suggestions? You need to delete them as I stated above. I agree that sudden latency problem cropping up are not acceptable, especially when they occur in a paid program.
I have the same problem after the last update of Garageband, and it apparently has manifested itself in the parent Logic Pro X. Previous versions of Garageband worked with several add-ons, couple of upgrades caused add-ons to stop working. Then an upgrade fixed the problem with the add-ons. Then another upgrade broke those, and now I can't do overdubs because of latency issues. OSX Same problem here. Latency issues all over after update to Mojave.
I'm on a Mac Pro 5,1 with Saffire Pro System info below, recent updates include Logic 4. The first tracks were recorded direct through a Neve RNDI direct box, one output going to an Apollo 8p Unison amp plugin recorded , the other low Z output going to an Apollo preamp input, direct input only, no UAD plugins used.
Because the delay is visible in all Logic displays I assume this means that the delay is not happening outside of Logic Changing Recording Delay to anything other than zero produces playback glitching.
The audio file is delayed by approximately. I'm experiencing this latency issue also, just in the last week or so. Recently updated to Logic Pro X 4. I'm running macOS If you don't have any plugins on any channels anywhere, then there is no point to concern yourself about Low Latency mode, that is totally irrelevant.
I recorded 3 audio tracks and one MIDI track, then added an Ultrabeat click track for a loud and clear click track. What exactly were you recording onto the audio tracks? You said you recorded an ultra beat track after the fact. When it plays back does the ultra beat track sound like its matching the built in metronome? I don't know what this is. Please explain. You said above, no plugins, but actually you do have at least this one plugin?
Where is that plugin in your template? Please explain exactly the audio routing you're using bringing the audio into LogicPro and through the logicPro mixer. Ok nothing on the master bus.
I would leave it at zero unless you know what you're doing. You need to do a loopback latency test to properly set that value and should mostly be a set it and forget it value pertaining to your audio device's unreported latency, if any. I doubt its relevant here, but might be. You'd have to do a loopback test and measure the known latency of your audio device in order to find out. I do not know why it would cause audio glitches. I'm suspicious of your sound card.
Did you try tests using built in audio instead of the Apollo? I know its a good quality device, but eliminate it to narrow down the problem. Thanks for your quick reply, I'll attempt to clarify.
I'm new to posting so I don't know how to comment directly in your post as you helpfully did in mine, so I hope the following clarifies:. It was never switched on during testing. Only the Click "Klopfgeist" track was used during initial audio recording tests. The Ultrabeat click was created not "recorded" in the Ultrabeat sequencer a Software Instrument after initial testing. I did this to produce a more audible click track. I programmed 4 clave hits in one Ultrabeat sequencer bar which repeats as long as the project is running playback or recording.
I also created the Ultrabeat clave click to double-check the Click track. I mentioned the Neve direct box because of it's signal splitting architecture, agreed, probably not relevant or unusual.
Signal flow is as follows:. The direct guitar signal no plugins used in Apollo Console or Logic is recorded on another track. No plugins, UAD or otherwise, are inserted anywhere in Logic. The Ultrabeat instance was introduced later in testing and produced no changes in the results audio and MIDI recorded data is delayed.
I left Recording Delay set to 0 for all testing, that's where I'll leave it unless specifically directed otherwise. I haven't yet determined if tempo affects the amount of delay, more testing today. The second audio source direct guitar, no "amp" Unison processing goes from the DI box to the Apollo input preamp, then directly to Logic.
This is the routing that I've used for years, provided by the UAD manuals. The UAD Console software is designed to reduce latency by monitoring through their Console app required by the Apollo interface. Unfortunately, I can't determine exactly when this issue appeared, my best guess is in the last month.
I'm hoping the "empty project" test isolates the delay symptoms from influence by my other software. Thanks for your response, Dewdman42, and reminding me of my former manual-authoring job responsibility to be clear! What happens when you remove that from the picture completely? How does it get to logic? If you run audio through another application, such as this console software you speak of, who knows what is happening.
Whether or not its reporting the correct latency to Logic is another matter. Quite possibly not. I would suggest you try to setup a loopback test using your guitar UAD plugin in the mix to see what it says.. I don't have links handy to send you right now, I will try to find them later, but there is a free 3rd party loopback tester out there you can use to measure exact loopback latency, and you can compare that value to what Logic shows in preferences..
If they don't match then you need to set the record offset slider. There are posts out there about this procedure, google around. It doesn't matter if its in the path. When you are recording its playing back a metronome to you which by the way has some latency due to the audio buffer , logic knows all of that and attempts to adjust the record time of incoming midi or audio events so that theoretically they will end up registered in the region at the time you MEANT for them to land Logic can keep track of what the audio card is reporting for latency and can be aware of plugins, but if they don't report correctly, then the record offset can be wrong, which is what the offset slider is for.
So in theory if your UAD console setup is adding some kind of latency and not reporting it right, you can adjust that slider and the stuff will be recorded at the correct place. I do not know why you are getting audio glitches. There is another thread and it does seem that suddenly recently people are complaining about latency problems. I have not personally been experiencing that. I am on sierra with LPX But I haven't been that active the last couple weeks recording music either.
Its possible some OS X update broke something in core audio or something strange like that, but we need to hear more information from people in order to determine that and report a bug to apple. However, if you were using all the same hardware and software up until very recently and then suddenly its giving you problems the same way you've been using it many times before..
Don't know what else to say We can't fix the Logic bugs here, we can only advise about the many common latency problems that users have often from not using Logic right. Beyond that, try sending a bug report to apple, but they will need more information from you about what you changed or what exactly you're trying to do in order to zero in on it. Because of the sudden excitement on the other thread about latency, I am suspicious also that Apple may have broken something with a recent OS X update, but I personally haven't experienced that yet.
When you begin to regularly use your system after a few months of downtime you tend to forget what you used to know. I had a problem late last year getting an app I used and still use regularly for apartment studio headphone work to load during startup: Sonarworks Systemwide standalone version of Reference 4.
After one of their "updates" it refused to recognize audio after booting. I still had to load the program manually from the Apple menu bar after booting. Seemed to work, now the headphone correction EQ was active inside and outside Logic.
I had not realized that I had done very little actual recording, just using self-running synth patches and pencil-MIDI parts to create several pieces. I know several other Logic users rely on the Sonarworks software so I thought this issue was worth mentioning on a Logic forum.
The trick is to remember to CHANGE the Output Device setting set to Systemwide for mixing, your audio interface for recording depending on whether you're recording or mixing. It probably isn't an issue if you only use the Reference 4 plugin in Logic, but heed the following warning: Systemwide is a stand-alone app for audio output only, which is handy because if you leave an instance of the Reference 4 plugin active on your mix bus during a bounce, the EQ is applied to the bounced audio file.
Not good. Sorry for burning up the forum time on my specific problem, I appreciate and understand your description of how Logic works. I hope I won't need to use that knowledge to troubleshoot an actual Logic bug anytime soon, too much work to do So just to comment a little further on this. This is a case where Sonarworks was adding extra latency that LogicPro was not aware about.
So basically with that in play, you were hearing everything later then LogicPro thought you were hearing it. If you played against a late-sound click, then your recorded audio and midi parts would go into Logic late also Now how to work around that, if you still want to use sonar works that way, is you have to do a loopback latency test with sonar works activated. Then when you know the additional latency, you can adjust the record offset delay to the correct value and then LogicPro will record everything exactly where its supposed to, even with Sonarworks activated.
But the latency will still suck if you try to monitor your voice while recording vocals, or try to record a software instrument.. In that case turn off sonar works while you need to monitor through the LPX mixer.
I also want to say that I have also started to suddenly have an odd latency issue. When I start a new project with a simple instrument plugin that has its own built in keyboard on the plugin hi.
I try to mouse on that keyboard and there is extreme latency, over a second. I think wtf. So then I play a few notes on a real midi keyboard, or using LPX virtual keyboard. The first strike or two are delayed and glitchy and then LPX recalibrates itself and starts reacting without latency, including if I mouse on the plugin gui keyboard.
Ok that is strange stuff that was never happening before. I have been on Sierra and LPX Might have been a recent Apple update that makes sense timewise. But I am wondering if other people complaining about latency all of a sudden could try to hit a few notes on a midi keyboard to see if LPX recalibrates itself in some way. I really think there is some bug they have introduced somehow through the security update, I'm getting weird behavior also in the past couple weeks.
I plan to do an absolutely clean install of Mojave on a test partition too in order to see if I still get the problem. I really wanted to do a clean install when I got this new computer, but unfortunately I couldn't take the risk of loosing stuff from way back. 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. However, smaller buffer sizes require more processing power, which can cause system overload alerts. Roundtrip latency is the total amount of input monitoring latency you'll experience from audio input to audio output. Certain plug-ins can contribute to input monitoring latency, particularly dynamics plug-ins with look-ahead functions. If you're using these kinds of plug-ins in a project, you can minimise the latency they produce while recording using Low Latency Mode.
Low Latency Mode bypasses plug-ins as needed, so the amount of latency doesn't exceed the Limit setting in the Plug-in Latency section of the General Audio preferences of Logic Pro. Low latency mode is especially useful when you want to record a software instrument in a project that includes latency-inducing plug-ins.
Information about products not manufactured by Apple, or independent websites not controlled or tested by Apple, is provided without recommendation or endorsement.
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.
-
Very annoying. Posted April 2,
