Can TB3 be the only connection to the Mac?

[RobertDorn]

Interesting topic to read:) actually always wondered what wizardry made it happen that when overdubbing with an Apollo (monitoring through console, same principle as when monitoring the incoming signal directly through the MTRX by connecting the dots in DADman) made it happen that even when dubbing in on a pro tools session with some sample heavy mastering processing on the masterbus already, everything ends up perfectly in time. If I understand it all right the DAW just reports this back to the core audio driver. Cool.

[Darryl Ramm]

Originally Posted by RobertDorn

Interesting topic to read:) actually always wondered what wizardry made it happen that when overdubbing with an Apollo (monitoring through console, same principle as when monitoring the incoming signal directly through the MTRX by connecting the dots in DADman) made it happen that even when dubbing in on a pro tools session with some sample heavy mastering processing on the masterbus already, everything ends up perfectly in time. If I understand it all right the DAW just reports this back to the core audio driver. Cool.

The DAW does not report latency to the driver, it's the other way around. At some point in setting stuff up the DAW asks the driver for its latency data and then uses that as described in this thread. All the timing/latency adjustment happens purely in the DAW.

You will have to look through what is happening in any dubbing situation. e.g. if (UAD console) hardware or software monitoring is being used, if plugins are enabled or disabled on monitoring paths, what the actual latencies are, etc.

[RobertDorn]

Originally Posted by Darryl Ramm

The DAW does not report latency to the driver, it's the other way around. At some point in setting stuff up the DAW asks the driver for its latency data and then uses that as described in this thread. All the timing/latency adjustment happens purely in the DAW.

You will have to look through what is happening in any dubbing situation. e.g. if (UAD console) hardware or software monitoring is being used, if plugins are enabled or disabled on monitoring paths, what the actual latencies are, etc.

mmm perhaps then it's a feature in Pro Tools with LLM enabled, like, if Pro Tools knows the session delay is 8000 samples, and you'll use hardware monitoring, it 'knows' to print the audio clip 8000 samples to the left because it was performed to a mix heard 8000 samples later. Or something:) then I don't yet factor in the RTL as discussed above in this thread. At least in practice, it turns out to work flawlessly for me.