What are they talking about?

[mightyduck]

I bought a Thunderbolt and HD Omni Interface awhile ago, and I'm just getting around to setting it up and figuring it out.

I'm used to working with HD Systems with a console and all that.

The manual for the Omni says:

"with Omni HD, Delay Compensation is not supported on the Monitor output paths. Delay Compensation is only supported on the physical output paths
(those not assigned for the monitor path)"

Maybe I am missing the obvious, but what does that mean, exactly?

Enlighten me, please.


Best,

mightyduck

[_JJ_]

Yeah, I can't decode that either. But I will mention that Low Latency Monitoring with that setup is only available from the Omni output, not from the headphone jack on the TB box. LLM happens physically inside the Omni. Could that be related to what they're trying to tell us? I dunno.

[mightyduck]

Like what is the difference between the "monitor output paths" and the "physical output paths"? Doesn't it all go through the same circuit / tsp? You have to monitor from a physical output, right?


Anyone? I think I am not understanding something basic to this box.



Best,

mightyduck

[JFreak]

Old review here

[mightyduck]

Originally Posted by JFreak

Old review here

Thanks. I saw that, but, well, TLDR. : ) It does initially confirm my belief that this is kind of a weird piece of gear. I guess I should wade through it, and see if it makes any sense to me. Did you find it helpful?

Do you have a short "cliff-notes" explanation by any chance.


EDIT: I read the whole article. Not a lot of answers there, as far as I can tell. What am I missing?


Thanks,

mightyduck

[Ashford]

The AVID I/O boxes have the capability to correct and automatically time align for the couple of cycles of latency introduced by the A/D and D/A process. This is available on all the Avid I/O channels. It appears that on the Omni that this correction is not available on the monitor output path. I cannot see why this would be a problem, unless you were using the monitor output as a line output.

[mightyduck]

Originally Posted by Ashford

The AVID I/O boxes have the capability to correct and automatically time align for the couple of cycles of latency introduced by the A/D and D/A process. This is available on all the Avid I/O channels. It appears that on the Omni that this correction is not available on the monitor output path. I cannot see why this would be a problem, unless you were using the monitor output as a line output.

What is the "monitor output"? "path"?



Best,

mightyduck

[Ashford]

I/O setup under the Setup tab configures the I/O setup
Under input there is a tick box that says "Compensate for input delays after record pass"
Under output there is a tick box that says "Compensate for output delays after record pass"
Below the output delay tick box there are a number of options for output paths. One of these options is Monitor Path. If you assign an output to the monitor path, delay compensation will not be applied even if the delay compensation tick box is ticked.

[mightyduck]

Originally Posted by Ashford

I/O setup under the Setup tab configures the I/O setup
Under input there is a tick box that says "Compensate for input delays after record pass"
Under output there is a tick box that says "Compensate for output delays after record pass"
Below the output delay tick box there are a number of options for output paths. One of these options is Monitor Path. If you assign an output to the monitor path, delay compensation will not be applied even if the delay compensation tick box is ticked.

When I try to set the monitor output paths to "none", I get no audio to the outputs at all. Also the software demands that I assign a monitor output to either main or alt output path, or it will not get past the dialogue box roundabout.

Is it possible to listen to audio from a Pro Tools session with a Thunderbolt Omni setup, without using the monitor path scheme?

It seems to me, btw, that having no "compensate for record pass" function would ruin overdubs because they would not print time-aligned.

What am I missing?


mightyduck

[JFreak]

You are not recording thru your monitor path nor using hardware inserts with those outputs so what is the problem really? Please, just tell me again and I may be able to understand