What's going on? Recording latency and track delay

[UltimateOutsider]

Wow, this makes a huge difference. I did the little Driver Error Compensation tutorial and found that Live was still around 1.5ms off (which was a huge improvement over what I'd been dealing with before).

QUESTION: Is there a way to enter decimal values in the Driver Error Compensation field in Preferences > Audio? It appears as 0.00 ms, but it would only let me adjust in 1ms increments. I tried double-clicking the value to edit, and tried holding SHIFT, CTRL, and ALT while dragging, but none seemed to do anything. I mean, I can deal with only 0.5ms latency, but it looks like the field should accept decimals...

Now that I have to switch Monitoring to OFF in Live when working with audio tracks I have to use the software my interface came with (CueMix FX) to direct-monitor the incoming audio. Not as flexible as doing everything inside the DAW, but saves me a lot of crazy zooming and panning which I used to have to do when manually adjusting recorded clips to make up for latency.

[manasseh]

Ableton records midi and audio differently depending on whether you choose monitoring "OFF" or "IN"/"AUTO"
if set to "off" it will record and shift the events early according to buffer size latency because it assumes you are monitoring directly with no delay (like asio direct monitoring) - Cubase/studio one have this as default
if set to "in" or "auto" it shifts events later according to buffer size latency so that events are placed "when they are heard" because you compensate and play a little earlier because of the delay

[OCH]

@0x80
Thank you so much for your research and reporting back on this!
Following this thread is still the easiest way to understand what is going on.
Current entries in knowledge base instructions, to read in tandem with this, include:
- https://help.ableton.com/hc/en-us/artic ... n-Live-FAQ
- https://help.ableton.com/hc/en-us/artic ... monitoring
- https://help.ableton.com/hc/en-us/artic ... toring-FAQ

Best,