Hello,
I am on a thread ripper of a PC. Total CPU usage in Reaper 7 is 4% with sumu at 96khz and 4096 buffer size.
Windows task manager is showing 11% memory usage and 9% cpu for reaper, the rest of the machine is in good numbers.
No matter what I do, Sumu sounds glitched out like my cpu is maxed out (when it's not). Can't fix unless I go down to 48khz.
Anyone else seeing this issue?
Thanks for the report. I've added this to the issues list. As soon as I can fix the installer issues with this version I'll try a higher sample rate in Reaper and see if I can reproduce.
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.