HD driver MTRX studio

[Soundworks UK]

Hi, a while ago I switched to a totally native system with a UA Apollo 16 interface. I made this decision primarily because I thought it worked better with Mac OS non Avid software, I could play Spotify / YouTube etc through my studio monitor system as well as Pro Tools, which has worked great. My question is how is the Avid HD driver these days? (It wasn't great a few years back) as I'd quite like to go with the MTRX studio with a HD native setup and have all the benefits of monitor control over Eucon etc.

Would that give me the same flexibility in terms of being a good Mac OS interface also?

[Soundworks UK]

Just to be clear, I'm talking about the core audio driver.

[originalscottyg]

With MTRX Studio, most are monitoring non-Pro Tools audio via Dante Virtual Soundcard into the Dante inputs on the MTRX Studio, with are then used as a monitor source in the EuCon DADman monitor section. Works quite well, unless you are switching sample rates a lot (e.g. back and forth from 48k to 96k and back). I find manually switching the sample rate for DVS in Dante Controller to be hit or miss and a bit frustrating. I would really love for DADman to be able to SRC incoming Dante signals.

Otherwise, monitoring non-PT audio through Dante into the MTRX monitor section is great!

[Soundworks UK]

Aha very interesting thanks Scott

[originalscottyg]

Any time! The MXTR Studio, or more specifically DADman software, has a pretty steep learning curve. But once it's setup it works great, for the most part. There is a very long thread with a lot of great info and some links to tutorials in this forum titled "First Steps with MTRX Studio". I would recommend perusing through that thread.

[uptheoctave]

Originally Posted by originalscottyg

I find manually switching the sample rate for DVS in Dante Controller to be hit or miss and a bit frustrating. I would really love for DADman to be able to SRC incoming Dante signals.

Agree- it is very annoying.
I ended up running multiple audio interfaces- one for native, one for HDX.

[originalscottyg]

Originally Posted by uptheoctave

Agree- it is very annoying.
I ended up running multiple audio interfaces- one for native, one for HDX.

Are you using a MTRX or MTRX Studio connected to the HDX card for monitoring? How do you run the native interface back into the MTRX for monitoring?

[LukeHoward]

Originally Posted by uptheoctave

Agree- it is very annoying.
I ended up running multiple audio interfaces- one for native, one for HDX.

Super annoying isn’t it! Particularly as on my Mac (not sure if it’s related to MacPro7,1 or Catalina) I can only change the sample rate on DVS from Dante Controller from a second machine. If I change it on the machine on which it’s running, it doesn’t stick.

[originalscottyg]

Originally Posted by LukeHoward

Super annoying isn’t it! Particularly as on my Mac (not sure if it’s related to MacPro7,1 or Catalina) I can only change the sample rate on DVS from Dante Controller from a second machine. If I change it on the machine on which it’s running, it doesn’t stick.

Interesting. I was having the same problem of the sample rate change not sticking sometimes. It was pretty hit or miss. This was on Mojave, though, not Catalina. I never thought to try using a different machine, since my Dante network was self-contained to the computer with the MTRX Studio. (I am writing in past tense because I am at home working on an Omni at the moment while we are building out an Atmos room).

[LukeHoward]

Originally Posted by originalscottyg

Interesting. I was having the same problem of the sample rate change not sticking sometimes. It was pretty hit or miss. This was on Mojave, though, not Catalina. I never thought to try using a different machine, since my Dante network was self-contained to the computer with the MTRX Studio. (I am writing in past tense because I am at home working on an Omni at the moment while we are building out an Atmos room).

Yeah, I guess it could be a bug that affects all platforms but it seems like something that should be caught in QA. If you could change the rate from DVS itself or, if it could follow another Dante device, that would be nice. Don’t think anyone from Audinate will be reading this though.