MTRX Studio automatic sample rate switching issue

[AINSLIE]

So as I move between sessions of different sample rates, protools crashes if I have the 'Conf' - 'Sync' - 'Sampling' set to adapt to Digilink 1. If I set adapt to internal and change manually I can avoid the crashing. I am on the current dadman (5.6.3.8) PT 2022.7 / Catalina 10.15.7. It was doing this on previous versions also. But seems like end of lat year it was adapting to Digilink just fine. However my MTRX Studio is in a semi broken state - no front panel lights, Device list showing front panel status as 'error' I have been meaning to send it in, but I can be without it fora two week or more period. ug.

Thoughts on the adapt setting crash? Is tis reproducible? I have many clients still using 44.1 and money on 48 so its a constant issue manually switching.

[BScout]

Disable the Avid Audio Server, if you haven't already (and you have to do it after every new HDX card driver install since that repairs it.)

Go to Applications > Avid > AvidAudioServer
Fine the "AvidAudioServer" application in that folder
Change its name to "#AvidAudioServer"
You'll be prompted for a password.
Restart computer (what happens is the auto launcher can't find the changed name application so it doesn't launch)

One note is Avid HDX will no longer appear in Audio MIDI Settings after this change as a sound output option. (But most people using a MTRX don't need that anyway -- if they need system sounds, DVS/Dante can be used)

[Reckless Erik]

DAPS won't see the MTRX if you do this

[LDS]

Originally Posted by Reckless Erik

DAPS won't see the MTRX if you do this

I would try using DVS for this if you haven't already. It interfaces in pretty much the same way, except it has about 1/4 of the latency and 1/90 of the cost of a HDX card running under Avid's coreaudio drivers.


If you don't need more than 64 inputs into DAPS, you could even keep using your HDX hardware in Pro Tools this way...

[Reckless Erik]

I would try using DVS for this if you haven't already. It interfaces in pretty much the same way, except it has about 1/4 of the latency and 1/90 of the cost of a HDX card running under Avid's coreaudio drivers.
If you don't need more than 64 inputs into DAPS, you could even keep using your HDX hardware in Pro Tools this way...

I use an HD Native system and the MTRX Studio as the audio and monitoring interface. The latency on Dante is still rather a lot so I don't use DVS as the audio engine for the Dolby Atmos Renderer.

[LDS]

Originally Posted by Reckless Erik

I use an HD Native system and the MTRX Studio as the audio and monitoring interface. The latency on Dante is still rather a lot so I don't use DVS as the audio engine for the Dolby Atmos Renderer.

Depends on the specific setup, really. I have HDN with a DAD DX32 here, which is quite similar. Using HDN in Pro Tools and a HDSPe Madi card in the Atmos renderer is definitely the lowest latency here. In terms of software solutions though, I actually think DVS might have considerably lower latency than Dolby Audio Bridge. Unless you need more than 64 inputs into the renderer, there are quite a few upsides to using it (latency, live inputs into pro tools, hardware inserts, live rerender returns & plugin metering, Pro Tools video sync peripheral support, etc).

Dolby Audio Bridge always seems to come in the slowest in loopback and video sync tests here. It is always the configuration with results that are furthest away from a standard HDN setup using only Pro Tools.