[BScout]

Originally Posted by JFreak

Doesn't carbon have that automatic latency compensation on IO setup?

It only compensates for its own hardware.
It doesn't compensate for devices attached (which add additional latency.)

To the OP, you can use user offsets (per track) for latency but it gets messy. It's easier to set a nudge value and then nudge post-record.

For inserts, you can compensate the round trip in I/O. There's been a long standing request to make that sample based (so changing sample rates, you don't have to correct) but that's not been implemented yet.