DADman Routing Results -3db Loss
 

I'm hoping there's a simple answer as we're new to DADman and Dante.

Until incorporating DADman in our setup with a new MTRX ST, we have successfully been operating a modified Native Atmos setup. We routed live rerenders from DAPS to Source Nexus so we can pick them up in PT for measurement and outputs. Everything worked great!

Now, using DADman and the MTRX ST, we are routing live rerenders in DAPS from DigiLink to Dante in DADman, then Dante to DVS in the Dante Controller, and then DVS to Source Nexus in Pro Tools. However, the signal is coming back -3db lower.

When we switch between the 2 setups, the results are consistent, which confirms something is up with DADman and/or Dante causing a -3db result.

Did we miss something during setup that would explains this?

Thanks.

Re: DADman Routing Results -3db Loss
 

We can eliminate Dante altogether by sending live rerenders in DAPS from DigiLink to DigiLink in DADman, and pick them up with Source Nexus in PT ... and we still get the same result.

Did we miss something in the DADman setup as it seems the issue is with DADman?

Thanks.

Re: DADman Routing Results -3db Loss
 

Have you tried skipping DAPs and just checking a sine 1k tone from digilink to digilink looped through the MTRX Studio?

DADman doesn't change levels unless running through the ProMon (monitoring) section.
Double-checked it here (on a full MTRX though there should be no difference) and it is still as accurate as ever.

When you say you are routing DAPS to digilink, I assume that is direct? Which would mean you are using the CoreAudio driver model for digilink. CoreAudio has gain level/trim possibilities (in Audio/MIDI Setup)

Re: DADman Routing Results -3db Loss
 

Exactly what I was going to suggest. Look to AMS: Audio and check for any inadvertent attenuations.


Jeff

Re: DADman Routing Results -3db Loss
 

Ugh .... Yes, of course! AMS output set to -3.

Does a new unit default to -3 in AMS? We never touch it!

Thanks for the quick fix.