Hardware/sample rate errors on MacPro7,1

[LukeHoward]

Since upgrading, I'm getting a "Pro Tools detected the number of HDX cards changed" errors when changing sample rates. I imagine this has nothing to do with the Mac but rather also upgrading to HDX2 (MTRX hung off the first card, Avid HD I/O off the second). DADman is set to follow sample rate from DigiLink 1, and the MTRX is the master clock. I'm on Pro Tools 2020.3.

I think this is the relevant error but I could be wrong (it's the last one before Pro Tools quit).

8078.367636,dc003,0e10: CFicMariaTDMDeck::ErrorStop - err: -6080
8078.367752,dc003,000f: CDAEErrorHandler::DAEErrorStopProc - err - -6080
8078.372708,00307,0d02: Performing TCommand: CHandleErrorStopCommand  
8078.372769,00307,000f: CDAEErrorHandler::HandleErrorStop - mErrorStopOSErr - -6080
8078.372916,00307,0e10: ReportDAEError - iDAEError - -6080

[Ryan Young]

I don't have HDX or MTRX, but I've had sample rate weirdness. When Pro Tools is closed and you open "AvidAudioServer", make sure the interfaces are clocked correctly. I had an issue where my 192 kept reverting to 192k although everything I did and needed was 48k. Once I changed it from the audio server, I didn't have any issues where my AES wouldn't feed my speakers or sync issues with other interfaces. Worth a look?

[LukeHoward]

Originally Posted by Ryan Young

I don't have HDX or MTRX, but I've had sample rate weirdness. When Pro Tools is closed and you open "AvidAudioServer", make sure the interfaces are clocked correctly. I had an issue where my 192 kept reverting to 192k although everything I did and needed was 48k. Once I changed it from the audio server, I didn't have any issues where my AES wouldn't feed my speakers or sync issues with other interfaces. Worth a look?

Ah yes, I have a sneaking suspicion it could be Pro Tools momentarily releasing the hardware and their CoreAudio drive taking over in the interim. Everything's clocked together as far as I can tell but, I will simplify things and try with just the MTRX and see how that goes.

[LukeHoward]

Originally Posted by LukeHoward

Ah yes, I have a sneaking suspicion it could be Pro Tools momentarily releasing the hardware and their CoreAudio drive taking over in the interim. Everything's clocked together as far as I can tell but, I will simplify things and try with just the MTRX and see how that goes.

Still seeing this after killing the CoreAudio driver Seems to be AAE error -6080.

NB: error is the number of peripherals connected to the HDX cards changed, not the number of cards. Interestingly I am seeing SDI O PIO Floating Point / PIO TDM Loop / TDM PIO Loop Int B-A fail on the primary (newer) HDX card. Hmmmmm.

[LukeHoward]

This appears to be MTRX-specific, too. If I just connect a HD I/O to the first card there are no issues changing sample rate.