Jump to content

Latency question


A_Pryce

Recommended Posts

Hello,

I am not experiencing this in any other DAW so maybe I do something wrong in Logic.

When there is a latency inducing plugin on an audio track(let's say vocal with ozone or similar latency causing plugins) I get latency when playing an instrument plugin with my keyboard. Now I understand that is normal if the plugins are on the instrument itself or master bus but why an unrelated audio tracks plugins affect the live midi input?

I do not get this issue with Cubase for example.

 

Thank You

Link to comment
Share on other sites

Hi Dewdman42,

Thank you for the reply.

Yes that is what confuses me. When I remove the plugin from the vocal track midi response is normal again.

I have nothing on the master track and do not have any aux tracks. I checked the Global and Project preferences but could not find anything that helps.

 

Edit: I have latest Monterey, Logic 10.7.4 and Mac Studio running in Native mode.

All 3rd party plugins are also Native Apple Silicon.

Edited by A_Pryce
System Info
Link to comment
Share on other sites

OK new update.

Further looking to the project, the latency inducing plugin is on the track stack of vocal track. So I guess that is considered as an aux track. If I put the plugin on the actual audio track, there is no latency. Sorry for the confusion I was not in front of the project.

But, I just checked the same setup with Cubase (All vocals routed to a group track which is an aux track in Cubase and plugin is inserted there  does not cause any live midi playing latency issues like Logic. I also tried it on Ableton, no problem there either.

So I guess Logic is different how it handles the latency? Yet I do not understand why it would create latency since my instrument track is going directly to the master track without any plugins or routings.

Thank You.

 

Link to comment
Share on other sites

We would have to look at your full signal routing to give you a proper diagnostic (screenshot of your entire Mixer). 

All DAWs have different solutions for handling plug-in delay compensation and latency, so it's not surprising that you would get different results with the same routing in different DAWs. In Logic Pro, you can choose Record > Low Latency Mode to temporarily bypass the plug-ins that create latency in your R-enabled track's signal chain. 

Link to comment
Share on other sites

3 hours ago, A_Pryce said:

Further looking to the project, the latency inducing plugin is on the track stack of vocal track. So I guess that is considered as an aux track. If I put the plugin on the actual audio track, there is no latency. Sorry for the confusion I was not in front of the project.

 

As @Dewdman42 points out, any auxes with latent plugins makes Logic behave like this... ASFAIK this has been the behavior at least since LPX 10.0.7 (?) 

1 hour ago, David Nahmani said:

Here's the interesting part. If you first create an Aux and insert the Adaptive Limiter plug-ins, then set its input to a bus, then set the output of the audio track to that bus, then select the audio track and create the summing stack, you end up with the exact same configuration, but no latency. 

Can't reproduce here on 10.5.1...

Link to comment
Share on other sites

Coming back after I was away...a lot happened on this thread and I'm a little confused about what exactly the scenario is does or doesn't create latency?  But I will make the following points just after a brief scan of the thread:

  1. LogicPro recalibrates things like PDC at the time you hit PLAY, it does not do it dynamically while LogicPro is playing...and it seems from the above dialog that it doesn't do it while stopped either?  Its an interesting point that I can see led to some confusion.  Seems weird to me that it didn't recalibrate while stopped and that could be a bug where its not recalibrating PDC until PLAY under some condition, but other actions while stopped are recalibrating.  And really it should always recalibrated while stopped...but anyway, maybe we can figure out what the situation is where its no recalibrating?  it may also matter which track is selected and when you actually select it, which might affect PDC.
     
  2. Its normal and expected behavior for Logic to add delay to all tracks in the project when any latent plugin is placed on an AUX track.  This goes back many many versions, probably all the way back to whenever Logic had plugin delay compensation of any kind.   Its by design that it happens.  

    The way LogicPro generally handles PDC is that midi and audio tracks during playback are able to have their source regions fed to the mixer ahead of time by the PDC amount, so that any latency that is on those instrument or audio mixer channels will be compensated by playing the regions early.  But AUX channels typically don't have source regions on the arrange page.  So nothing can be fed to them early.  Therefore LogicPro's standard approach for handling PDC on AUX channels is to delay ALL OTHER CHANNELS in the mixer to make up for the delay that is in that AUX channel.  

    That is a generalized description of how LogicPro handles PDC.  When it can feed the source midi or audio early, it will.  When it can't, then everything else has to be made later.
     
  3. Now when AUX's are used as a direct bus from an audio track, and the aux is not being used by anything else; you would think that AUX is basically in the signal path of the audio track and LogicPro ought to be able to figure out that it doesn't need to make everything else late since its source region was early.  Or there can be other weird routings that its beyond me how LogicPro could possibly figure out how to delay or not delay tracks due to complicated routing.  But what I can say is simply that LogicPro does follow the rule that audio and instruments tracks are fed from a region, which can be queued early to avoid hearing latency, and AUX channels are more like a "live" channel that can't be fed early, so if its going to be late, then all the others have to be made later also in order to line up.
     
  4. Cubase or other DAW's may handle latency in different exact ways then LogicPro of which I don't know enough to make any exact statements.

 

  • Like 2
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...