After many tries, and with SIP adjustment made in Recovery; driver/kext still will not load... It never shows up in Security & Privacy/General so that I can "Allow" it to load. Merging Ravenna/AES67 prefs pane is installed along with Aneman, but no device in Audio Midi setup or Sound control panel; Aneman sees my connected Hapi just fine, but can't see Mac/Core Audio.
Anyone find a work around? A couple of you seem to have solved this...
Thanks
VAD 3.2/M1 Pro 12.2.1 will not load K-ext
Forum rules
The Merging Technologies team cannot be held responsible for support queries logged on the public forums. If a support query is logged here and only here, it may not be found and dealt with by the appropriate team.
If you need assistance please contact tech support.
The Merging Technologies team cannot be held responsible for support queries logged on the public forums. If a support query is logged here and only here, it may not be found and dealt with by the appropriate team.
If you need assistance please contact tech support.
Re: VAD 3.2/M1 Pro 12.2.1 will not load K-ext
After much back and forth with Merging Support (Thank you Ricardo!), I have finally found the solution that worked for me elsewhere...
found here in the RME Forum (https://forum.rme-audio.de/viewtopic.php?id=30462), but instead inserting the Merging Technology Apple Developer ID 6DJE6SYM8Q (which I found in /System Information/Software/Extensions/MergingRAVENNAAudioDriver/Signed by):
- Boot into macOS Recovery mode.
- Open Terminal from the Utilities menu in the menu bar.
- Run the command: /usr/sbin/spctl kext-consent add 6DJE6SYM8Q
- Reboot the computer
It should not be necessary, but in case the driver is still not loaded check that everything worked as expected by using this command in the Terminal (Recovery mode not required):
/usr/sbin/spctl kext-consent list
This should give the following result:
Allowed Team Identifiers:
6DJE6SYM8Q
Don’t know why my new Mac is somehow responding differently than others, but from the forum thread linked above it’s clear I’m not the only ‘lucky’ one; I had to use this same path to get my RME kext to load as well.
found here in the RME Forum (https://forum.rme-audio.de/viewtopic.php?id=30462), but instead inserting the Merging Technology Apple Developer ID 6DJE6SYM8Q (which I found in /System Information/Software/Extensions/MergingRAVENNAAudioDriver/Signed by):
- Boot into macOS Recovery mode.
- Open Terminal from the Utilities menu in the menu bar.
- Run the command: /usr/sbin/spctl kext-consent add 6DJE6SYM8Q
- Reboot the computer
It should not be necessary, but in case the driver is still not loaded check that everything worked as expected by using this command in the Terminal (Recovery mode not required):
/usr/sbin/spctl kext-consent list
This should give the following result:
Allowed Team Identifiers:
6DJE6SYM8Q
Don’t know why my new Mac is somehow responding differently than others, but from the forum thread linked above it’s clear I’m not the only ‘lucky’ one; I had to use this same path to get my RME kext to load as well.