Protools 2022.10 HD Driver wrongly labelled after install

[paulo m]

Hi,

after installing PT HD driver 2022.10 along wit the same PT version, Sys Info/software/extensions shows the Digidal.kext file as 2022.9

Screenshot 2022-10-30 at 19.10.27.jpg

[creativecontrol]

Greetings,

There were no changes to the HD Driver released with Pro Tools 2022.10 from 2022.9. In the future, we will try and update the HD Driver version to match the Pro Tools version.


best,


Jeff

[paulo m]

Originally Posted by creativecontrol

Greetings,

There were no changes to the HD Driver released with Pro Tools 2022.10 from 2022.9. In the future, we will try and update the HD Driver version to match the Pro Tools version.


best,


Jeff

Thanks for clarifying Jeff.

Do you have any idea on why HDX is not available anymore to use as output device in the DAPS or shows up on Audio MIDI setup when PT is closed or the Playback Engine is other than HDX?

Since version 2022.9, HDX has mysteriously vanished for other uses except for PT, so I can´t use it anymore as my output on the DAPS Renderer for example. Had to reconfigure everything with the PT Audio Bridge, before I could have the audio outs from the Renderer straight to DADman using HDX, not anymore...

Posted on Dolby forum as well, but they don´t know either.

Best,

[creativecontrol]

That certainly sounds like the HD Driver loading conversation. Have you gone through everything in the knowledge base?

https://avid.secure.force.com/pkb/ar...n-macOS?retU_7

Also, have you tried to launch the Avid Audio Server manually? May not be a bad idea to try creating a new Admin User on your machine as well and see if things improve.

best,


Jeff

[paulo m]

Originally Posted by creativecontrol

That certainly sounds like the HD Driver loading conversation. Have you gone through everything in the knowledge base?

https://avid.secure.force.com/pkb/ar...n-macOS?retU_7

Also, have you tried to launch the Avid Audio Server manually? May not be a bad idea to try creating a new Admin User on your machine as well and see if things improve.

best,


Jeff

Hi Jeff, thanks,

yes, I followed all the best practices on the article, except I never tried to launch the AAS manually, as the HD Driver shows up as loaded on Sys Info/Software/Extensions (Digidal.kext) and it works perfectly with PT and the HDX card too. I uninstalled the HD driver and reinstalled as well. Only happens since V 2022.9, was working perfectly before that. I suspect has something to do with the new Aux features launched with 2022.9, but it´s obviously just a coincidence. It seems that PT does not release the HD driver properly when the PB Engine is set to DAB or other.

[paulo m]

Originally Posted by paulo m

Hi Jeff, thanks,

yes, I followed all the best practices on the article, except I never tried to launch the AAS manually, as the HD Driver shows up as loaded on Sys Info/Software/Extensions (Digidal.kext) and it works perfectly with PT and the HDX card too. I uninstalled the HD driver and reinstalled as well. Only happens since V 2022.9, was working perfectly before that. I suspect has something to do with the new Aux features launched with 2022.9, but it´s obviously just a coincidence. It seems that PT does not release the HD driver properly when the PB Engine is set to DAB or other.

Here´s a link to the Dolby forum thread that I posted about this:

https://professionalsupport.dolby.co...=1667233676938