Trying to get some waves plugins to work on Big Sur.


I copy and pasted some terminal commands on my macbook which is running Big Sur and received the response shown in the attached photos. The files that the command line are addressing are placed in the spot they should be placed. I'm not sure what terminal is upset with and was hoping someone here could help shine some light on the issue.

Commands used in terminal:

xattr -cr /Library/Application\ Support/Waves/Modules/WavesLicenseEngine.bundle


sudo codesign --force --deep --sign - /Library/Application\ Support/Waves/Modules/WavesLicenseEngine.bundle


As you can see, there are two terminal commands, both which have their own error. See below.

Image 1: The terminal commands used which I copy and pasted exactly as shown.


Image 2: The terminal response to my commands

https://imgur.com/a/nEM6Q0R

 

Last edited: Sep 22, 2022

I always use Codesigner to avoid Typographical Errors. Here is a link to it: https://mega.nz/file/sV4wXQQQ#GgV1gF7S38E09nCCAmzWszCR3GQc9PwQP4nOnLFmQ2Y

Anything you need after that should just be Waves related, and I do not use Waves.

 

I have same problem with synplant 2.

 

in most linux and unix o/s of which osx is a variant (berkley standard distribution - BSD)
you can type $help and the command name so, "$help xattr" should return the help file for the xattr command.

linux help command link
https://www.geeksforgeeks.org/help-command-in-linux-with-examples/

Mac terminal help command link
https://phoenixnap.com/kb/mac-terminal-commands

in the 1st example
xattr -cr /Library/Application\ Support/Waves/Modules/WavesLicenseEngine.bundle

your slashes are mixed in direction which may be confusing the command interepter.
typically in an operating system it wants all the slashes to go in one direction, forward or backwards

ie windows uses c:\windows\billgatesucks\mylifeisover.txt
in your example the 2nd and 3 slash are in different directions. this is wrong..

 

Go here ---> https://audiosex.pro/threads/codesigning-for-sip-enabled.74681/.

And read yourself through!

 

the 2nd error says codesign "cannot be found or used" so make sure codesign is present and the path variable is set to allow the o/s to see it, by typing just the command "codesign" minus the "".. if it says cannot be found, etc. you need to supply the path to codesign when using the command.

in linux if I remember correctly the command would be "find codesign" which should return all instances of codesign on your machine, this should show the path to the location of where codesign can be found, add this path to the command you are trying to execute. and it should work..

 

note.... this may also be an error caused by incorrect path as the slashes are still mixed in this command line as well.