MTRX Studio - Output fine, no input now

[Matt Stephanson]

After no change to OS, 3rd party software, plugins, or configuration, I'm no longer getting input signal into the MTRX Studio, despite green lights all around in DADman and Dante Controller.

I just tried reinstalling the latest firmware (1.0.3.2) for the MTRX St, but not having any luck.

Outputs are fine, and all my programmed functions on the panel of the MTRX are working (shifting between mon sets, folddown, etc.). 7.1 to stereo all working.

Just no input now!

Has anyone seen/solved something like this?
I've checked all cabling, tried plugging/repluggin, the normal techery.
Restarted many times, of course!

Using latest PT Ultimate, MTRX Studio, DADman 5.4.4.2, 2019 Mac Pro 3.2 on Catalina.

Where to continue troubleshooting?
Thanks very much for any insight, folks!

[creativecontrol]

Greetings,

What kind of Inputs - Mic, DI, Line level analog, ADAT, Dante, DigiLink?

Whatever the question to the above - do you see meter deflection in DADMan for said inputs? If so, likely this signal is there - just perhaps not being routed correctly. I would also recommend pulling down 5.4.5 of DADman from your Avid account as it is a bit more current relative to your macOS.


Jeff

[Matt Stephanson]

Thanks, Jeff!

All inputs are blank in Pro Tools now.

I used to be successful feeding 16 analog I/o over DB25, all routed in and out of pro tools, but now it's not passing input any signal at all.

I see no meter deflection in either DADman, or on the panel of the MTRX Studio.

One thing though, under Pro Tools' engine, I'm using "Dante Virtual Soundcard" and not seeing my Omni HDN as an option. Omni HDN does NOT show up in Audio Midi Setup, either. It never has since installing the MTRX.

For whatever reason, it's been working until yesterday, so I'm just trying to get to the bottom of it.

Edit - just updated to 5.4.5 DADman.

Thanks much!

[creativecontrol]

DVS = Dante Virtual Soundcard is CoreAudio - and is not a direct HD engine like HDX or HDN and as such you will not be able to see your OMNI or MTRX via DigiLink.

All inputs are blank? Do you mean there are no paths defined for Input or Output in Pro Tools? These are independent from the signal flow actually existing and being patchable into Pro Tools.

Is there a reason you are using DVS (which is not great for clocking or latency) instead of HDN + MTRX?


Jeff

[Matt Stephanson]

Hi Jeff,

Thanks for the replies!

Basically everything was working fine until last week, when after no change, audio input is not happening. Output is fine.

There's no reason I'm using DVS over HDN, other than I can't seem to get the routing sorted any other way.



How can I integrate the OMNI and the MTRX Studio within the Pro Tools I/o setup window?

I'm using an HDN Thunderbolt box with the Omni and the MTRX.
I'm clearly confused here

[Matt Stephanson]

Ok, I have input working again, so please ignore my post.

Except, I'm still not sure of best practices on a couple things.

1. In an IT managed environment (university), how to mitigate traffic issues causing dropouts, etc.?

2. Would using a PCIe card like the rednet help stability?

3. I'm using DHCP, would a fixed address help stability?

I'd experiment, but in the school, everything is a request to IT and takes time for them to respond, of course.
So I thought I'd just ask these 3 points to help my system run smoother.

Thanks very much!

[creativecontrol]

Place MTRX ST / DVS / and any other IP Audio devices on their own dedicated network outside of your LAN / Internet / facility / school network. If you don't have a router - assign static IP addresses to everything. If you don't have a free physical NIC / Ethernet port - simply add an Apple Gigabit adapter for the flavor of your computer.



Jeff

[Matt Stephanson]

Thanks, Jeff; will put in a router and get it all isolated. Appreciate your help!!

[LDS]

Originally Posted by Matt Stephanson

How can I integrate the OMNI and the MTRX Studio within the Pro Tools I/o setup window?

I'm using an HDN Thunderbolt box with the Omni and the MTRX.
I'm clearly confused here

Unfortunately you can't route the Omni in the way you are trying to do in DADman. They don't talk to each other in that way. The MTRX Studio works just like any other digilink interface in that regard, with the exception of being able to toggle the second digilink port between primary (to speak directly to the HDN), or expansion (to pass through audio from another digilink interface straight to HDN).

[Matt Stephanson]

Thanks, LDS!
So really no reason to keep the OMNI, then.
Sounds like I need to invest in some more converters of the ADAT variety to get those last 8 i/o happening within PT.

Thanks folks. Will do some more digging.

Best,
Matt