MTRX IO Delays

[shawnhonsberger]

Originally Posted by uptheoctave

Thanks for this Jeff.

It would be very, very helpful for this to be automatically calculated, or for there to be a roundtrip 'ping' type plugin (like the IO plugin in Logic) to save a lot of faffing about.

+1

[uptheoctave]

Would anyone like me to post DADman IO delays?

I'm expanding my MTRX II with an AX64 over DADman and using some inserts on the AX64 (I've kept most of them on the MTRX II to simplify things but I recently added more analogue outboard.)

I've also got delays for a H9000 over Dante and an Axe FX III over AES.

[shawnhonsberger]

Hi James,

I would love that! Though I'm on MTRX Studio, it might still be a helpful reference for everyone.

Thank you!

[Darryl Ramm]

James, I love seeing real latency measurements so whatever you can do here would be great.

For CoreAudio are you going to use RTL Utility to do these measurements? If so can you please include the driver reported latencies as well.

If you want to go all out RTL Utility also breaks down the components of the latency that CoreAudio is reporting, they are not show by default in the output window in RTL Utility (you can add them to the displayed columns in the RTL Utility main window UI, but all the numbers are always recorded in the measurement log file (kudos to the RME developers who asked the RTL Utility developer for this feature).

When I make measurements with RTL Utility, I just run them all and then massage the data out of the measurement log file, makes it easy. If you do that could you consider including the additional driver reported latency component data e.g. Core Audio Input|Output Safety Offset, CoreAudio Input|Output Stream Latency.

[uptheoctave]

Originally Posted by Darryl Ramm

James, I love seeing real latency measurements so whatever you can do here would be great.

For CoreAudio are you going to use RTL Utility to do these measurements? If so can you please include the driver reported latencies as well.

If you want to go all out RTL Utility also breaks down the components of the latency that CoreAudio is reporting, they are not show by default in the output window in RTL Utility (you can add them to the displayed columns in the RTL Utility main window UI, but all the numbers are always recorded in the measurement log file (kudos to the RME developers who asked the RTL Utility developer for this feature).

When I make measurements with RTL Utility, I just run them all and then massage the data out of the measurement log file, makes it easy. If you do that could you consider including the additional driver reported latency component data e.g. Core Audio Input|Output Safety Offset, CoreAudio Input|Output Stream Latency.

Yes I can use RTL Utility for Core Audio.

I did some CA latency in a Gearspace thread a while back.

For HDX I just record off a bus with a hardware insert in place on the master channel and then use the grid set to samples and use my eye to estimate the peak in a sample with a lot of attack (like a click or a bass drum).

It will take me a little while to do this as I need to reconfigure things a bit.
By default I use SRC on one incoming stereo AES channel so I will need to remember to disable that.

I'll also do some readings with and without Pro Mon turned on.

[shawnhonsberger]

Thank you so much, James!

[shawnhonsberger]

Originally Posted by creativecontrol

Greetings,

This is a work in progress, however I wanted to start in on the discussion of patching different types of IO into MTRX family devices and determining the appropriate delay values. Here's the start of that. Please note that all of the Digi Delay values being used here are 7 samples - which is the default when you have the monitor section (Pro|Mon) enabled on MTRX with a monitor profile loaded. We can discuss more on that - but for now I would always recommend using the 7 sample value for consistency. Hopefully this will be a helpful starting place before we can get some of this put into an article on the Avid Knowledge Base.

MTRX Studio
AD DA via DigiLink to Pro Tools HDX
1.29ms Hardware Insert Delay
44.1kHz, 7 Samples Digi Delay

AD DA via DigiLink to Pro Tools HDX
1.17ms Hardware Insert Delay
48kHz, 7 Samples Digi Delay

AD DA via DigiLink to Pro Tools HDX
0.63ms Hardware Insert Delay
88.2kHz, 7 Samples Digi Delay

AD DA via DigiLink to Pro Tools HDX
0.58ms Hardware Insert Delay
96kHz, 7 Samples Digi Delay

AD DA via DigiLink to Pro Tools HDX
0.28ms Hardware Insert Delay
176.4kHz, 7 Samples Digi Delay

AD DA via DigiLink to Pro Tools HDX
0.26ms Hardware Insert Delay
192kHz, 7 Samples Digi Delay

MTRX I and MTRX II
AD DA via DigiLink to Pro Tools HDX
1.17ms Hardware Insert Delay
44.1kHz, 7 Samples Digi Delay

AD DA via DigiLink to Pro Tools HDX
1.06ms Hardware Insert Delay
48kHz, 7 Samples Digi Delay

AD DA via DigiLink to Pro Tools HDX
0.55ms Hardware Insert Delay
88.2kHz, 7 Samples Digi Delay

AD DA via DigiLink to Pro Tools HDX
0.51ms Hardware Insert Delay
96kHz, 7 Samples Digi Delay

AD DA via DigiLink to Pro Tools HDX
0.26ms Hardware Insert Delay
176.4kHz, 7 Samples Digi Delay

AD DA via DigiLink to Pro Tools HDX
0.24ms Hardware Insert Delay
192kHz, 7 Samples Digi Delay





Jeff

Thank you, Jeff for updating this first post! It's super helpful! I appreciate you. Is it also possible for you to post the numbers for inputs as well? Furthermore once inputs are included, it is possible for you to post the numbers via TB3 and not just HDX? Thanks, again!