HDX Card not Showing Up in Core Audio or Pro Tools Ultimate 2019.12

[LukeHoward]

Originally Posted by Producer112

When done with just chassis and no interface I get the same -1175 error upon launch and it quits.

Hmm. OK, another approach which may or may not yield useful results. Try starting Pro Tools, and have a look at the most recent log file in ~/Library/Logs/Avid (you can use Command-Shift-G to go there in Finder).

If my memory serves me correctly, I saw -1175 on starting DigiTest cold (without having started Pro Tools, and quit it, first). So try that too.

[Producer112]

Originally Posted by Southsidemusic

Make sure the digilink is On the ilok key and also do a PRAM and restart the Mac.

We had a similar issue a few years ago on our HDX2 and after uninstalling the HD driver, not just run the installer over the omd HD driver and doing a PRAM we got it up and running. Double check your digilink is on the ilok key not just on the ilok account. Sorry if thats obvious but one post you said it is on your ilok account easily missed and we need to try everything.

Thanks for your reply.

Yes the Digilink I/o asset is on the ILok. I double and triple checked.

Tried un-installing HD Driver. Re-setting PRAm and also re-installing HD Driver. Issue is the same.

[LukeHoward]

Originally Posted by Producer112

Thanks for your reply.

Yes the Digilink I/o asset is on the ILok. I double and triple checked.

Tried un-installing HD Driver. Re-setting PRAm and also re-installing HD Driver. Issue is the same.

Might be time to ring the retailer you bought it from, or use your Avid Support Code.

[Producer112]

Originally Posted by LukeHoward

Hmm. OK, another approach which may or may not yield useful results. Try starting Pro Tools, and have a look at the most recent log file in ~/Library/Logs/Avid (you can use Command-Shift-G to go there in Finder).

If my memory serves me correctly, I saw -1175 on starting DigiTest cold (without having started Pro Tools, and quit it, first). So try that too.

I’ll check that out.

I’ve started a support ticket and will give this the college for another couple days. Won’t have much time to do much due to deadlines but maybe Avid is aware of something I’m not.

One thing that interesting.

I had my Previous Studio machine (a 2013 MacPro Trashcan on Sierra /Pro Tools HD 12.8 or something) and even though I had to run a thunderbolt adapater from the USB 3 Avid chassis to my Trash Can, it turned on right away, and was recognized in the system profiler.

However, I got the exact same DigiTest error and it wasn’t recognized by Pro Tools or Core audio. I did launch pro tools before I plugged the hdx card in to make sure it would launch and it did.

That would have been Hd Driver 12.8 I believe when I checked.

So something is obviously consistent with (2) totally different (but ironically stable systems).

[waynejones253]

I'm getting the same -1175 error when launching DigiTest with my HDX card in the Avid/Sonnet TB3 Chassis. Keep me informed if y'all got a solution.

Specs
Catalina 10.15.5
iMac Retina 5k 27 inch Late 2014
4gHz Quad Core Intel Core i7
32 GB RAM

ProTools Ultimate 2020.5

[waynejones253]

So i tried to hook up the HDX Chassis to a MacBook Pro with 2019.12 and still getting the same “DSI error occurred -1175” when attempting to run DigiTest. Now I wish I had a different chassis to test to see if it’s the card or the newer TB3 chassis itself.

[C_F_H_13]

I know this post is months old, but did you ever find a fix? I'm having the exact same issue right now and was hoping for some insight.

[lichimin]

Hi!

someone find a solution?

i have the same problem with HDX and MTRX studio
i try to change the digilink too but nothing...


Thanks

[creativecontrol]

What macOS version and what version of DADman? This Knowledge base article is also quite useful ->
https://avid.secure.force.com/pkb/ar...__2&popup=true


Jeff

[B-Grade]

This thread has been a lifesaver! I have had the HDX card not showing up, and the script has brought it back. Brought it back, that is until I reboot. I have tried the uninstall reinstall of the HD driver, resetting the Pram, to no avail. I never get any warnings or messages in the security control panel.

So any other ideas on how to fix this for real would be great. I don't want to have to do the script thing every time I reboot.