kevink's Recent Posts
It could be something as simple as the certificate used to sign the binary having expired.
This was something I saw in the beta, and to a lesser degree in 1.0. As you observed, it's not that the plugin is constantly taking all available CPU cycles. Another of my observations was that I'd get a lot more audio artifacts (a) when interacting with the GUI, and (b) just after a preset is loaded. As a software engineer who's written some real-time audio code, the first would be typical of the code making system service calls (i.e. GUI updates and inputs) using (or blocking with a held lock) the thread that updates the audio buffers, and the second would be typical of doing the same with the loads from files of patch parameters and samples. I don't know how Sumu is implemented, but hopefully this will trigger some thoughts on what to look for to debug it.
There have been other reports of people having problems downloading and installing v1.1.1 for MacOS. The Windows binary has a similar problem. Chrome considers it a defective/dangerous file and will only download it if forced. Windows 10 likewise blocks execution of the installer, as it is from an "unknown publisher". Indeed, looking at the file properties, most of them have been stripped, apart from the name Sumu and the version 1.1.1. I could override this, but it's such a basic breach of computer security practice that I don't want to do it. Please, rebuild the distribution binaries and republish them!