MTRX Studio - Output fine, no input now

[LDS]

Originally Posted by 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

I sold my Omni for exactly the same reason. ADAT is probably your best bet without chewing up Dante channels for stuff like Atmos.

[Matt Stephanson]

Thanks again, LDS!

So just to confirm: one doesn't need to combine the MTRX Studio with another digi interface in order to work in Pro Tools.

If that's so, I can get rid of the entire HDN+Omni setup, and run things via an 8 ch. ad/da's adat i/o.

Does that make sense?

[creativecontrol]

Correct. If you are happy running FF PCIeR + MTRX ST -> that's fine. Just don't run DVS as your primary conduit to MTRX ST.



Jeff

[Matt Stephanson]

Got it, Jeff. Thanks, that makes sense. I need at least the MTRX + a RedNet card.
This sounds like a more stable system than just relying on DVS.
I’m hopeful that will reduce the random dropouts I was getting.

Cheers all!

[LDS]

Originally Posted by Matt Stephanson

Got it, Jeff. Thanks, that makes sense. I need at least the MTRX + a RedNet card.
This sounds like a more stable system than just relying on DVS.
I’m hopeful that will reduce the random dropouts I was getting.

Cheers all!

Depends what you are trying to achieve. The MTRX Studio with the HDN card will be pretty similar in function when using Pro Tools.

[creativecontrol]

Yes - agreed. A few comparisons for engines to connect to a MTRX Studio:

HDX - Hybrid engine, DigiLink, 64 Channels of IO per card (up to 192 IO), Frame Edge Alignment (via SYNC X or SYNC HD), Dante available
HDN - Native engine, DigiLink, 64 Channels of IO, Frame Edge Alignment (via SYNC X or SYNC HD), Dante available
PCIeR - Native Engine, 64 Channels via CoreAudio, No Frame Edge, Dante allocated



Jeff