Latency / Delay Compensation doesnt work

Hey,
i got some problems with my Apollo DUO on MacPro (Sierra) and Logic Pro x (Everything up to date and running on latest version).

I send the logic click on an Apollo output and record this again via apollo input channel.
It was an 120 Bpm click and its about 4ms away from the position it should be.

System is running on 32ms (I/O Puffer) and Delay Compensation in Logic is turn on "all".
Where is my problem?

Thanks!!
best wishes from germany!

One thing: your buffer is set to 32 "samples" not ms.

Anyway, delay compensation doesn't do what you're expecting it to; it's not about sending things out to hardware and back in.

What it does, it measure the delay introduced by plugins in your session, finds the channel with the largest delay, then adds delay to all the other tracks so they have the same total delay as the most delayed track. So they all stay in time/phase.

What you've done is measure your output to input latency for a hardware loop. So when you send something out to hardware and back you can compensate for that manually (or automatically if Logic has a feature for that, like Pro Tools does)

Hi, thanks for this fast answer and sorry for my disknowledge
But nevertheless, in my opinion it should be on the same position.
Lets think about this:
Amusician records to a playback-track in logic. When he/she hears the playback and plays ON this track his/her signal becomes recorded not at the same time as the musician hears the track.
I hope you can understand my point. There shouldnt be any delay/latency between hearing and recording, right??
So you can´t play "tight", cause the audio system doesnt record the time position you play on.

Turn off Input Delay Compensation in Console and retest. I believe you're seeing the 100 sample IDC. The converter delay is compensated for by the driver, but not a Console delay.

I think I understand what you're trying to say but it's really not as bad as you're thinking.

Your DAW is aware of the total native system delay (including the delay compensation it's doing for plugins, and the native buffer) and it does offset recorded audio by this much on the timeline so that your audio is placed on the timeline exactly as you played it along with what you were hearing. (even though what you heard was delayed, so you were playing to a delayed track)

What your DAW can't do automatically is compensate for the system delay of your interface's converters, since your DAW doesn't know what that delay is.

You can prove this by putting a bunch of plugins on your click track so that it incurs delay that the system has to compensate for. Send it out and record it back in and you'll find that you get the same 4ms offset as you did this time.

You may be able to manually set Logic to compensate for this (I'm not a logic user) but even if you can't don't worry. 4ms isn't a legitimate time difference between performed audio tracks. The only time when this would come into play is a situation like recording a bass DI and later re-amping that signal and mixing the two together. You'll end up with this 4ms difference (plus any other delay caused by whatever in the chain at the time). So after you record the re-amp you'll want to zoom in and line those two back up if they are going to play together.

Other than that, no overdub is going to have a problem with 4ms. Understand that in multi-mic situations you can't punch in some but not all of the mics without causing this 4ms difference to throw off the phase of the configuration. But that would be something like a drum set anyway, so you'd do the whole thing in a punchin so this isn't really an issue.

One minor note, Justin, the converter delay round trip is less than 1ms and is compensated for by the driver. If it was 12–15 samples I'd say it was converter delay not being compensated for, but for 100+ samples I'm pretty sure it's IDC or a plugin in Console adding the uncompensated delay.

The IDC delay is 100 samples (regardless of whether plugins are in use). 3.5ms approximately. That appears to be what the OP is experiencing, perhaps in combination with the converter delay.

Hi, thanks for your help!
I checked everything with I/O Plugin Ping Test and recived some interesting results:

My latency (UAD Out & UAD in) is 81 samples. So i adjust the "Recording Delay" slider -81 samples. This should fix everything, but by recording the Logic Click it doesnt fit eighter.

Furthermore i got another problem.

I got two different latencys:
1. UAD OUT & UAD IN Ping Test: 81 samples
2. ADAT Extension in my UAD - Ping Test: 93 samples

Watch my screenshot:



What do you think??
Thanks in advice!

best wishes,

Malte

Hi This is Aaron here purchased a secondhand Apollo 8p and sent a click to the speaker on Pro Tools, Logic Pro and Luna at 1024 Sample Buffer Size. When IDC is off the, The click is actually offset early for Logic and Pro tools. While Luna has a slight delay instead. When IDC is turned on the signal delayed according to 100, 200, 300, 1000 samples corresponding to short medium medium long and long IDC. Luna is completely in sync. Is there something that is stopping Apollo interface communicating the IDC to Pro tools and Logic? Can anyone please help me.