Yes, the recommended way to connect a MTRX Studio interface is with an HDX or HD Native engine. In doing so, it is recommended to connect both 32-channel DigiLink ports for 64 channels and the most flexibility of bidirectional analog and digital interfacing. If expanding beyond a single HDX card, multiple sets of 64 channel IO connections can be made when adding a 2nd MTRX Studio. This can also facilitate Dolby Atmos workflows when interconnecting a Dante based renderer running DAMS.
Alternative means of connectivity include IP Audio with Dante. The best way to connect (lowest latency for example) would be with a PCIe based interface from Focusrite or Yamaha:
https://pro.focusrite.com/category/a...m/rednet-pcier
https://usa.yamaha.com/products/proa...8-d/index.html
It is also possible to use a virtual audio driver with Audinate's Dante Virtual Soundcard (DVS). If using DVS, you should try and minimize the buffer setting (Dante Latency) - which spans from 4 ms -> 10 ms.
https://www.audinate.com/products/so...tual-soundcard
Regarding loading existing or preset monitor profiles (.dmprof files), after choosing the profile to open you will indeed get an error message if the monitor profile was created on a device with a different serial number. Simply hit Cancel, go to Settings > Monitor Profile, choose your unit from the menu (Select unit) then tick Enable monitor.
Regarding networking for DADman management and IP Audio, it is highly recommended to have at least a Gigabit switch if not a router to connect MTRX Studio, workstations and any other Dante devices. Here's a knowledge base document from Audinate on best practices for networks with Dante:
https://www.audinate.com/support/networks-and-switches
Here's an expanding collection of Monitor Profiles for MTRX Studio:
MTRX Studio Monitor Profiles
Additionally, an expanding playlist of MTRX and MTRX Studio specific videos can be found here:
https://www.youtube.com/playlist?lis...QDeRgOaJw_FSI1
best,
Jeff