bruddell

Glad I could help dslee. Be forewarned, every time there is a Big Sur update your POD will stop working again and you will have to repeat this process. I've gotten it down to about 3 minutes.

I was finally able to get my POD HD500X Edit software to work. I'm new to Mac so it took some learning. I tried dingdini's solution but it kept giving me a "Authenticating extension failed: Bad code signature" error. The solution was to temporarily disable SIP. There is info on the web if you need more detail, but in short, reboot into recovery mode, go to the terminal and type "csrutil disable". Reboot. Once you are back in MacOS perform dingdini's solution. It "should" work, at least it did for me. Once you have it working, you can (and should) reenable SIP by booting back into Recover Mode, run Terminal and type "csrutil enable". Reboot back into standard MacOS and you should be all set.

I could see that the Line6 extension was not loaded. So I tried to manually load from the terminal screen and get the following result regarding a "Bad Signature" : sudo kextutil -vvvv -bundle-id com.line6.driver.xtaudio Defaulting to kernel file '/System/Library/Kernels/kernel' Executing: /usr/bin/kmutil load --bundle-identifier com.line6.driver.xtaudio Error Domain=KMErrorDomain Code=29 "Authenticating extension failed: Kext com.line6.driver.xtaudio v7.6.8 in executable kext bundle com.line6.driver.xtaudio at /private/var/db/KernelExtensionManagement/Staging/com.line6.driver.xtaudio.wy23zM/Line6Audio.kext: Authenticating extension failed: Bad code signature" UserInfo={NSLocalizedDescription=Authenticating extension failed: Kext com.line6.driver.xtaudio v7.6.8 in executable kext bundle com.line6.driver.xtaudio at /private/var/db/KernelExtensionManagement/Staging/com.line6.driver.xtaudio.wy23zM/Line6Audio.kext: Authenticating extension failed: Bad code signature} Does Line6 need to update their signature? Is there some sort of workaround?